From: Andrew Morton <akpm@osdl.org>
To: Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: Charles Edward Lever <chucklever@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: Yet another borken page_count() check in invalidate_inode_pages2()....
Date: Wed, 15 Nov 2006 11:24:26 -0800 [thread overview]
Message-ID: <20061115112426.84e5417c.akpm@osdl.org> (raw)
In-Reply-To: <1163613913.5691.215.camel@lade.trondhjem.org>
On Wed, 15 Nov 2006 13:05:13 -0500
Trond Myklebust <Trond.Myklebust@netapp.com> wrote:
> On Wed, 2006-11-15 at 08:46 -0800, Andrew Morton wrote:
>
> > but nobody could have started another writeback after the "..." because they
> > couldn't have got the lock_page(), and lock_page() is required for
> > ->writepage()?
>
> Nothing can have called writepage(), but something may be calling
> ->writepages(). That may call set_page_writeback without taking the page
> lock.
>
The protocol is
lock_page()
set_page_writeback()
->writepage()
and there are various places which assume that nobody will start new
writeout of a locked page. But I forget where they are - things have always
been this way.
If NFS is running set_page_writeback() against an unlocked page then I
don't know what will break. I didn't know it was doing that.
next prev parent reply other threads:[~2006-11-15 19:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-15 5:33 Trond Myklebust
2006-11-15 5:42 ` Andrew Morton
2006-11-15 13:18 ` Trond Myklebust
2006-11-15 16:46 ` Andrew Morton
2006-11-15 18:05 ` Trond Myklebust
2006-11-15 19:24 ` Andrew Morton [this message]
2006-11-15 20:57 ` Trond Myklebust
2006-11-15 21:12 ` Andrew Morton
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=20061115112426.84e5417c.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=Trond.Myklebust@netapp.com \
--cc=chucklever@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®