Re: PATCH: Lock tty directly in acct layer

Ar Mer, 2006-08-16 am 18:24 +0200, ysgrifennodd Arjan van de Ven:
> > -	read_lock(&tasklist_lock);	/* pin current->signal */
> > +	mutex_lock(&tty_mutex);
> >  	ac.ac_tty = current->signal->tty ?
> 
> but.. can't ->signal still change, even if signal->tty isn't ?

I'm not sure, thats a good question (as if so is how to lock it). Will
investigate.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • PATCH: Lock tty directly in acct layer
    • From: Alan Cox <[email protected]>
  • Re: PATCH: Lock tty directly in acct layer
    • From: Arjan van de Ven <[email protected]>

• Prev by Date: Re: DEBUG_LOCKS_WARN_ON triggered by bcm43xx-SoftMAC
• Next by Date: [PATCH 7/7 v2] [I/OAT] Add entries to MAINTAINERS for the DMA memcpy subsystem and ioatdma
• Previous by thread: Re: PATCH: Lock tty directly in acct layer
• Next by thread: PATCH: Multiprobe sanitizer
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]