From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH 0/3] xfs: tidy up corruption reporting
Date: Mon, 4 Nov 2019 08:34:23 -0800 [thread overview]
Message-ID: <20191104163423.GA4153244@magnolia> (raw)
In-Reply-To: <20191104152222.GC10485@infradead.org>
On Mon, Nov 04, 2019 at 07:22:22AM -0800, Christoph Hellwig wrote:
> On Sun, Nov 03, 2019 at 02:23:43PM -0800, Darrick J. Wong wrote:
> > 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.
>
> Do you have a reference to that discussion?
https://lore.kernel.org/linux-xfs/CAHk-=wiHuHLK49LKQhtERXaq0OYUnug4DJZFLPq9RHEG2Cm+bQ@mail.gmail.com/
--D
prev parent reply other threads:[~2019-11-04 16:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-03 22:23 [PATCH 0/3] xfs: tidy up corruption reporting Darrick J. Wong
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 [this message]
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=20191104163423.GA4153244@magnolia \
--to=darrick.wong@oracle.com \
--cc=hch@infradead.org \
--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 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).