From: Jeff Layton <jlayton@redhat.com>
To: NeilBrown <neilb@suse.com>, "Yan, Zheng" <zyan@redhat.com>,
Sage Weil <sage@redhat.com>, Ilya Dryomov <idryomov@gmail.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: [PATCH 2/2] cephfs: remove warning when ceph_releasepage() is called on dirty page.
Date: Wed, 31 Aug 2016 09:48:22 -0400 [thread overview]
Message-ID: <1472651302.5795.6.camel@redhat.com> (raw)
In-Reply-To: <87y43dd4oe.fsf@notabene.neil.brown.name>
On Wed, 2016-08-31 at 12:59 +1000, NeilBrown wrote:
> If O_DIRECT writes are racing with buffered writes, then
> the call to invalidate_inode_pages2_range() can call ceph_releasepage()
> on dirty pages.
>
> Most filesystems hold inode_lock() across O_DIRECT writes so they do not
> suffer this race, but cephfs deliberately drops the lock, and opens a window
> for the race.
>
> This race can be triggered with the generic/036 test from the xfstests
> test suite. It doesn't happen every time, but it does happen often.
>
> As the possibilty is expected, remove the warning, and instead include
> the PageDirty() status in the debug message.
>
> > Signed-off-by: NeilBrown <neilb@suse.com>
> ---
> fs/ceph/addr.c | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/fs/ceph/addr.c b/fs/ceph/addr.c
> index d5b6f959a3c3..f657da7d12ff 100644
> --- a/fs/ceph/addr.c
> +++ b/fs/ceph/addr.c
> @@ -175,9 +175,8 @@ static void ceph_invalidatepage(struct page *page, unsigned int offset,
>
> static int ceph_releasepage(struct page *page, gfp_t g)
> {
> > - dout("%p releasepage %p idx %lu\n", page->mapping->host,
> > - page, page->index);
> > - WARN_ON(PageDirty(page));
> > + dout("%p releasepage %p idx %lu (%sdirty)\n", page->mapping->host,
> > + page, page->index, PageDirty(page) ? "" : "not ");
>
> > /* Can we release the page from the cache? */
> > if (!ceph_release_fscache_page(page, g))
Reviewed-by: Jeff Layton <jlayton@redhat.com>
next prev parent reply other threads:[~2016-08-31 13:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-31 2:56 [PATCH 0/2]: CEPHFS: allow for races between direct and buffered writes NeilBrown
2016-08-31 2:58 ` [PATCH 1/2] cephfs: ignore error from invalidate_inode_pages2_range() in direct write NeilBrown
2016-08-31 13:47 ` Jeff Layton
2016-09-01 1:01 ` NeilBrown
2016-08-31 2:59 ` [PATCH 2/2] cephfs: remove warning when ceph_releasepage() is called on dirty page NeilBrown
2016-08-31 13:48 ` Jeff Layton [this message]
2016-08-31 9:19 ` [PATCH 0/2]: CEPHFS: allow for races between direct and buffered writes Yan, Zheng
2016-09-01 1:13 ` NeilBrown
2016-09-01 14:30 ` Yan, Zheng
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=1472651302.5795.6.camel@redhat.com \
--to=jlayton@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=idryomov@gmail.com \
--cc=neilb@suse.com \
--cc=sage@redhat.com \
--cc=zyan@redhat.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