[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aW3zWKJ4-ThpwT7Y@infradead.org>
Date: Mon, 19 Jan 2026 01:03:20 -0800
From: Christoph Hellwig <hch@...radead.org>
To: Aleksandr Nogikh <nogikh@...gle.com>
Cc: Christoph Hellwig <hch@...radead.org>,
syzbot <syzbot+0391d34e801643e2809b@...kaller.appspotmail.com>,
linux-kernel@...r.kernel.org, linux-xfs@...r.kernel.org,
syzkaller-bugs@...glegroups.com, Dmitry Vyukov <dvyukov@...gle.com>
Subject: Re: [syzbot] [xfs?] KASAN: slab-use-after-free Read in xfs_buf_rele
(4)
On Mon, Jan 19, 2026 at 09:53:18AM +0100, Aleksandr Nogikh wrote:
> On Mon, Jan 19, 2026 at 9:37 AM Christoph Hellwig <hch@...radead.org> wrote:
> >
> > So I'm not sure what this test does that it always triggers the lockdep
> > keys, but that makes it impossible to validate the original xfs report.
> >
> > Is there a way to force running syzbot reproducers without lockdep?
>
> Not directly, but you could explicitly modify lockdep's Kconfig in
> your test patch to disable lockdep entirely.
Already, I'll give it a try.
Powered by blists - more mailing lists