From: Jeff Layton <jlayton@kernel.org>
To: viro@zeniv.linux.org.uk, akpm@linux-foundation.org
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-api@vger.kernel.org, andres@anarazel.de,
willy@infradead.org, dhowells@redhat.com, hch@infradead.org,
jack@suse.cz, david@fromorbit.com
Subject: [PATCH v6 RESEND 0/2] vfs: have syncfs() return error when there are writeback errors
Date: Tue, 28 Apr 2020 09:51:53 -0400 [thread overview]
Message-ID: <20200428135155.19223-1-jlayton@kernel.org> (raw)
Just a resend since this hasn't been picked up yet. No real changes
from the last set (other than adding Jan's Reviewed-bys). Latest
cover letter follows:
--------------------------8<----------------------------
v6:
- use READ_ONCE to ensure that compiler doesn't optimize away local var
The only difference from v5 is the change to use READ_ONCE to fetch the
bd_super pointer, to ensure that the compiler doesn't refetch it
afterward. Many thanks to Jan K. for the explanation!
Jeff Layton (2):
vfs: track per-sb writeback errors and report them to syncfs
buffer: record blockdev write errors in super_block that it backs
drivers/dax/device.c | 1 +
fs/buffer.c | 7 +++++++
fs/file_table.c | 1 +
fs/open.c | 3 +--
fs/sync.c | 6 ++++--
include/linux/fs.h | 16 ++++++++++++++++
include/linux/pagemap.h | 5 ++++-
7 files changed, 34 insertions(+), 5 deletions(-)
--
2.26.1
next reply other threads:[~2020-04-28 13:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-28 13:51 Jeff Layton [this message]
2020-04-28 13:51 ` [PATCH v6 RESEND 1/2] vfs: track per-sb writeback errors and report them to syncfs Jeff Layton
2020-04-28 13:51 ` [PATCH v6 RESEND 2/2] buffer: record blockdev write errors in super_block that it backs Jeff Layton
2020-04-28 23:48 ` [PATCH v6 RESEND 0/2] vfs: have syncfs() return error when there are writeback errors Andrew Morton
2020-04-29 12:23 ` Jeff Layton
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=20200428135155.19223-1-jlayton@kernel.org \
--to=jlayton@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=andres@anarazel.de \
--cc=david@fromorbit.com \
--cc=dhowells@redhat.com \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=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).