From: Christoph Hellwig <hch@infradead.org>
To: Chris Mason <chris.mason@oracle.com>,
Nick Piggin <npiggin@suse.de>,
Trond Myklebust <trond.myklebust@fys.uio.no>,
Miklos Szeredi <miklos@szeredi.hu>,
holt@sgi.com, linux-nfs@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: Why doesn't zap_pte_range() call page_mkwrite()
Date: Tue, 8 Sep 2009 22:21:02 -0400 [thread overview]
Message-ID: <20090909022102.GA28318@infradead.org> (raw)
In-Reply-To: <20090908153007.GB2513@think>
On Tue, Sep 08, 2009 at 11:30:07AM -0400, Chris Mason wrote:
> Sorry for digging up an old thread, but is there any reason we can't
> just use page_mkwrite here? I'd love to get rid of the btrfs code to
> detect places that use set_page_dirty without a page_mkwrite.
It's not just btrfs, it's also a complete pain in the a** for XFS and
probably every filesystems using ->page_mkwrite for dirty page tracking.
--
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:[~2009-09-09 2:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1240510668.11148.40.camel@heimdal.trondhjem.org>
[not found] ` <E1Lx4yU-0007A8-Gl@pomaz-ex.szeredi.hu>
[not found] ` <1240519320.5602.9.camel@heimdal.trondhjem.org>
2009-04-24 7:15 ` Why doesn't zap_pte_range() call page_mkwrite() Miklos Szeredi
2009-04-24 7:33 ` Miklos Szeredi
2009-04-24 12:59 ` Chris Mason
2009-04-24 13:31 ` Trond Myklebust
2009-04-24 14:06 ` Trond Myklebust
2009-04-24 16:18 ` Jamie Lokier
2009-04-24 10:41 ` Robin Holt
2009-04-24 14:52 ` Miklos Szeredi
2009-04-24 17:00 ` Trond Myklebust
2009-04-25 5:10 ` Nick Piggin
2009-09-08 15:30 ` Chris Mason
2009-09-08 15:41 ` Nick Piggin
2009-09-08 16:31 ` Chris Mason
2009-09-08 17:00 ` Nick Piggin
2009-09-08 17:00 ` Nick Piggin
2009-09-08 15:41 ` Nick Piggin
2009-09-09 2:21 ` Christoph Hellwig [this message]
2009-09-09 5:39 ` Nick Piggin
2009-09-09 2:21 ` Christoph Hellwig
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=20090909022102.GA28318@infradead.org \
--to=hch@infradead.org \
--cc=chris.mason@oracle.com \
--cc=holt@sgi.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=npiggin@suse.de \
--cc=trond.myklebust@fys.uio.no \
/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).