From: syzbot <syzbot+2b6a17991a6af64f9489@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, pz010001011111@proton.me,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bcachefs?] kernel BUG in bch2_bucket_alloc_trans (2)
Date: Sun, 20 Oct 2024 08:44:04 -0700 [thread overview]
Message-ID: <67152544.050a0220.3d9749.000b.GAE@google.com> (raw)
In-Reply-To: <rKlLbfCLe5qEsfZ4TwH_eOdju4cwug4dACGLemYC5dRwYv5U3VdjfKzPIbXADvaDMKCJ3aI4gbg4KoYzwRZOSrZkFzhE6w59CUOTakduIUo=@proton.me>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+2b6a17991a6af64f9489@syzkaller.appspotmail.com
Tested-by: syzbot+2b6a17991a6af64f9489@syzkaller.appspotmail.com
Tested on:
commit: 715ca9dd Merge tag 'io_uring-6.12-20241019' of git://g..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=15d38c87980000
kernel config: https://syzkaller.appspot.com/x/.config?x=78db40d8379956d9
dashboard link: https://syzkaller.appspot.com/bug?extid=2b6a17991a6af64f9489
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=1431a0a7980000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2024-10-20 15:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <rKlLbfCLe5qEsfZ4TwH_eOdju4cwug4dACGLemYC5dRwYv5U3VdjfKzPIbXADvaDMKCJ3aI4gbg4KoYzwRZOSrZkFzhE6w59CUOTakduIUo=@proton.me>
2024-10-20 15:44 ` syzbot [this message]
[not found] <62UDikG_A_c9--WGMXiOnVYgYo7NJo7Q3r83PJM03i01CIM9IRkHrZcG0agPWZ38lUhCqFLDToTkgxHwPrD1aKOhFvnIeJTS49ygYkRYCEE=@proton.me>
2024-10-21 8:39 ` [syzbot] [bcachefs?] kernel BUG in bch2_bucket_alloc_trans (2) syzbot
[not found] <Bx42aYpwIlfScXqal1denKS6tcNZtrc7xFTMYNGbIiw5OnuQL1UsjwMf5ZSxsmC9ech23ggVlKCNmAnCc9ewtxJ-WyJwX14aB4xx77pmAvU=@proton.me>
2024-10-20 13:18 ` syzbot
2024-10-17 5:03 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=67152544.050a0220.3d9749.000b.GAE@google.com \
--to=syzbot+2b6a17991a6af64f9489@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