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 for Android: free password hash cracker in your pocket

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

Message-ID: <Pine.LNX.4.44L0.0705301057040.2564-100000@iolanthe.rowland.org>
Date:	Wed, 30 May 2007 10:57:44 -0400 (EDT)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Oleg Nesterov <oleg@...sign.ru>
cc:	linux-kernel@...r.kernel.org
Subject: Re: Sending signals to a kernel thread, broken in 2.6.22

On Wed, 30 May 2007, Oleg Nesterov wrote:

> > Please look at
> > 
> > 	change kernel threads to ignore signals instead of blocking them
> > 	commit: 10ab825bdef8df510f99c703a5a2d9b13a4e31a5
> > 
> > I think you can convert the code above to use allow_signal().
> 
> something like untested/uncompiled patch below, what do you think?

I tried it out, and it worked perfectly.  Thank you very much.

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/