From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Christoph Hellwig <hch@infradead.org>
Cc: Dave Chinner <david@fromorbit.com>,
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: Wed, 16 Jul 2008 14:12:40 +1000 [thread overview]
Message-ID: <200807161412.40893.nickpiggin@yahoo.com.au> (raw)
In-Reply-To: <20080715122250.GA15744@infradead.org>
On Tuesday 15 July 2008 22:22, Christoph Hellwig wrote:
> > It would be easily possible to do, yes.
>
> What happened to your plans to merge ->nopfn into ->fault? Beeing
> able to restart page based faults would be a logical fallout from that.
Yeah I guess I should really do that, and you're right it would
work nicely for this.
Actually I have some code but it is not quite as nice as I'd like.
The problem is that we have the generic file fault handler, but not
a generic page mkwrite handler. So we still need some kind of
page_mkwrite aop which the file fault handler can then call if it
exists. It isn't a big problem AFAIKS, but just a bit irritating.
next prev parent reply other threads:[~2008-07-16 4:12 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
2008-07-15 12:22 ` Christoph Hellwig
2008-07-16 4:12 ` Nick Piggin [this message]
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=200807161412.40893.nickpiggin@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=david@fromorbit.com \
--cc=hch@infradead.org \
--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
Powered by JetHome