From: Eryu Guan <guaneryu@gmail.com>
To: Jeff Mahoney <jeffm@suse.com>
Cc: "Darrick J. Wong" <darrick.wong@oracle.com>,
linux-xfs@vger.kernel.org, fstests@vger.kernel.org
Subject: Re: [PATCH 2/2] t_attr_corruption: fix this yet again
Date: Sat, 2 Mar 2019 17:32:48 +0800 [thread overview]
Message-ID: <20190302093248.GC2824@desktop> (raw)
In-Reply-To: <ed56f33a-5fff-1200-7353-ba411c863baa@suse.com>
On Thu, Feb 28, 2019 at 03:56:40PM -0500, Jeff Mahoney wrote:
> On 2/25/19 9:35 PM, Darrick J. Wong wrote:
> > From: Darrick J. Wong <darrick.wong@oracle.com>
> >
> > Jeff Moyer pointed out that 'security.evm' actually has an expected
>
> Mahoney :)
Fixed on commit :)
>
> > value format, which breaks the test if EVM is enabled. It turns out
> > that the 'security.evm' setxattr call in the original syzkaller report
> > was a total red herring, as this bug can be reproduced without it.
> >
> > Fix the test case to do the minimum amount of work needed to reproduce
> > the corruption.
> >
> > Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
>
> Otherwise, works for me in the case that failed for me previously.
Thanks for the fix and test!
Eryu
next prev parent reply other threads:[~2019-03-02 9:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-26 2:35 [PATCH 1/2] misc: don't oom the box opening tmpfiles Darrick J. Wong
2019-02-26 2:35 ` [PATCH 2/2] t_attr_corruption: fix this yet again Darrick J. Wong
2019-02-26 20:03 ` Allison Henderson
2019-02-28 20:56 ` Jeff Mahoney
2019-03-02 9:32 ` Eryu Guan [this message]
2019-02-26 3:46 ` [PATCH 3/2] xfs/010: use correct type for finobt corrupting Darrick J. Wong
2019-02-26 20:17 ` Allison Henderson
2019-02-26 19:08 ` [PATCH 1/2] misc: don't oom the box opening tmpfiles Allison Henderson
2019-02-26 21:05 ` Darrick J. Wong
2019-02-26 22:24 ` Allison Henderson
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=20190302093248.GC2824@desktop \
--to=guaneryu@gmail.com \
--cc=darrick.wong@oracle.com \
--cc=fstests@vger.kernel.org \
--cc=jeffm@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox