From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: nigel@nigel.suspend2.net
Cc: Alan Stern <stern@rowland.harvard.edu>,
Kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: Sending signals to a kernel thread, broken in 2.6.22
Date: Wed, 30 May 2007 22:09:20 +0200 [thread overview]
Message-ID: <200705302209.20963.rjw@sisk.pl> (raw)
In-Reply-To: <1180528720.3976.42.camel@nigel.suspend2.net>
On Wednesday, 30 May 2007 14:38, Nigel Cunningham wrote:
> 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 think they are. Otherwise the freezer would have been failing.
> 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).
I have noticed it, but thanks anyway. :-)
Greetings,
Rafael
next prev parent reply other threads:[~2007-05-30 20:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-29 20:55 Sending signals to a kernel thread, broken in 2.6.22 Alan Stern
2007-05-30 12:38 ` Nigel Cunningham
2007-05-30 14:51 ` Alan Stern
2007-05-30 22:22 ` Nigel Cunningham
2007-05-30 20:09 ` Rafael J. Wysocki [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-05-30 11:22 Oleg Nesterov
2007-05-30 12:33 ` Oleg Nesterov
2007-05-30 14:57 ` Alan Stern
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200705302209.20963.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=nigel@nigel.suspend2.net \
--cc=stern@rowland.harvard.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox