From: syzbot <syzbot+353de08f32ce69361b89@syzkaller.appspotmail.com>
To: agruenba@redhat.com, gfs2@lists.linux.dev,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [gfs2?] kernel BUG in do_xmote
Date: Tue, 21 Oct 2025 19:11:02 -0700 [thread overview]
Message-ID: <68f83d36.a00a0220.9662e.0000.GAE@google.com> (raw)
In-Reply-To: <68ef003e.050a0220.91a22.0229.GAE@google.com>
syzbot has bisected this issue to:
commit 669d4eb0b91817f2451a0210c79ef4c21af66f49
Author: Andreas Gruenbacher <agruenba@redhat.com>
Date: Mon Aug 4 22:07:02 2025 +0000
gfs2: Clean up properly during a withdraw
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=15f57c58580000
start commit: 52ba76324a9d Add linux-next specific files for 20251013
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=17f57c58580000
console output: https://syzkaller.appspot.com/x/log.txt?x=13f57c58580000
kernel config: https://syzkaller.appspot.com/x/.config?x=99cb6b007a8889ef
dashboard link: https://syzkaller.appspot.com/bug?extid=353de08f32ce69361b89
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1589f304580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1492bb34580000
Reported-by: syzbot+353de08f32ce69361b89@syzkaller.appspotmail.com
Fixes: 669d4eb0b918 ("gfs2: Clean up properly during a withdraw")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2025-10-22 2:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-15 2:00 [syzbot] [gfs2?] kernel BUG in do_xmote syzbot
2025-10-22 2:11 ` syzbot [this message]
2025-10-22 22:32 ` Forwarded: " syzbot
[not found] <CAHc6FU7GK25PT5qCZV6iX_HYoJ+gtA9sejPB5Oz51Ji8Wj5CQw@mail.gmail.com>
2025-10-22 23:06 ` syzbot
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=68f83d36.a00a0220.9662e.0000.GAE@google.com \
--to=syzbot+353de08f32ce69361b89@syzkaller.appspotmail.com \
--cc=agruenba@redhat.com \
--cc=gfs2@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.