From: Christoph Hellwig <hch@infradead.org>
To: Aleksandr Nogikh <nogikh@google.com>
Cc: Christoph Hellwig <hch@infradead.org>,
syzbot <syzbot+0391d34e801643e2809b@syzkaller.appspotmail.com>,
linux-kernel@vger.kernel.org, linux-xfs@vger.kernel.org,
syzkaller-bugs@googlegroups.com,
Dmitry Vyukov <dvyukov@google.com>
Subject: Re: [syzbot] [xfs?] KASAN: slab-use-after-free Read in xfs_buf_rele (4)
Date: Mon, 19 Jan 2026 01:03:20 -0800 [thread overview]
Message-ID: <aW3zWKJ4-ThpwT7Y@infradead.org> (raw)
In-Reply-To: <CANp29Y6PLo-Lr81SWp4qK9avLKpTGhXMAUDrZe3OYYgfWuaKVw@mail.gmail.com>
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@infradead.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.
next prev parent reply other threads:[~2026-01-19 9:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <aW3g7G_dWk4cbx0_@infradead.org>
2026-01-19 8:34 ` syzbot
2026-01-19 8:37 ` Christoph Hellwig
2026-01-19 8:53 ` Aleksandr Nogikh
2026-01-19 9:03 ` Christoph Hellwig [this message]
[not found] <aW5Do2YeRpq2IJZ_@infradead.org>
2026-01-19 15:17 ` syzbot
[not found] <aW3zct8OHdx5QJpG@infradead.org>
2026-01-19 9:29 ` syzbot
[not found] <aW3J5Cc3ezll_601@infradead.org>
2026-01-19 7:38 ` syzbot
[not found] <aQMbZoAAVWxxx6wc@infradead.org>
2025-10-30 8:47 ` syzbot
[not found] <aQMPqDAxyM3i3pQk@infradead.org>
2025-10-30 7:42 ` syzbot
2025-09-02 11:40 syzbot
2025-09-03 1:05 ` Dave Chinner
2025-09-03 6:08 ` Christoph Hellwig
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=aW3zWKJ4-ThpwT7Y@infradead.org \
--to=hch@infradead.org \
--cc=dvyukov@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=nogikh@google.com \
--cc=syzbot+0391d34e801643e2809b@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
/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
all inboxes | Powered by JetHome®