From: syzbot <syzbot+b581c7106aa616bb522c@syzkaller.appspotmail.com>
To: davem@davemloft.net, dsahern@kernel.org, edumazet@google.com,
gregkh@linuxfoundation.org, horms@kernel.org,
kent.overstreet@linux.dev, kuba@kernel.org,
linux-bcachefs@vger.kernel.org, linux-kernel@vger.kernel.org,
mmpgouride@gmail.com, netdev@vger.kernel.org, pabeni@redhat.com,
syzkaller-bugs@googlegroups.com, tj@kernel.org
Subject: Re: [syzbot] [bcachefs?] [kernfs?] UBSAN: shift-out-of-bounds in radix_tree_delete_item
Date: Wed, 19 Mar 2025 02:40:03 -0700 [thread overview]
Message-ID: <67da90f3.050a0220.2ca2c6.0194.GAE@google.com> (raw)
In-Reply-To: <67afa09f.050a0220.21dd3.0054.GAE@google.com>
syzbot suspects this issue was fixed by commit:
commit 3a04334d6282d08fbdd6201e374db17d31927ba3
Author: Alan Huang <mmpgouride@gmail.com>
Date: Fri Mar 7 16:58:27 2025 +0000
bcachefs: Fix b->written overflow
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=176e8e98580000
start commit: 09fbf3d50205 Merge tag 'tomoyo-pr-20250211' of git://git.c..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=c516b1c112a81e77
dashboard link: https://syzkaller.appspot.com/bug?extid=b581c7106aa616bb522c
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11e449b0580000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: bcachefs: Fix b->written overflow
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2025-03-19 9:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-14 19:59 [syzbot] [kernfs?] [bcachefs?] UBSAN: shift-out-of-bounds in radix_tree_delete_item syzbot
2025-02-15 11:09 ` syzbot
2025-02-15 16:22 ` syzbot
2025-03-19 9:40 ` syzbot [this message]
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=67da90f3.050a0220.2ca2c6.0194.GAE@google.com \
--to=syzbot+b581c7106aa616bb522c@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=horms@kernel.org \
--cc=kent.overstreet@linux.dev \
--cc=kuba@kernel.org \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmpgouride@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tj@kernel.org \
/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