Hi. On Tue, 2007-05-29 at 16:55 -0400, Alan Stern wrote: > The g_file_storage driver uses a kernel thread and communicates with > that thread in part by means of signals. It also relies on the thread > receiving signals from userspace as an indication that the thread > should terminate. > > This was all working in 2.6.21, but as of 2.6.22-rc3 the signal > delivery mechanism (entirely within the kernel!) is no longer > functional. > > What's the story? Do I need to do something new and different to get > signals working again? Should I avoid using signals entirely? > > Thanks for any help, > > Alan Stern Hmm. Given Oleg's reply, it could pay to check that freezable kernel threads are still being frozen. I'm about to go off to bed, and am away for half the day tomorrow, but will check as soon as I can if noone else gets to it first. (Rafael added for a heads-up, just in case he hasn't noticed this thread). Regards, Nigel
Attachment:
signature.asc
Description: This is a digitally signed message part
- Follow-Ups:
- Re: Sending signals to a kernel thread, broken in 2.6.22
- From: "Rafael J. Wysocki" <[email protected]>
- Re: Sending signals to a kernel thread, broken in 2.6.22
- From: Alan Stern <[email protected]>
- Re: Sending signals to a kernel thread, broken in 2.6.22
- References:
- Sending signals to a kernel thread, broken in 2.6.22
- From: Alan Stern <[email protected]>
- Sending signals to a kernel thread, broken in 2.6.22
- Prev by Date: Re: Sending signals to a kernel thread, broken in 2.6.22
- Next by Date: Kernel 2.6.20: possible circular locking dependency detected
- Previous by thread: 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):
 |