From: Matthew Wilcox <willy@infradead.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH v2 2/4] mm: add file_fdatawait_range and file_write_and_wait
Date: Wed, 26 Jul 2017 12:13:05 -0700 [thread overview]
Message-ID: <20170726191305.GC15980@bombadil.infradead.org> (raw)
In-Reply-To: <20170726175538.13885-3-jlayton@kernel.org>
On Wed, Jul 26, 2017 at 01:55:36PM -0400, Jeff Layton wrote:
> +int file_write_and_wait(struct file *file)
> +{
> + int err = 0, err2;
> + struct address_space *mapping = file->f_mapping;
> +
> + if ((!dax_mapping(mapping) && mapping->nrpages) ||
> + (dax_mapping(mapping) && mapping->nrexceptional)) {
Since patch 1 exists, shouldn't this use the new helper?
> + err = filemap_fdatawrite(mapping);
> + /* See comment of filemap_write_and_wait() */
> + if (err != -EIO) {
> + loff_t i_size = i_size_read(mapping->host);
> +
> + if (i_size != 0)
> + __filemap_fdatawait_range(mapping, 0,
> + i_size - 1);
> + }
> + }
> + err2 = file_check_and_advance_wb_err(file);
> + if (!err)
> + err = err2;
> + return err;
Would this be clearer written as:
if (err)
return err;
return err2;
or even ...
return err ? err : err2;
next prev parent reply other threads:[~2017-07-26 19:13 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-26 17:55 [Cluster-devel] [PATCH v2 0/4] mm/gfs2: extend file_* API, and convert gfs2 to errseq_t error reporting Jeff Layton
2017-07-26 17:55 ` [Cluster-devel] [PATCH v2 1/4] mm: consolidate dax / non-dax checks for writeback Jeff Layton
2017-07-27 8:43 ` Jan Kara
2017-07-26 17:55 ` [Cluster-devel] [PATCH v2 2/4] mm: add file_fdatawait_range and file_write_and_wait Jeff Layton
2017-07-26 19:13 ` Matthew Wilcox [this message]
2017-07-26 22:18 ` Jeff Layton
2017-07-26 19:50 ` Bob Peterson
2017-07-27 8:49 ` Jan Kara
2017-07-27 12:48 ` Jeff Layton
2017-07-31 11:27 ` Jeff Layton
2017-07-31 11:32 ` Steven Whitehouse
2017-07-31 11:44 ` Jeff Layton
2017-07-31 12:05 ` Steven Whitehouse
2017-07-31 12:22 ` Jeff Layton
2017-07-31 12:25 ` Steven Whitehouse
2017-07-31 12:38 ` Bob Peterson
2017-07-31 12:07 ` Jan Kara
2017-07-31 13:00 ` Jeff Layton
2017-07-31 13:32 ` Jan Kara
2017-07-31 16:49 ` [Cluster-devel] [PATCH v3] " Jeff Layton
2017-08-01 9:52 ` Jan Kara
2017-07-26 17:55 ` [Cluster-devel] [PATCH v2 3/4] fs: convert sync_file_range to use errseq_t based error-tracking Jeff Layton
2017-07-26 17:55 ` [Cluster-devel] [PATCH v2 4/4] gfs2: convert to errseq_t based writeback error reporting for fsync Jeff Layton
2017-07-26 19:21 ` Matthew Wilcox
2017-07-26 22:22 ` Jeff Layton
2017-07-27 12:47 ` Bob Peterson
2017-07-28 12:37 ` Steven Whitehouse
2017-07-28 12:47 ` Jeff Layton
2017-07-28 12:54 ` Steven Whitehouse
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=20170726191305.GC15980@bombadil.infradead.org \
--to=willy@infradead.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).