From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Dave Chinner <david@fromorbit.com>
Cc: Lachlan McIlroy <lachlan@sgi.com>,
Mikael Abrahamsson <swmike@swm.pp.se>,
linux-kernel@vger.kernel.org, xfs@oss.sgi.com,
linux-mm@kvack.org
Subject: Re: xfs bug in 2.6.26-rc9
Date: Tue, 15 Jul 2008 16:17:58 +1000 [thread overview]
Message-ID: <200807151617.58329.nickpiggin@yahoo.com.au> (raw)
In-Reply-To: <20080714121332.GX29319@disturbed>
On Monday 14 July 2008 22:13, Dave Chinner wrote:
> Christoph and I were contemplating this problem with ->page_mkwrite
> reecently. The problem is that we can't, right now, return an
> EAGAIN-like error to ->page_mkwrite() and have it retry the
> page fault. Other parts of the page faulting code can do this,
> so it seems like a solvable problem.
>
> The basic concept is that if we can return a EAGAIN result we can
> try-lock the inode and hold the locks necessary to avoid this race
> or prevent the page fault from dirtying the page until the
> filesystem is unfrozen.
>
> Added linux-mm to the cc list for discussion.
It would be easily possible to do, yes.
next prev parent reply other threads:[~2008-07-15 6:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-11 7:46 Mikael Abrahamsson
2008-07-11 8:42 ` Dave Chinner
2008-07-11 10:21 ` Mikael Abrahamsson
2008-07-14 7:30 ` Dave Chinner
2008-07-14 8:16 ` Mikael Abrahamsson
2008-07-14 7:34 ` Lachlan McIlroy
2008-07-14 12:13 ` Dave Chinner
2008-07-15 2:12 ` Lachlan McIlroy
2008-07-15 3:18 ` Dave Chinner
2008-07-15 6:17 ` Nick Piggin [this message]
2008-07-15 12:22 ` Christoph Hellwig
2008-07-16 4:12 ` Nick Piggin
2008-07-11 19:02 ` Sebastian Siewior
2008-07-11 19:52 ` Eric Sandeen
2008-07-11 23:22 ` Dave Chinner
2008-07-12 5:06 ` Sebastian Siewior
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=200807151617.58329.nickpiggin@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=david@fromorbit.com \
--cc=lachlan@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=swmike@swm.pp.se \
--cc=xfs@oss.sgi.com \
/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
all inboxes | Powered by JetHome®