linux-kernel - Re: Pull request: TASK

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: <1201830304.3087.2.camel@heimdal.trondhjem.org>
Date:	Thu, 31 Jan 2008 20:45:04 -0500
From:	Trond Myklebust <Trond.Myklebust@...app.com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Matthew Wilcox <matthew@....cx>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Liam Howlett <howlett@...il.com>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: Pull request: TASK_KILLABLE


On Fri, 2008-02-01 at 11:48 +1100, Linus Torvalds wrote:
> 
> On Thu, 31 Jan 2008, Matthew Wilcox wrote:
> > 
> > To allow tasks to be interrupted by fatal signals, we introduce a new
> > TASK_* bit; TASK_WAKEKILL.  We also add a predicate fatal_signal_pending;
> > the counterpart of signal_pending().  Then we add killable versions
> > of lock_page(), mutex_lock(), schedule_timeout(), wait_event(), and
> > wait_for_completion().  Finally, we can make the NFS 'intr' mount option
> > a no-op.
> 
> Ok, I've pulled this. It conflicted with some NFS changes, but I did what 
> appeared to be the obvious conflict resolution, and it all at least 
> compiles and it looked sane to me. But I don't have NFS enabled normally, 
> and I certainly don't have a good way to test with my laptop while in 
> Melbourne, so Trond/Matthew, can you please double- and triple-check my 
> merge?

Hmm... The current code won't compile as a module. We're at least going
to require something like the attached patch.

Cheers
  Trond

Download attachment "linux-2.6.24-000-export_fatal_signal_pending.dif" of type "message/rfc822" (804 bytes)