From: syzbot <syzbot+fd8af97c7227fe605d95@syzkaller.appspotmail.com>
To: kartikey406@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ocfs2?] divide error in ocfs2_block_group_fill (3)
Date: Sun, 26 Oct 2025 06:13:02 -0700 [thread overview]
Message-ID: <68fe1e5e.050a0220.32483.000c.GAE@google.com> (raw)
In-Reply-To: <20251026125108.11538-1-kartikey406@gmail.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+fd8af97c7227fe605d95@syzkaller.appspotmail.com
Tested-by: syzbot+fd8af97c7227fe605d95@syzkaller.appspotmail.com
Tested on:
commit: 72761a7e Merge tag 'driver-core-6.18-rc3' of git://git..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=13fa5614580000
kernel config: https://syzkaller.appspot.com/x/.config?x=25811b07889c90db
dashboard link: https://syzkaller.appspot.com/bug?extid=fd8af97c7227fe605d95
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
patch: https://syzkaller.appspot.com/x/patch.diff?x=17d82c92580000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2025-10-26 13:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251026125108.11538-1-kartikey406@gmail.com>
2025-10-26 13:13 ` syzbot [this message]
[not found] <20251029062745.ABm5W%dmantipov@yandex.ru>
2025-10-29 10:18 ` [syzbot] [ocfs2?] divide error in ocfs2_block_group_fill (3) syzbot
[not found] <20251029062551.GvRBN%dmantipov@yandex.ru>
2025-10-29 8:40 ` syzbot
[not found] <20251029062156.pGggr%dmantipov@yandex.ru>
2025-10-29 7:08 ` syzbot
[not found] <20251027121326.8868-1-kartikey406@gmail.com>
2025-10-27 12:34 ` syzbot
2025-10-19 9:13 syzbot
2025-10-25 21:54 ` 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=68fe1e5e.050a0220.32483.000c.GAE@google.com \
--to=syzbot+fd8af97c7227fe605d95@syzkaller.appspotmail.com \
--cc=kartikey406@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox