[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20180604180304.9662-1-jlayton@kernel.org>
Date: Mon, 4 Jun 2018 14:02:59 -0400
From: Jeff Layton <jlayton@...nel.org>
To: viro@...IV.linux.org.uk, dhowells@...hat.com
Cc: willy@...radead.org, andres@...razel.de, cmaiolino@...hat.com,
linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org
Subject: [PATCH 0/5] vfs: track per-sb writeback errors and report them via fsinfo()
From: Jeff Layton <jlayton@...hat.com>
This is a reworked (and more modest) version of the syncfs rework that I
posted recently. Given that we have a new fsinfo syscall being
introduced, we may as well use it to report writeback errors on a per
superblock basis. This allows us to provide the info that the PostgreSQL
developers wanted, without needing to change an existing interface.
We may still want to change syncfs to report writeback errors at some
point, but for now, I think this is a safer path to presenting this
info.
This seems to do the right thing when tested by hand, but I don't yet
have an xfstest for it, since the syscall is still quite new. Once that
goes in and we get fsinfo support in xfs_io, it should be rather
trivial to modify the test I wrote for the syncfs rework.
Jeff Layton (5):
vfs: track per-sb writeback errors
buffer: record blockdev write errors in super_block that backs them
errseq: add a new errseq_scrape function
vfs: allow fsinfo to fetch the current state of s_wb_err
samples: extend test-fsinfo to access error_state
fs/buffer.c | 2 ++
fs/statfs.c | 9 +++++++++
include/linux/errseq.h | 1 +
include/linux/fs.h | 3 +++
include/linux/pagemap.h | 5 ++++-
include/uapi/linux/fsinfo.h | 11 +++++++++++
lib/errseq.c | 33 +++++++++++++++++++++++++++++++--
samples/statx/test-fsinfo.c | 13 +++++++++++++
8 files changed, 74 insertions(+), 3 deletions(-)
--
2.17.0
Powered by blists - more mailing lists