linux-kernel - 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-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.44L0.0705291649010.2974-100000@iolanthe.rowland.org>
Date:	Tue, 29 May 2007 16:55:09 -0400 (EDT)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Kernel development list <linux-kernel@...r.kernel.org>
Subject: 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 majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/