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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1180528720.3976.42.camel@nigel.suspend2.net>
Date:	Wed, 30 May 2007 22:38:40 +1000
From:	Nigel Cunningham <nigel@...el.suspend2.net>
To:	Alan Stern <stern@...land.harvard.edu>,
	"Rafael J. Wysocki" <rjw@...k.pl>
Cc:	Kernel development list <linux-kernel@...r.kernel.org>
Subject: Re: Sending signals to a kernel thread, broken in 2.6.22

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

Download attachment "signature.asc" of type "application/pgp-signature" (190 bytes)