From: Nick Piggin <npiggin@suse.de>
To: yawei niu <yawei.niu@gmail.com>
Cc: linux-fsdevel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [patch][rfc] change writepage prototype, introduce new page cleaning APIs
Date: Wed, 25 Feb 2009 10:43:36 +0100 [thread overview]
Message-ID: <20090225094336.GE22785@wotan.suse.de> (raw)
In-Reply-To: <9106c300902250140t33a22a25s6bf49e1b08736dd@mail.gmail.com>
On Wed, Feb 25, 2009 at 05:40:52PM +0800, yawei niu wrote:
> On Wed, Feb 25, 2009 at 4:47 PM, Nick Piggin <npiggin@suse.de> wrote:
>
> > Hi,
> >
> > I have a problem with writepage because the caller clears the page dirty
> > bit before calling the filesystem. I want to do proper refcounting on
> > filesystem metadata in fsblock, and this includes pinning the metadata
> > when it is dirty.
> Is it possible that two threads trigger writepage on same page in this way?
It shouldn't be, because the filesystem would have to hold page lock
over the operation and until it either clears dirty, or decides it is
not going to do the writeback. No different from the former rules in
that respect.
prev parent reply other threads:[~2009-02-25 9:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-25 8:47 [patch][rfc] change writepage prototype, introduce new page cleaning APIs Nick Piggin
[not found] ` <9106c300902250140t33a22a25s6bf49e1b08736dd@mail.gmail.com>
2009-02-25 9:43 ` Nick Piggin [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=20090225094336.GE22785@wotan.suse.de \
--to=npiggin@suse.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=yawei.niu@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).