From: syzbot <syzbot+f51a2a34984e4d8888fd@syzkaller.appspotmail.com>
To: eadavis@qq.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bfs?] general protection fault in bfs_get_block (3)
Date: Sun, 03 Nov 2024 06:33:03 -0800 [thread overview]
Message-ID: <6727899f.050a0220.35b515.019d.GAE@google.com> (raw)
In-Reply-To: <tencent_A5864B09B4AED4AEEE8CB467D086DB52F106@qq.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: 3e5e6c99 Merge tag 'nfsd-6.12-3' of git://git.kernel.o..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=120f6b40580000
kernel config: https://syzkaller.appspot.com/x/.config?x=4aec7739e14231a7
dashboard link: https://syzkaller.appspot.com/bug?extid=f51a2a34984e4d8888fd
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=17fcb630580000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2024-11-03 14:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2024-11-03 14:36 ` [PATCH] bfs: add check for return value of sb_getblk Edward Adam Davis
2024-11-15 17:58 ` [syzbot] [bfs?] general protection fault in bfs_get_block (3) syzbot
2025-11-19 18:40 ` Forwarded: " syzbot
[not found] <CAHjv_atfaaAbS_-KWuqV3j4_x1E45BS9oPzM26GeTPvQbzHyvQ@mail.gmail.com>
2025-11-19 19:14 ` [syzbot] [bfs?] " 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=6727899f.050a0220.35b515.019d.GAE@google.com \
--to=syzbot+f51a2a34984e4d8888fd@syzkaller.appspotmail.com \
--cc=eadavis@qq.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 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.