From: Christoph Hellwig <hch@infradead.org>
To: David Chinner <dgc@sgi.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
nickpiggin@yahoo.com.au
Subject: Re: [PATCH 1 of 2] block_page_mkwrite() Implementation V2
Date: Mon, 19 Mar 2007 09:22:22 +0000 [thread overview]
Message-ID: <20070319092222.GA1720@infradead.org> (raw)
In-Reply-To: <20070318233008.GA32597093@melbourne.sgi.com>
On Mon, Mar 19, 2007 at 10:30:08AM +1100, David Chinner wrote:
>
> Generic page_mkwrite functionality.
>
> Filesystems that make use of the VM ->page_mkwrite() callout will generally use
> the same core code to implement it. There are several tricky truncate-related
> issues that we need to deal with here as we cannot take the i_mutex as we
> normally would for these paths. These issues are not documented anywhere yet
> so block_page_mkwrite() seems like the best place to start.
This will need some updates when ->fault replaces ->page_mkwrite.
Nich, what's the plan for merging ->fault?
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2007-03-19 9:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-18 23:30 David Chinner
2007-03-19 6:37 ` Nick Piggin
2007-03-19 8:12 ` David Chinner
2007-03-19 9:57 ` Nick Piggin
2007-03-19 10:28 ` Nick Piggin
2007-03-19 9:22 ` Christoph Hellwig [this message]
2007-03-19 10:11 ` Nick Piggin
2007-03-19 12:22 ` Christoph Hellwig
2007-03-20 5:34 ` Nick Piggin
2007-05-16 10:19 ` David Howells
2007-05-16 11:59 ` Nick Piggin
2007-05-16 12:09 ` David Woodhouse
2007-05-16 12:53 ` Chris Mason
2007-05-16 13:04 ` Nick Piggin
2007-05-16 13:10 ` Chris Mason
2007-05-16 13:20 ` David Howells
2007-05-16 13:41 ` Nick Piggin
2007-05-16 13:25 ` David Howells
2007-05-16 23:28 ` David Chinner
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=20070319092222.GA1720@infradead.org \
--to=hch@infradead.org \
--cc=dgc@sgi.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nickpiggin@yahoo.com.au \
/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