Sending signals to a kernel thread, broken in 2.6.22

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

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

Prev by Date: Re: [PATCH] Kconfig powernow-k8 driver should depend on ACPI P-States driver
Next by Date: Re: CPU hotplug: system hang on CPU hot remove during `pfmon --system-wide'
Previous by thread: [PATCH] xen_start_kernel is __init, so startup_xen should be too
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]