Re: How to lock current->signal->tty

Ar Maw, 2006-08-08 am 09:41 -0700, ysgrifennodd Luck, Tony:
> unaligned accesses at all is rather controversial.  So its a 50-50
> shot whether I'll fix it by adding the mutex_lock/mutex_unlock
> around the use of current->signal->tty, or just rip this out and
> just leave the printk().

Personally I'd just rip it out full stop. Its trivial to use kprobes and
friends to audit such things if there is a performance concern.

Alan

-
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/

---

• Follow-Ups:
  • Re: How to lock current->signal->tty
    • From: Jes Sorensen <[email protected]>

• References:
  • How to lock current->signal->tty
    • From: Alan Cox <[email protected]>
  • Re: How to lock current->signal->tty
    • From: Arjan van de Ven <[email protected]>
  • Re: How to lock current->signal->tty
    • From: Alan Cox <[email protected]>
  • Re: How to lock current->signal->tty
    • From: "Luck, Tony" <[email protected]>

• Prev by Date: Re: + fs-cache-make-kafs-use-fs-cache.patch added to -mm tree
• Next by Date: Re: [PATCH 1/3] Kprobes: Make kprobe modules more portable
• Previous by thread: Re: How to lock current->signal->tty
• Next by thread: Re: How to lock current->signal->tty
• 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]