From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Nick Piggin <npiggin@suse.de>
Cc: linux-fsdevel@vger.kernel.org, Rince <rincebrain@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org
Subject: Re: NFS BUG_ON in nfs_do_writepage
Date: Tue, 28 Apr 2009 07:59:38 -0400 [thread overview]
Message-ID: <1240919978.7376.7.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <20090428115449.GD9442@wotan.suse.de>
On Tue, 2009-04-28 at 13:54 +0200, Nick Piggin wrote:
> If the page gets cleaned after page_mkwrite and before the page
> table locks are taken again in order to set the pte writeable.
> (actually, page_mkclean only runs if it finds mapcount elevated,
> so it is enough to clean the page even after the locks are taken
> and before mapcount is incremented in the case of __do_fault).
OK. This was what I was missing...
Thanks!
prev parent reply other threads:[~2009-04-28 11:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.LFD.2.00.0904130145050.4396@centaur.acm.jhu.edu>
[not found] ` <20090412235010.c8e3475b.akpm@linux-foundation.org>
[not found] ` <1239650202.16771.15.camel@heimdal.trondhjem.org>
[not found] ` <5da0588e0904131506k5c58e8ddob9bf38f61da6302a@mail.gmail.com>
[not found] ` <5da0588e0904131644g131dc816r61884e83bc4cd006@mail.gmail.com>
[not found] ` <5da0588e0904240226j3454941y5f58c17a32a9a23d@mail.gmail.com>
[not found] ` <1240671428.6112.1.camel@heimdal.trondhjem.org>
[not found] ` <1240671428.6112.1.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-04-26 6:40 ` NFS BUG_ON in nfs_do_writepage Nick Piggin
2009-04-26 14:18 ` Trond Myklebust
2009-04-26 15:13 ` Nick Piggin
2009-04-26 17:55 ` Trond Myklebust
[not found] ` <1240768522.10548.33.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-04-28 4:27 ` Nick Piggin
[not found] ` <20090428042717.GA6304-B4tOwbsTzaBolqkO4TVVkw@public.gmane.org>
2009-04-28 11:45 ` Trond Myklebust
2009-04-28 11:54 ` Nick Piggin
2009-04-28 11:59 ` Trond Myklebust [this message]
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=1240919978.7376.7.camel@heimdal.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=npiggin@suse.de \
--cc=rincebrain@gmail.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;
as well as URLs for NNTP newsgroup(s).