All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@kernel.org>
To: dhowells@redhat.com
Cc: linux-fsdevel@vger.kernel.org, andres@anarazel.de
Subject: [fsinfo PATCH v2 0/3] fsinfo: add error state information to fsinfo
Date: Fri, 26 Jun 2020 11:04:57 -0400	[thread overview]
Message-ID: <20200626150500.565417-1-jlayton@kernel.org> (raw)

Hi David,

I sent a draft version of these patches back in 2018. The per-sb
errseq_t tracking was just merged for v5.8, so most of the underlying
infrastructure is now in place. Wiring up the reporting of that to
fsinfo() is fairly trivial.

Can you toss these onto your fsinfo pile? If that goes in at some point
in the future, it'd be nice to have this infolevel available on day 1.
This is based on your current fsinfo-core branch. The patches are also
available here if you want to cherry-pick them instead:

    https://git.kernel.org/pub/scm/linux/kernel/git/jlayton/linux.git/log/?h=fsinfo-wberr


Thanks!

Jeff Layton (3):
  errseq: add a new errseq_scrape function
  vfs: allow fsinfo to fetch the current state of s_wb_err
  samples: add error state information to test-fsinfo.c

 fs/fsinfo.c                 | 11 +++++++++++
 include/linux/errseq.h      |  1 +
 include/uapi/linux/fsinfo.h | 13 +++++++++++++
 lib/errseq.c                | 33 +++++++++++++++++++++++++++++++--
 samples/vfs/test-fsinfo.c   | 10 ++++++++++
 5 files changed, 66 insertions(+), 2 deletions(-)

-- 
2.26.2


             reply	other threads:[~2020-06-26 15:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-26 15:04 Jeff Layton [this message]
2020-06-26 15:04 ` [fsinfo PATCH v2 1/3] errseq: add a new errseq_scrape function Jeff Layton
2020-06-26 15:04 ` [fsinfo PATCH v2 2/3] vfs: allow fsinfo to fetch the current state of s_wb_err Jeff Layton
2020-06-26 15:05 ` [fsinfo PATCH v2 3/3] samples: add error state information to test-fsinfo.c 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=20200626150500.565417-1-jlayton@kernel.org \
    --to=jlayton@kernel.org \
    --cc=andres@anarazel.de \
    --cc=dhowells@redhat.com \
    --cc=linux-fsdevel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.