From: Linus Torvalds <torvalds@linux-foundation.org>
To: Matthew Wilcox <matthew@wil.cx>,
Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Liam Howlett <howlett@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: Pull request: TASK_KILLABLE
Date: Fri, 1 Feb 2008 11:48:44 +1100 (EST) [thread overview]
Message-ID: <alpine.LFD.1.00.0802011146180.3198@www.l.google.com> (raw)
In-Reply-To: <20080131234504.GB25967@parisc-linux.org>
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?
Linus
next prev parent reply other threads:[~2008-02-01 0:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-29 0:04 Matthew Wilcox
2008-01-29 11:41 ` Linus Torvalds
2008-01-31 23:45 ` Matthew Wilcox
2008-02-01 0:48 ` Linus Torvalds [this message]
2008-02-01 1:45 ` Trond Myklebust
2008-02-01 1:54 ` Linus Torvalds
2008-02-01 2:03 ` Trond Myklebust
2008-02-01 2:02 ` Andrew Morton
2008-02-06 2:19 ` Matthew Wilcox
2008-02-06 2:33 ` Andrew Morton
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=alpine.LFD.1.00.0802011146180.3198@www.l.google.com \
--to=torvalds@linux-foundation.org \
--cc=Trond.Myklebust@netapp.com \
--cc=akpm@linux-foundation.org \
--cc=howlett@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
/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
Powered by JetHome