From: "NeilBrown" <neilb@suse.de>
To: "Christoph Hellwig" <hch@lst.de>
Cc: "Christoph Hellwig" <hch@lst.de>,
linux-raid@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] md: stop using do_sync_mapping_range
Date: Sun, 27 Sep 2009 07:51:17 +1000 [thread overview]
Message-ID: <9d44977545b3d447e4c7a1a84b594562.squirrel@neil.brown.name> (raw)
In-Reply-To: <20090926151354.GD11623@lst.de>
On Sun, September 27, 2009 1:13 am, Christoph Hellwig wrote:
> On Thu, Sep 24, 2009 at 08:52:36AM +1000, Neil Brown wrote:
>> On Wednesday September 23, hch@lst.de wrote:
>> > It's a very awkward way to write out all data and wait for it, so just
>> > call filemap_write_and_wait. I still can't figure what the point of
>> > all this is, so a comment would surely be helpful.
>>
>> When md/bitmap accesses a file, it uses bmap to find addresses and then
>> submit_bh to do IO, so it completely by-passes the page cache.
>> So this code is present to ensure that the page cache has no dirty
>> pages for the file before we start using the file.
>>
>> I don't recall exactly why I used do_sync_mapping_range. I suspect
>> that I looked at what "sys_fsync" used (do_fsync?) and found that
>> wasn't exported, so I looked at what sys_sync_file_range used, found
>> that was exported, and so used that.
>>
>> Looking at the current state of the VFS, I think I would rather use
>> vfs_fsync.
>
> Using vfs_fsync is better, but using bmap is extremly dangerous, I'm
> kinda suprised how this managed to get sneaked in without notice. bmap
> really is just an advisory interface as the mappings by change
> underneath all the time. Some modern filesystems like btrfs really
> can't implement it at all.
>
I used bmap because I wanted writeout characteristics similar to
swapout, and mm/swapfile.c uses bmap. I copied the ideas from that
code. If bmap is unsafe for bitmap files, then presumably it is
unsafe for swap files too.
This is exactly the argument that I used when Andrew Morton queried
the code on the way in.
The swap-over-NFS patches introduce a new interface to the filesystem
that supports swapout (i.e. writeout that is guaranteed not to block
on mem allocation etc). If they ever get upstream, I will change
bitmap files to use that interface when it is present.
>
>> So would you be happy with something like the following?
>
> It's at least a small improvement..
Thanks.
NeilBrown
prev parent reply other threads:[~2009-09-26 21:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-23 13:18 [PATCH] md: stop using do_sync_mapping_range Christoph Hellwig
2009-09-23 13:47 ` Jamie Lokier
2009-09-26 15:11 ` Christoph Hellwig
2009-09-23 22:52 ` Neil Brown
2009-09-26 15:13 ` Christoph Hellwig
2009-09-26 21:51 ` NeilBrown [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=9d44977545b3d447e4c7a1a84b594562.squirrel@neil.brown.name \
--to=neilb@suse.de \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-raid@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;
as well as URLs for NNTP newsgroup(s).