From: syzbot <syzbot+843981bb836d699c07d1@syzkaller.appspotmail.com>
To: contact@arnaud-lcm.com, kent.overstreet@linux.dev,
linux-bcachefs@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bcachefs?] kernel BUG in __bch2_str_hash_check_key
Date: Mon, 28 Apr 2025 09:35:02 -0700 [thread overview]
Message-ID: <680fae36.a70a0220.23e4d2.0032.GAE@google.com> (raw)
In-Reply-To: <20250428160903.20110-1-contact@arnaud-lcm.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+843981bb836d699c07d1@syzkaller.appspotmail.com
Tested-by: syzbot+843981bb836d699c07d1@syzkaller.appspotmail.com
Tested on:
commit: b4432656 Linux 6.15-rc4
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=150dd270580000
kernel config: https://syzkaller.appspot.com/x/.config?x=a33ce5560507649
dashboard link: https://syzkaller.appspot.com/bug?extid=843981bb836d699c07d1
compiler: Debian clang version 20.1.2 (++20250402124445+58df0ef89dd6-1~exp1~20250402004600.97), Debian LLD 20.1.2
patch: https://syzkaller.appspot.com/x/patch.diff?x=11d7e368580000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2025-04-28 16:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-10 6:58 syzbot
2025-04-21 23:44 ` syzbot
2025-04-23 15:45 ` Sub volumes handling in bch2_fsck_update_backpointers Arnaud Lecomte
2025-04-23 16:47 ` Kent Overstreet
2025-04-23 17:18 ` Arnaud Lecomte
2025-04-23 17:46 ` Kent Overstreet
2025-04-23 20:24 ` Arnaud Lecomte
2025-04-24 6:27 ` [syzbot] [bcachefs?] kernel BUG in __bch2_str_hash_check_key syzbot
2025-04-28 16:09 ` syztest Arnaud Lecomte
2025-04-28 16:26 ` syztest Kent Overstreet
2025-04-28 16:35 ` syzbot [this message]
2025-07-07 20:29 ` [syzbot] [bcachefs?] kernel BUG in __bch2_str_hash_check_key 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=680fae36.a70a0220.23e4d2.0032.GAE@google.com \
--to=syzbot+843981bb836d699c07d1@syzkaller.appspotmail.com \
--cc=contact@arnaud-lcm.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--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
Powered by JetHome