Re: Sending signals to a kernel thread, broken in 2.6.22

On Wed, 30 May 2007, Nigel Cunningham wrote:

> Hmm. Given Oleg's reply, it could pay to check that freezable kernel
> threads are still being frozen.

I don't think we have to worry about this.  See this discussion thread:

	http://marc.info/?t=118045713200006&r=1&w=2

and in particular this message:

	http://marc.info/?l=linux-kernel&m=118046964817995&w=2

Alan Stern

-
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: Sending signals to a kernel thread, broken in 2.6.22
    • From: Nigel Cunningham <[email protected]>

• References:
  • Re: Sending signals to a kernel thread, broken in 2.6.22
    • From: Nigel Cunningham <[email protected]>

• Prev by Date: [PATCH] Performance Stats: Kernel patch
• Next by Date: Re: joydev.c and saitek cyborg evo force
• Previous by thread: Re: Sending signals to a kernel thread, broken in 2.6.22
• Next by thread: Re: Sending signals to a kernel thread, broken in 2.6.22
• 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]