linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Mason <clm@fb.com>
To: Benjamin LaHaise <bcrl@kvack.org>
Cc: <linux-fsdevel@vger.kernel.org>, <linux-aio@kvack.org>,
	Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH RFC] fs/aio: fix sleeping while TASK_INTERRUPTIBLE
Date: Tue, 13 Jan 2015 11:20:20 -0500	[thread overview]
Message-ID: <1421166020.21014.7@mail.thefacebook.com> (raw)
In-Reply-To: <20150113160633.GC25742@kvack.org>



On Tue, Jan 13, 2015 at 11:06 AM, Benjamin LaHaise <bcrl@kvack.org> 
wrote:
> Hi Chris,
> 
> On Mon, Dec 22, 2014 at 07:16:25PM -0500, Chris Mason wrote:
>>  The 3.19 merge window brought in a great new warning to catch 
>> someone
>>  calling might_sleep with their state != TASK_RUNNING.  The idea was 
>> to
>>  find buggy code locking mutexes after calling prepare_to_wait(), 
>> kind
>>  of like this:
> ...
>>  This has been lightly tested and hasn't been benchmarked, so RFC for
>>  now.
>> 
>>  Signed-off-by: Chris Mason <clm@fb.com>
>>  Reported-by: The code of Peter Zijlstra <peterz@infradead.org>
> 
> After mulling this over, I think your patch is probably the safest 
> for us
> to apply at present as it is also the most amenable to backporting.  
> Are
> you okay with removing the RFC status?  I still have my concerns about
> possible task wakeups causing problems with filesystem code if the
> copy_to_user() takes a page fault, but those can be addressed 
> separately.
> Kent's closures are an option for the future, but I think it would be
> more appropriate for that new code to be introduced in the next merge
> window.

I'll resend the patch with improved comments, and get perf tests done 
on fast storage.

-chris

--
To unsubscribe, send a message with 'unsubscribe linux-aio' in
the body to majordomo@kvack.org.  For more info on Linux AIO,
see: http://www.kvack.org/aio/
Don't email: <a href=mailto:"aart@kvack.org">aart@kvack.org</a>

  reply	other threads:[~2015-01-13 16:20 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-23  0:16 [PATCH RFC] fs/aio: fix sleeping while TASK_INTERRUPTIBLE Chris Mason
2014-12-23 18:43 ` Benjamin LaHaise
2014-12-23 18:55   ` Chris Mason
2014-12-23 21:58     ` Benjamin LaHaise
2014-12-25  2:59       ` Kent Overstreet
2014-12-25  3:11         ` Benjamin LaHaise
2014-12-25  3:29           ` Kent Overstreet
2014-12-29  1:24           ` Chris Mason
2014-12-25  2:56 ` Kent Overstreet
2014-12-25 14:27   ` Sedat Dilek
2015-01-04 10:16     ` Sedat Dilek
2014-12-29 15:08   ` Chris Mason
2014-12-29 22:08     ` Kent Overstreet
2015-01-13 16:06 ` Benjamin LaHaise
2015-01-13 16:20   ` Chris Mason [this message]
2015-01-21 10:13 ` Dave Chinner
2015-01-21 21:42   ` Chris Mason
2015-02-03  9:14     ` Sedat Dilek
2015-02-03  9:54       ` Sedat Dilek
2015-02-09  3:08     ` Sedat Dilek
2015-02-09  4:21       ` Sedat Dilek

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=1421166020.21014.7@mail.thefacebook.com \
    --to=clm@fb.com \
    --cc=bcrl@kvack.org \
    --cc=linux-aio@kvack.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=peterz@infradead.org \
    /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;
as well as URLs for NNTP newsgroup(s).