From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: darrick.wong@oracle.com
Cc: linux-xfs@vger.kernel.org
Subject: [PATCH 0/3] xfs: tidy up corruption reporting
Date: Sun, 03 Nov 2019 14:23:43 -0800 [thread overview]
Message-ID: <157281982341.4150947.10288936972373805803.stgit@magnolia> (raw)
Hi all,
Linus requested that I audit the XFS code base to make sure that we
always log something to dmesg when returning EFSCORRUPTED or EFSBADCRC
to userspace. These patches are the results of that audit.
The first three patches start by refactoring a few helper methods so
that in the third patch we always report something to dmesg whenever we
decide to return EFSCORRUPTED.
If you're going to start using this mess, you probably ought to just
pull from my git trees, which are linked below.
This has been lightly tested with fstests. Enjoy!
Comments and questions are, as always, welcome.
--D
kernel git tree:
https://git.kernel.org/cgit/linux/kernel/git/djwong/xfs-linux.git/log/?h=report-corruption
next reply other threads:[~2019-11-03 22:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-03 22:23 Darrick J. Wong [this message]
2019-11-03 22:23 ` [PATCH 1/3] xfs: relax shortform directory size checks Darrick J. Wong
2019-11-04 15:22 ` Carlos Maiolino
2019-11-04 19:23 ` Christoph Hellwig
2019-11-03 22:23 ` [PATCH 2/3] xfs: constify the buffer pointer arguments to error functions Darrick J. Wong
2019-11-04 15:44 ` Carlos Maiolino
2019-11-04 19:25 ` Christoph Hellwig
2019-11-03 22:24 ` [PATCH 3/3] xfs: always log corruption errors Darrick J. Wong
2019-11-04 15:44 ` Carlos Maiolino
2019-11-04 19:26 ` Christoph Hellwig
2019-11-04 15:22 ` [PATCH 0/3] xfs: tidy up corruption reporting Christoph Hellwig
2019-11-04 16:34 ` Darrick J. Wong
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=157281982341.4150947.10288936972373805803.stgit@magnolia \
--to=darrick.wong@oracle.com \
--cc=linux-xfs@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.