From: syzbot <syzbot+3030e17bd57a73d39bd7@syzkaller.appspotmail.com>
To: clm@fb.com, dsterba@suse.com, josef@toxicpanda.com,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
lizhi.xu@windriver.com, quwenruo.btrfs@gmx.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [btrfs?] general protection fault in btrfs_search_slot
Date: Thu, 24 Oct 2024 21:59:03 -0700 [thread overview]
Message-ID: <671b2597.050a0220.381c35.000b.GAE@google.com> (raw)
In-Reply-To: <20241025043848.1981317-1-lizhi.xu@windriver.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+3030e17bd57a73d39bd7@syzkaller.appspotmail.com
Tested-by: syzbot+3030e17bd57a73d39bd7@syzkaller.appspotmail.com
Tested on:
commit: ae90f6a6 Merge tag 'bpf-fixes' of git://git.kernel.org..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=129e3287980000
kernel config: https://syzkaller.appspot.com/x/.config?x=fc6f8ce8c5369043
dashboard link: https://syzkaller.appspot.com/bug?extid=3030e17bd57a73d39bd7
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=17ca0230580000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2024-10-25 4:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-24 3:50 [syzbot] [btrfs?] general protection fault in btrfs_search_slot syzbot
2024-10-25 2:23 ` Lizhi Xu
2024-10-25 2:44 ` syzbot
2024-10-25 4:19 ` Qu Wenruo
2024-10-25 4:38 ` [syzbot] [bcachefs?] KASAN: slab-use-after-free Read in bch2_reconstruct_alloc Lizhi Xu
2024-10-25 4:44 ` Qu Wenruo
2024-10-25 4:59 ` syzbot [this message]
2024-10-25 4:55 ` [PATCH] btrfs: add a sanity check for btrfs root Lizhi Xu
2024-10-25 9:53 ` Qu Wenruo
2024-10-25 18:03 ` David Sterba
2024-10-25 21:03 ` Qu Wenruo
2024-10-25 22:22 ` David Sterba
2024-11-03 21:44 ` [syzbot] [btrfs?] general protection fault in btrfs_search_slot 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=671b2597.050a0220.381c35.000b.GAE@google.com \
--to=syzbot+3030e17bd57a73d39bd7@syzkaller.appspotmail.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizhi.xu@windriver.com \
--cc=quwenruo.btrfs@gmx.com \
--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