From: Dave Chinner <david@fromorbit.com>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: xfs <linux-xfs@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Kent Overstreet <kent.overstreet@linux.dev>
Subject: Re: dentry UAF bugs crashing arm64 machines on 6.5/6.6?
Date: Mon, 18 Sep 2023 11:37:20 +1000 [thread overview]
Message-ID: <ZQep0OR0uMmR/wg3@dread.disaster.area> (raw)
In-Reply-To: <20230912173026.GA3389127@frogsfrogsfrogs>
On Tue, Sep 12, 2023 at 10:30:26AM -0700, Darrick J. Wong wrote:
> Hi everyone,
>
> Shortly after 6.5 was tagged, I started seeing the following stacktraces
> when running xfs through fstests on arm64. Curiously, x86_64 does not
> seem affected.
>
> At first I thought this might be caused by the bug fixes in my
> development tree, so I started bisecting them. Bisecting identified a
> particular patchset[1] that didn't seem like it was the culprit. A
> couple of days later, one of my arm64 vms with that patch reverted
> crashed in the same way. So, clearly not the culprit.
I would suggest that this is the same problem as being reported
here:
https://lore.kernel.org/linux-fsdevel/ZOWFtqA2om0w5Vmz@fedora/
due to some kind of screwup with hash_bl_lock() getting broken on
arm64 by commit 9257959a6e5b ("locking/atomic: scripts: restructure
fallback ifdeffery").
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
prev parent reply other threads:[~2023-09-18 1:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 17:30 dentry UAF bugs crashing arm64 machines on 6.5/6.6? Darrick J. Wong
2023-09-12 17:48 ` Kent Overstreet
2023-09-18 1:37 ` Dave Chinner [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=ZQep0OR0uMmR/wg3@dread.disaster.area \
--to=david@fromorbit.com \
--cc=djwong@kernel.org \
--cc=kent.overstreet@linux.dev \
--cc=linux-fsdevel@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