From: Jeff Layton <jlayton@kernel.org>
To: viro@zeniv.linux.org.uk
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, akpm@linux-foundation.org, david@fromorbit.com
Subject: [PATCH v5 0/2] vfs: have syncfs() return error when there are writeback errors
Date: Wed, 15 Apr 2020 08:12:58 -0400 [thread overview]
Message-ID: <20200415121300.228017-1-jlayton@kernel.org> (raw)
v5:
- use RCU to ensure that bd_super doesn't go away while we're using it
This is the fifth iteration of this patchset. The main difference from
v4 is that this one uses RCU to ensure validity of the bd_super pointer
when we're marking it after a buffer_head writeback error.
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.25.2
next reply other threads:[~2020-04-15 12:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-15 12:12 Jeff Layton [this message]
2020-04-15 12:12 ` [PATCH v5 1/2] vfs: track per-sb writeback errors and report them to syncfs Jeff Layton
2020-04-15 12:13 ` [PATCH v5 2/2] buffer: record blockdev write errors in super_block that it backs Jeff Layton
2020-04-15 14:06 ` Jan Kara
2020-04-15 16:22 ` Jeff Layton
2020-04-16 9:35 ` Jan Kara
2020-04-16 11:31 ` 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=20200415121300.228017-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).