From: syzbot <syzbot+8882b2f5f48a7170a726@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, dmantipov@yandex.ru,
jlbec@evilplan.org, joseph.qi@linux.alibaba.com,
linux-kernel@vger.kernel.org, mark@fasheh.com,
ocfs2-devel@lists.linux.dev, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ocfs2?] kernel BUG in ocfs2_remove_extent
Date: Tue, 06 Jan 2026 21:41:04 -0800 [thread overview]
Message-ID: <695df1f0.050a0220.1c677c.0353.GAE@google.com> (raw)
In-Reply-To: <683bef14.a70a0220.1a6ae.0011.GAE@google.com>
syzbot suspects this issue was fixed by commit:
commit e1c70505ee8158c1108340d9cd67182ade93af4a
Author: Dmitry Antipov <dmantipov@yandex.ru>
Date: Thu Oct 30 15:30:02 2025 +0000
ocfs2: add extra consistency checks for chain allocator dinodes
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13776f92580000
start commit: be48bcf004f9 Merge tag 'for-6.17-rc2-tag' of git://git.ker..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=fe8fc1adb24b215
dashboard link: https://syzkaller.appspot.com/bug?extid=8882b2f5f48a7170a726
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=152226f0580000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: ocfs2: add extra consistency checks for chain allocator dinodes
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2026-01-07 5:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-01 6:11 [syzbot] [ocfs2?] kernel BUG in ocfs2_remove_extent syzbot
2025-06-20 6:10 ` syzbot
2025-08-29 1:50 ` syzbot
2025-10-22 15:04 ` Forwarded: #syz test https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 552c50713f273b494ac6c77052032a49bc9255e2 syzbot
2026-01-07 5:41 ` syzbot [this message]
[not found] <20251022150444.jHFNw%dmantipov@yandex.ru>
2025-10-22 15:21 ` [syzbot] [ocfs2?] kernel BUG in ocfs2_remove_extent 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=695df1f0.050a0220.1c677c.0353.GAE@google.com \
--to=syzbot+8882b2f5f48a7170a726@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=dmantipov@yandex.ru \
--cc=jlbec@evilplan.org \
--cc=joseph.qi@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@fasheh.com \
--cc=ocfs2-devel@lists.linux.dev \
--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.