From: syzbot <syzbot+005ef9aa519f30d97657@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, pz010001011111@proton.me,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bcachefs?] general protection fault in btree_node_iter_and_journal_peek
Date: Tue, 22 Oct 2024 15:09:02 -0700 [thread overview]
Message-ID: <6718227e.050a0220.10f4f4.017e.GAE@google.com> (raw)
In-Reply-To: <c8IH934n7hOP4OxexVl1FkZewtnxm09Kgns9QF-3xW_f7GUGVd4D7_wOn8UfrXCO5gWdnY1OZcvJKd_Wmty8-9u-nnEq0ZCiKCx122GozyI=@proton.me>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+005ef9aa519f30d97657@syzkaller.appspotmail.com
Tested-by: syzbot+005ef9aa519f30d97657@syzkaller.appspotmail.com
Tested on:
commit: c2ee9f59 KVM: selftests: Fix build on on non-x86 archi..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=11ab8287980000
kernel config: https://syzkaller.appspot.com/x/.config?x=fc6f8ce8c5369043
dashboard link: https://syzkaller.appspot.com/bug?extid=005ef9aa519f30d97657
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=1448ca5f980000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2024-10-22 22:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <c8IH934n7hOP4OxexVl1FkZewtnxm09Kgns9QF-3xW_f7GUGVd4D7_wOn8UfrXCO5gWdnY1OZcvJKd_Wmty8-9u-nnEq0ZCiKCx122GozyI=@proton.me>
2024-10-22 22:09 ` syzbot [this message]
[not found] <Cxjx92g-RDXPwPhRPOczrlF7XC9EQd2TNFcHJN2cZryuWJnFbMnXlmaB5oZYD3Fm5ZLsvazKTGebBdxdOWGztBE91Nz67neXQ91bd-Ro-1A=@proton.me>
2024-10-22 21:41 ` [syzbot] [bcachefs?] general protection fault in btree_node_iter_and_journal_peek syzbot
2024-09-30 6:01 syzbot
2024-10-22 7:35 ` 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=6718227e.050a0220.10f4f4.017e.GAE@google.com \
--to=syzbot+005ef9aa519f30d97657@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pz010001011111@proton.me \
--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