From: syzbot <syzbot+725322cc4ff5c53abfac@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] Re: [syzbot] [bcachefs?] possible deadlock in get_partial_node (2)
Date: Tue, 15 Apr 2025 05:31:15 -0700 [thread overview]
Message-ID: <67fe5193.050a0220.186b78.0001.GAE@google.com> (raw)
In-Reply-To: <67b1f949.050a0220.173698.000c.GAE@google.com>
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.
***
Subject: Re: [syzbot] [bcachefs?] possible deadlock in get_partial_node (2)
Author: kent.overstreet@linux.dev
On Mon, Apr 14, 2025 at 12:22:01PM -0700, syzbot wrote:
> 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=17e4ea3f980000
> start commit: b7c90e3e717a Merge tag 'x86-urgent-2025-03-08' of git://gi..
> git tree: upstream
> kernel config: https://syzkaller.appspot.com/x/.config?x=523d3ff8e053340a
> dashboard link: https://syzkaller.appspot.com/bug?extid=725322cc4ff5c53abfac
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=137c1fa0580000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12e0fa54580000
>
> If the result looks correct, please mark the issue as fixed by replying with:
>
#syz fix: bcachefs: Fix b->written overflow
prev parent reply other threads:[~2025-04-15 12:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-16 14:42 [syzbot] [kernel?] possible deadlock in get_partial_node (2) syzbot
2025-03-09 10:40 ` [syzbot] [bcachefs?] " syzbot
2025-03-10 8:16 ` syzbot
2025-04-14 19:22 ` syzbot
2025-04-15 12:31 ` 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=67fe5193.050a0220.186b78.0001.GAE@google.com \
--to=syzbot+725322cc4ff5c53abfac@syzkaller.appspotmail.com \
--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