From: syzbot <syzbot+7960178e777909060224@syzkaller.appspotmail.com>
To: kartikey406@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ocfs2?] kernel BUG in ocfs2_move_extents
Date: Wed, 31 Dec 2025 02:25:03 -0800 [thread overview]
Message-ID: <6954f9ff.050a0220.a1b6.0317.GAE@google.com> (raw)
In-Reply-To: <20251231075100.287822-1-kartikey406@gmail.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+7960178e777909060224@syzkaller.appspotmail.com
Tested-by: syzbot+7960178e777909060224@syzkaller.appspotmail.com
Tested on:
commit: cc3aa43b Add linux-next specific files for 20251219
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=14725792580000
kernel config: https://syzkaller.appspot.com/x/.config?x=3da5346c9fca3188
dashboard link: https://syzkaller.appspot.com/bug?extid=7960178e777909060224
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
userspace arch: arm64
patch: https://syzkaller.appspot.com/x/patch.diff?x=121407da580000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2025-12-31 10:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251231075100.287822-1-kartikey406@gmail.com>
2025-12-31 10:25 ` syzbot [this message]
[not found] <20260104122615.13802-1-kartikey406@gmail.com>
2026-01-04 12:50 ` [syzbot] [ocfs2?] kernel BUG in ocfs2_move_extents syzbot
[not found] <20260104114905.12172-1-kartikey406@gmail.com>
2026-01-04 12:13 ` syzbot
[not found] <20251231075206.287881-1-kartikey406@gmail.com>
2025-12-31 11:25 ` syzbot
[not found] <20251231050537.50481-1-kartikey406@gmail.com>
2025-12-31 5:35 ` syzbot
2025-12-18 15:15 syzbot
2025-12-23 20:31 ` 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=6954f9ff.050a0220.a1b6.0317.GAE@google.com \
--to=syzbot+7960178e777909060224@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