From: Jeff Layton <firstname.lastname@example.org> To: viro@ZenIV.linux.org.uk, email@example.com Cc: firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org Subject: [PATCH 0/5] vfs: track per-sb writeback errors and report them via fsinfo() Date: Mon, 4 Jun 2018 14:02:59 -0400 [thread overview] Message-ID: <email@example.com> (raw) From: Jeff Layton <firstname.lastname@example.org> 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
next reply other threads:[~2018-06-04 18:03 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-06-04 18:02 Jeff Layton [this message] 2018-06-04 18:03 ` [PATCH 1/5] vfs: track per-sb writeback errors Jeff Layton 2018-06-04 18:03 ` [PATCH 2/5] buffer: record blockdev write errors in super_block that backs them Jeff Layton 2018-06-06 15:56 ` Jeff Layton 2018-06-19 10:40 ` Jeff Layton 2018-06-19 13:03 ` Jeff Layton 2018-06-04 18:03 ` [PATCH 3/5] errseq: add a new errseq_scrape function Jeff Layton 2018-06-04 18:03 ` [PATCH 4/5] vfs: allow fsinfo to fetch the current state of s_wb_err Jeff Layton 2018-06-04 18:03 ` [PATCH 5/5] samples: extend test-fsinfo to access error_state 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 \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --cc=viro@ZenIV.linux.org.uk \ --firstname.lastname@example.org \ --subject='Re: [PATCH 0/5] vfs: track per-sb writeback errors and report them via fsinfo()' \ /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
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).