From: syzbot <syzbot+f2107d999290b8166267@syzkaller.appspotmail.com>
To: dmantipov@yandex.ru, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ocfs2?] kernel BUG in __ocfs2_move_extents_range
Date: Wed, 22 Oct 2025 07:49:02 -0700 [thread overview]
Message-ID: <68f8eede.050a0220.346f24.0054.GAE@google.com> (raw)
In-Reply-To: <20251022140056.5Yda7%dmantipov@yandex.ru>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+f2107d999290b8166267@syzkaller.appspotmail.com
Tested-by: syzbot+f2107d999290b8166267@syzkaller.appspotmail.com
Tested on:
commit: 552c5071 Merge tag 'vfio-v6.18-rc3' of https://github...
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=13c6ce7c580000
kernel config: https://syzkaller.appspot.com/x/.config?x=f9a2ca2a8964bd4a
dashboard link: https://syzkaller.appspot.com/bug?extid=f2107d999290b8166267
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=11ac4614580000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2025-10-22 14:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251022140056.5Yda7%dmantipov@yandex.ru>
2025-10-22 14:49 ` syzbot [this message]
[not found] <20251024071534.2MOzq%dmantipov@yandex.ru>
2025-10-24 11:07 ` [syzbot] [ocfs2?] kernel BUG in __ocfs2_move_extents_range syzbot
[not found] <20251024071522.EtAA6%dmantipov@yandex.ru>
2025-10-24 10:22 ` syzbot
[not found] <20251024071155.pT8us%dmantipov@yandex.ru>
2025-10-24 9:17 ` syzbot
2025-04-16 2:09 syzbot
2025-08-17 8:12 ` 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=68f8eede.050a0220.346f24.0054.GAE@google.com \
--to=syzbot+f2107d999290b8166267@syzkaller.appspotmail.com \
--cc=dmantipov@yandex.ru \
--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