All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+76f13f2acac84df26aae@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] Re: [syzbot] [bcachefs] general protection fault in bioset_exit (2)
Date: Tue, 15 Apr 2025 05:30:47 -0700	[thread overview]
Message-ID: <67fe5177.050a0220.186b78.0000.GAE@google.com> (raw)
In-Reply-To: <679fb3a5.050a0220.163cdc.0030.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] general protection fault in bioset_exit (2)
Author: kent.overstreet@linux.dev

On Tue, Apr 15, 2025 at 03:07:02AM -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=11c360cc580000
> start commit:   76544811c850 Merge tag 'drm-fixes-2025-02-28' of https://g..
> git tree:       upstream
> kernel config:  https://syzkaller.appspot.com/x/.config?x=8de9cc84d5960254
> dashboard link: https://syzkaller.appspot.com/bug?extid=76f13f2acac84df26aae
> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=159248b7980000
> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=13152a97980000
> 
> If the result looks correct, please mark the issue as fixed by replying with:
> 
#syz fix: bcachefs: Fix b->written overflow

      parent reply	other threads:[~2025-04-15 12:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-02 18:04 [syzbot] [block?] general protection fault in bioset_exit (2) syzbot
2025-02-02 20:22 ` Jens Axboe
2025-02-17  2:11 ` [syzbot] [bcachefs] " syzbot
2025-02-17  8:52 ` syzbot
2025-04-15 10:07 ` syzbot
2025-04-15 12:30 ` 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=67fe5177.050a0220.186b78.0000.GAE@google.com \
    --to=syzbot+76f13f2acac84df26aae@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.