From: Chris Mason <chris.mason@oracle.com>
To: Nick Piggin <npiggin@suse.de>
Cc: Linux Memory Management List <linux-mm@kvack.org>,
linux-fsdevel@vger.kernel.org
Subject: Re: [rfc][patch 2/2] buffer, btrfs: fix page_mkwrite error cases
Date: Tue, 03 Mar 2009 09:26:03 -0500 [thread overview]
Message-ID: <1236090363.782.6.camel@think.oraclecorp.com> (raw)
In-Reply-To: <20090303104114.GD17042@wotan.suse.de>
On Tue, 2009-03-03 at 11:41 +0100, Nick Piggin wrote:
> page_mkwrite is called with neither the page lock nor the ptl held. This
> means a page can be concurrently truncated or invalidated out from underneath
> it. Callers are supposed to prevent truncate races themselves, however
> previously the only thing they can do in case they hit one is to raise a
> SIGBUS. A sigbus is wrong for the case that the page has been invalidated
> or truncated within i_size (eg. hole punched). Callers may also have to
> perform memory allocations in this path, where again, SIGBUS would be wrong.
>
> The previous patch made it possible to properly specify errors. Convert
> the generic buffer.c code and btrfs to return sane error values
> (in the case of page removed from pagecache, VM_FAULT_NOPAGE will cause the
> fault handler to exit without doing anything, and the fault will be retried
> properly).
>
Thanks Nick. I think the btrfs patch needs an extra } to compile, but
it looks fine.
-chris
next prev parent reply other threads:[~2009-03-03 14:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-03 10:38 [patch 1/2] mm: page_mkwrite change prototype to match fault Nick Piggin
2009-03-03 10:41 ` [rfc][patch 2/2] buffer, btrfs: fix page_mkwrite error cases Nick Piggin
2009-03-03 14:26 ` Chris Mason [this message]
2009-03-03 14:41 ` Nick Piggin
2009-03-03 14:47 ` Chris Mason
2009-03-03 12:39 ` [patch 1/2] mm: page_mkwrite change prototype to match fault steve
2009-03-03 15:58 ` Christoph Hellwig
2009-03-04 10:21 ` Nick Piggin
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=1236090363.782.6.camel@think.oraclecorp.com \
--to=chris.mason@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=npiggin@suse.de \
/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).