Re: PATCH: Voyager, tty locking

> The signal handling also appears to be incorrect as it does an
> unprotected sigfillset that also appears unneccessary. As I don't have a
> bowtie and am therefore not a qualified voyager maintainer I leave that
> to James.

Bowtie or not, you touched it last!

This seems like a decent candidate for being moved over to the kthread API..

- z
-
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: PATCH: Voyager, tty locking
    • From: James Bottomley <[email protected]>

• References:
  • PATCH: Voyager, tty locking
    • From: Alan Cox <[email protected]>

• Prev by Date: Re: How to lock current->signal->tty
• Next by Date: Re: PATCH: Voyager, tty locking
• Previous by thread: PATCH: Voyager, tty locking
• Next by thread: Re: PATCH: Voyager, tty locking
• 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]