Home » Mailing list archives » linux-kernel » 2007 » May » 29

Sending signals to a kernel thread, broken in 2.6.22

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
[view in full thread]
From: Alan Stern <stern@...>
To: Kernel development list <linux-kernel@...>
Subject: Sending signals to a kernel thread, broken in 2.6.22
Date: Tuesday, May 29, 2007 - 4:55 pm

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

-
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
Messages in current thread:
Sending signals to a kernel thread, broken in 2.6.22, Alan Stern, (Tue May 29, 4:55 pm)
Re: Sending signals to a kernel thread, broken in 2.6.22, Nigel Cunningham, (Wed May 30, 8:38 am)
Re: Sending signals to a kernel thread, broken in 2.6.22, Rafael J. Wysocki, (Wed May 30, 4:09 pm)
Re: Sending signals to a kernel thread, broken in 2.6.22, Alan Stern, (Wed May 30, 10:51 am)
Re: Sending signals to a kernel thread, broken in 2.6.22, Nigel Cunningham, (Wed May 30, 6:22 pm)