From: syzbot <syzbot+04ae2c9e709a347f1a81@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, dmantipov@yandex.ru, jack@suse.com,
jlbec@evilplan.org, joseph.qi@linux.alibaba.com,
kartikey406@gmail.com, linux-ext4@vger.kernel.org,
linux-kernel@vger.kernel.org, mark@fasheh.com,
ocfs2-devel@lists.linux.dev, syzkaller-bugs@googlegroups.com,
tytso@mit.edu
Subject: Re: [syzbot] [ocfs2?] [ext4?] WARNING in __jbd2_log_wait_for_space
Date: Tue, 23 Dec 2025 16:32:01 -0800 [thread overview]
Message-ID: <694b3481.050a0220.35954c.0009.GAE@google.com> (raw)
In-Reply-To: <67775d94.050a0220.178762.003a.GAE@google.com>
syzbot suspects this issue was fixed by commit:
commit 93ce0ff117b0c468961d7c296a03ad57e1e8da9f
Author: Deepanshu Kartikey <kartikey406@gmail.com>
Date: Thu Oct 30 15:30:03 2025 +0000
ocfs2: validate cl_bpc in allocator inodes to prevent divide-by-zero
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=11b4ef1a580000
start commit: 63676eefb7a0 Merge tag 'sched_ext-for-6.13-rc5-fixes' of g..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=ba7cde9482d6bb6
dashboard link: https://syzkaller.appspot.com/bug?extid=04ae2c9e709a347f1a81
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15c678b0580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=112bcedf980000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: ocfs2: validate cl_bpc in allocator inodes to prevent divide-by-zero
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2025-12-24 0:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-03 3:46 [syzbot] [ext4?] [ocfs2?] WARNING in __jbd2_log_wait_for_space syzbot
2025-12-24 0:32 ` syzbot [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=694b3481.050a0220.35954c.0009.GAE@google.com \
--to=syzbot+04ae2c9e709a347f1a81@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=dmantipov@yandex.ru \
--cc=jack@suse.com \
--cc=jlbec@evilplan.org \
--cc=joseph.qi@linux.alibaba.com \
--cc=kartikey406@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@fasheh.com \
--cc=ocfs2-devel@lists.linux.dev \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tytso@mit.edu \
/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;
as well as URLs for NNTP newsgroup(s).