From: Mikulas Patocka <mpatocka@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Niels de Vos <ndevos@redhat.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Al Viro <viro@zeniv.linux.org.uk>, Jeff Moyer <jmoyer@redhat.com>,
"Bryn M. Reeves" <bmr@redhat.com>
Subject: Re: [PATCH v3] fs: Invalidate the cache for a parent block-device if fsync() is called for a partition
Date: Thu, 26 Jan 2012 17:13:29 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.64.1201261651090.28710@hs20-bc2-1.build.redhat.com> (raw)
In-Reply-To: <20120126134051.6add3cd2.akpm@linux-foundation.org>
On Thu, 26 Jan 2012, Andrew Morton wrote:
> On Thu, 26 Jan 2012 13:33:22 +0000
> Niels de Vos <ndevos@redhat.com> wrote:
>
> > Executing an fsync() on a file-descriptor of a partition flushes the
> > caches for that partition by calling blkdev_fsync(). However, it seems
> > that reading data through the parent device will still return the old
> > cached data.
> >
> > The problem can be worked around by forcing the caches to be flushed
> > with either
> > # blockdev --flushbufs ${dev_disk}
> > or
> > # echo 3 > /proc/sys/vm/drop_caches
> >
> > One of the use-cases that shows this problem:
> > 1) create two or more partitions on a device
> > - use fdisk to create /dev/sdb1 and /dev/sdb2
> > 2) format and mount one of the partition
> > - mkfs -t ext3 /dev/sdb1
> > 3) read through the main device to have something in the cache
> > - read /dev/sdb with dd or use something like "parted /dev/sdb print"
> > 4) now write something to /dev/sdb2, format the partition for example
> > - mkfs -t ext3 /dev/sdb2
> > 5) read the blocks where sdb2 starts, through /dev/sdb
> > - use dd or do again a "parted /dev/sdb print"
> >
> > The cache for the block-device is not synced if the block-device is kept
> > open (due to a mounted partition, for example). Only when all users for
> > the disk have exited, the cache for the disk is made consistent again.
> >
> > Without this patch, calling "blockdev --flushbufs" or dropping the
> > caches, the result in 5) is the same as in 3). Reading the same area
> > through /dev/sdb2 shows the inconsistancy between the two caches.
> >
> > ...
> >
> > --- a/fs/block_dev.c
> > +++ b/fs/block_dev.c
> > @@ -424,6 +424,10 @@ int blkdev_fsync(struct file *filp, loff_t start, loff_t end, int datasync)
> > if (error == -EOPNOTSUPP)
> > error = 0;
> >
> > + /* invalidate parent block_device */
> > + if (!error && bdev != bdev->bd_contains)
> > + invalidate_bdev(bdev->bd_contains);
> > +
> > return error;
> > }
> > EXPORT_SYMBOL(blkdev_fsync);
>
> I can't say I'm a huge fan of this. It just isn't logical to drop
> /dev/sda's pagecache in here.
>
> We're adapting the kernel to the behavior of existing userspace by
> inserting a useful side-effect into a suprising place. The result is
> pretty darned hacky.
>
> The Right Thing To Do here is to make the kernel behave logically and
> predictably, then modify the userspace tools. But if we're modifying
> the userspace tools then we would just change userspace to issue a
> BLKFLSBUF to /dev/sda and leave the kernel alone.
And how should userspace find out if the device is a partition and what is
the master device? For example, if I tell you that you have a block
device with major 259 and minor 2, how will you find out:
1) is it a partition or not?
2) what is the whole-disk device?
Do you think that userspace should recursively scan /sys/block to find out
disk-partition relationships?
> So hm. I think I might prefer to leave the issue unfixed rather than
> doing this to the poor old kernel :(
The major problem here is that "invalidate_bdev" is unreliable.
"invalidate_bdev" skips blocks that are beign read or written. udev may
open and read any block device anytime. Consequently, "invalidate_bdev"
may skip to invalidate any block device anytime (if it happens to be
racing with udev).
But this problem is irrelevant w.r.t the patch - the patch makes it
neither better nor worse. If someone executes "blockdev --flushbufs" or
ioctl BLKFLSBUF, it may not flush all buffers.
If you want to make the kernel behave predictably, you should fix
"invalidate_bdev" so that it invalidates the whole device, even if someone
is readint it.
Mikulas
next prev parent reply other threads:[~2012-01-26 22:13 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-20 1:58 [PATCH] block: Invalidate the cache for a parent block-device Mikulas Patocka
2012-01-20 9:35 ` Niels de Vos
2012-01-23 10:38 ` [PATCH v2] fs: Invalidate the cache for a parent block-device if fsync() is called for a partition Niels de Vos
2012-01-23 16:27 ` Jeff Moyer
2012-01-23 16:46 ` Niels de Vos
2012-01-23 19:23 ` Mikulas Patocka
2012-01-23 20:04 ` Jeff Moyer
2012-01-26 10:03 ` Andrew Morton
2012-01-26 11:50 ` Niels de Vos
2012-01-26 13:33 ` [PATCH v3] " Niels de Vos
2012-01-26 21:40 ` Andrew Morton
2012-01-26 21:45 ` Christoph Hellwig
2012-01-26 21:50 ` Mikulas Patocka
2012-01-27 12:19 ` Ric Wheeler
2012-01-31 16:00 ` Niels de Vos
2012-01-31 18:58 ` Andrew Morton
2012-01-31 19:04 ` Christoph Hellwig
2012-01-31 19:32 ` Andrew Morton
2012-01-31 19:37 ` Christoph Hellwig
2012-01-31 19:48 ` Andrew Morton
2012-01-26 21:49 ` Jeff Moyer
2012-01-26 22:13 ` Mikulas Patocka [this message]
2012-01-26 22:26 ` Kernel Oops report (Android gingerbread) Fan Zhang
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=Pine.LNX.4.64.1201261651090.28710@hs20-bc2-1.build.redhat.com \
--to=mpatocka@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=bmr@redhat.com \
--cc=jmoyer@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ndevos@redhat.com \
--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).