From: Nick Piggin <npiggin@suse.de>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: 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: Sat, 25 Apr 2009 07:10:28 +0200 [thread overview]
Message-ID: <20090425051028.GC10088@wotan.suse.de> (raw)
In-Reply-To: <1240592448.4946.35.camel@heimdal.trondhjem.org>
On Fri, Apr 24, 2009 at 01:00:48PM -0400, Trond Myklebust wrote:
> On Fri, 2009-04-24 at 16:52 +0200, Miklos Szeredi wrote:
> > On Fri, 24 Apr 2009, Robin Holt wrote:
> > > I am not sure how you came to this conclusion. The address_space has
> > > the vma's chained together and protected by the i_mmap_lock. That is
> > > acquired prior to the cleaning operation. Additionally, the cleaning
> > > operation walks the process's page tables and will remove/write-protect
> > > the page before releasing the i_mmap_lock.
> > >
> > > Maybe I misunderstand. I hope I have not added confusion.
> >
> > Looking more closely, I think you're right.
> >
> > I thought that detach_vmas_to_be_unmapped() also removed them from
> > mapping->i_mmap, but that is not the case, it only removes them from
> > the process's mm_struct. The vma is only removed from ->i_mmap in
> > unmap_region() _after_ zapping the pte's.
> >
> > This means that while the pte zapping is going on, any page faults
> > will fail but page_mkclean() (and all of rmap) will continue to work.
> >
> > But then I don't see how we get a dirty pte without also first getting
> > a page fault. Weird...
>
> You don't, but unless you unmap the page when you write it out, you will
> not get any further page faults. The VM will just redirty the page
> without calling page_mkwrite().
Why? It should call page_mkwrite...
> As I said, I think I can fix the NFS problem by simply unmapping the
> page inside ->writepage() whenever we know the write request was
> originally set up by a page fault.
The biggest outstanding problem we have remaining is get_user_pages.
Callers are only required to hold a ref on the page and then they
can call set_page_dirty at any point after that.
I have a half-done patch somewhere to add a put_user_pages, and then
we could probably go from there to pinning the fs metadata (whether
by using the page lock or something else, I don't quite know).
--
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-04-25 5:10 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 [this message]
2009-09-08 15:30 ` Chris Mason
2009-09-08 15:41 ` Nick Piggin
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-09 2:21 ` Christoph Hellwig
2009-09-09 2:21 ` Christoph Hellwig
2009-09-09 5:39 ` 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=20090425051028.GC10088@wotan.suse.de \
--to=npiggin@suse.de \
--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=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).