[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <t4y7xtgfnzfpfupnb7on33n6qzrfxfphsm2hqsa5rx4liqvvbc@wwj7ckhyilpo>
Date: Mon, 13 Oct 2025 13:59:21 +0200
From: Jan Kara <jack@...e.cz>
To: Christoph Hellwig <hch@....de>
Cc: "Matthew Wilcox (Oracle)" <willy@...radead.org>,
Eric Van Hensbergen <ericvh@...nel.org>, Latchesar Ionkov <lucho@...kov.net>,
Dominique Martinet <asmadeus@...ewreck.org>, Christian Schoenebeck <linux_oss@...debyte.com>,
Chris Mason <clm@...com>, David Sterba <dsterba@...e.com>, Mark Fasheh <mark@...heh.com>,
Joel Becker <jlbec@...lplan.org>, Joseph Qi <joseph.qi@...ux.alibaba.com>,
Alexander Viro <viro@...iv.linux.org.uk>, Christian Brauner <brauner@...nel.org>,
Josef Bacik <josef@...icpanda.com>, Jan Kara <jack@...e.cz>, linux-block@...r.kernel.org,
v9fs@...ts.linux.dev, linux-btrfs@...r.kernel.org, linux-ext4@...r.kernel.org,
linux-fsdevel@...r.kernel.org, jfs-discussion@...ts.sourceforge.net,
ocfs2-devel@...ts.linux.dev, linux-xfs@...r.kernel.org, linux-mm@...ck.org
Subject: Re: [PATCH 07/10] mm: remove __filemap_fdatawrite
On Mon 13-10-25 11:58:02, Christoph Hellwig wrote:
> And rewrite filemap_fdatawrite to use filemap_fdatawrite_range instead
> to have a simpler call chain.
>
> Signed-off-by: Christoph Hellwig <hch@....de>
...
> int filemap_fdatawrite(struct address_space *mapping)
> {
> - return __filemap_fdatawrite(mapping, WB_SYNC_ALL);
> + return filemap_fdatawrite_range(mapping, 0, LONG_MAX);
As Damien pointed out, here should be LLONG_MAX.
> @@ -470,7 +464,7 @@ EXPORT_SYMBOL_GPL(filemap_fdatawrite_range_kick);
> */
> int filemap_flush(struct address_space *mapping)
> {
> - return __filemap_fdatawrite(mapping, WB_SYNC_NONE);
> + return filemap_fdatawrite_range_kick(mapping, 0, LLONG_MAX);
> }
> EXPORT_SYMBOL(filemap_flush);
filemap_fdatawrite_range_kick() doesn't exist at this point in the series.
Honza
--
Jan Kara <jack@...e.com>
SUSE Labs, CR
Powered by blists - more mailing lists