From: syzbot <syzbot+f51a2a34984e4d8888fd@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
zlatistiv@gmail.com
Subject: Re: [syzbot] [bfs?] general protection fault in bfs_get_block (3)
Date: Wed, 19 Nov 2025 11:14:02 -0800 [thread overview]
Message-ID: <691e16fa.a70a0220.d98e3.001a.GAE@google.com> (raw)
In-Reply-To: <CAHjv_atfaaAbS_-KWuqV3j4_x1E45BS9oPzM26GeTPvQbzHyvQ@mail.gmail.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+f51a2a34984e4d8888fd@syzkaller.appspotmail.com
Tested-by: syzbot+f51a2a34984e4d8888fd@syzkaller.appspotmail.com
Tested on:
commit: 0135f5af Merge remote-tracking branch 'will/for-next/p..
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci
console output: https://syzkaller.appspot.com/x/log.txt?x=14161b32580000
kernel config: https://syzkaller.appspot.com/x/.config?x=4bac9a44ad9d067c
dashboard link: https://syzkaller.appspot.com/bug?extid=f51a2a34984e4d8888fd
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=172ace0a580000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2025-11-19 19:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHjv_atfaaAbS_-KWuqV3j4_x1E45BS9oPzM26GeTPvQbzHyvQ@mail.gmail.com>
2025-11-19 19:14 ` syzbot [this message]
2024-10-30 0:43 [syzbot] [bfs?] general protection fault in bfs_get_block (3) syzbot
2024-11-03 1:37 ` Edward Adam Davis
2024-11-03 1:57 ` syzbot
2024-11-03 4:37 ` Edward Adam Davis
2024-11-03 4:53 ` syzbot
2024-11-03 6:08 ` Edward Adam Davis
2024-11-03 6:28 ` syzbot
2024-11-03 14:08 ` Edward Adam Davis
2024-11-03 14:33 ` syzbot
2024-11-15 17:58 ` 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=691e16fa.a70a0220.d98e3.001a.GAE@google.com \
--to=syzbot+f51a2a34984e4d8888fd@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=zlatistiv@gmail.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.