From: Christoph Hellwig <hch@infradead.org>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: Eryu Guan <eguan@redhat.com>, fstests <fstests@vger.kernel.org>,
Christoph Hellwig <hch@infradead.org>
Subject: Re: [PATCH] xfs/348: update error message when transmogrifying symlink into directory
Date: Thu, 13 Apr 2017 11:17:29 -0700 [thread overview]
Message-ID: <20170413181729.GA6909@infradead.org> (raw)
In-Reply-To: <20170413153942.GA5083@birch.djwong.org>
On Thu, Apr 13, 2017 at 08:39:43AM -0700, Darrick J. Wong wrote:
> We introduced the inline directory verifier in 4.11 to prevent the
> system from trying to use corrupt inline directories. This has the
> effect of changing the error message in one step of the i_mode fuzz
> tester, so update the test accordingly.
>
> Note that prior to the existence of the verifier, this test would
> occasionally result in memory corruption that did not become evident
> until later.
>
> Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
Looks good,
Reviewed-by: Christoph Hellwig <hch@lst.de>
prev parent reply other threads:[~2017-04-13 18:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-13 15:39 [PATCH] xfs/348: update error message when transmogrifying symlink into directory Darrick J. Wong
2017-04-13 18:17 ` Christoph Hellwig [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=20170413181729.GA6909@infradead.org \
--to=hch@infradead.org \
--cc=darrick.wong@oracle.com \
--cc=eguan@redhat.com \
--cc=fstests@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