From: Eryu Guan <eguan@redhat.com>
To: Brian Foster <bfoster@redhat.com>
Cc: fstests@vger.kernel.org, linux-xfs@vger.kernel.org
Subject: Re: [PATCH] tests/xfs: test for NULL xattr buffer problem during unlink
Date: Fri, 13 Oct 2017 13:46:05 +0800 [thread overview]
Message-ID: <20171013054605.GN10593@eguan.usersys.redhat.com> (raw)
In-Reply-To: <20171012113627.39452-1-bfoster@redhat.com>
On Thu, Oct 12, 2017 at 07:36:27AM -0400, Brian Foster wrote:
> XFS had a bug that resulted in an unexpected NULL buffer during
> unlink of an inode with a multi-level attr fork tree. This occurred
> due to a stale reference to content in a released/reclaimed buffer.
>
> Use the XFS buffer LRU reference count error injection tag to
> recreate the conditions for the bug. Create a file with a
> multi-level attr fork tree and then unlink it with buffer caching
> disabled.
>
> Signed-off-by: Brian Foster <bfoster@redhat.com>
> ---
>
> Note that this test depends on a pending[1] XFS error injection tag.
>
> Brian
>
> [1] https://marc.info/?l=linux-xfs&m=150765408521029&w=2
I ran this test with above patch applied (v4.14-rc4 based), and kernel
crashed as expected. Then cherry-pick commit f35c5e10c6ed ("xfs: reinit
btree pointer on attr tree inactivation walk") and test passed. So test
looks good to me, just that I added 'dangerous' group and referenced the
fix in commit log and test description.
Thanks for the test!
Eryu
next prev parent reply other threads:[~2017-10-13 5:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-12 11:36 [PATCH] tests/xfs: test for NULL xattr buffer problem during unlink Brian Foster
2017-10-12 19:57 ` Darrick J. Wong
2017-10-13 5:46 ` Eryu Guan [this message]
2017-10-13 10:08 ` Brian Foster
2017-10-13 17:01 ` Darrick J. Wong
2017-10-15 7:16 ` Eryu Guan
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=20171013054605.GN10593@eguan.usersys.redhat.com \
--to=eguan@redhat.com \
--cc=bfoster@redhat.com \
--cc=fstests@vger.kernel.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).