linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Moyer <jmoyer@redhat.com>
To: MITSUNARI Shigeo <herumi@nifty.com>
Cc: linux-fsdevel@vger.kernel.org,
	Alexander Viro <viro@zeniv.linux.org.uk>,
	linux-kernel@vger.kernel.org, Jens Axboe <axboe@kernel.dk>
Subject: Re: fs: page cache wrongly left invalidated after revalidate_disk
Date: Wed, 24 Oct 2012 09:44:23 -0400	[thread overview]
Message-ID: <x491ugo6l3c.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <28086318.27561350944959337.herumi@nifty.com> (MITSUNARI Shigeo's message of "Tue, 23 Oct 2012 07:29:19 +0900 (JST)")

MITSUNARI Shigeo <herumi@nifty.com> writes:

> Hi, 
>
> We found that bdev->bd_invalidated was left set once revalidate_disk() 
> is called, which results in page cache flush every time that device 
> is open. 
>
> Specifically, we found this problem in MD block device.  Once we 
> resize a MD device, mdadm --monitor periodically flush all page cache 
> for that device every 60 or 1000 seconds when it opens the device. 
>
> This bug lies since at least 3.2.0 till the latest kernel(3.6.2). 
> Patch is attached. 
>
> Anyone please review this?  Thanks in advance.

rescan_partitions (called in the bdev open path) should reset
bd_invalidated.  I think you need to dig into why that isn't happening.

Cheers,
Jeff

  reply	other threads:[~2012-10-24 13:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-22 22:29 fs: page cache wrongly left invalidated after revalidate_disk MITSUNARI Shigeo
2012-10-24 13:44 ` Jeff Moyer [this message]
2012-10-24 21:11   ` MITSUNARI Shigeo
2012-10-24 23:39   ` 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=x491ugo6l3c.fsf@segfault.boston.devel.redhat.com \
    --to=jmoyer@redhat.com \
    --cc=axboe@kernel.dk \
    --cc=herumi@nifty.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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).