public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+53bb24d476ef8368a7f0@syzkaller.appspotmail.com>
To: 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 __journal_res_get (2)
Date: Mon, 10 Mar 2025 07:05:07 -0700	[thread overview]
Message-ID: <67cef193.050a0220.3d01d1.0010.GAE@google.com> (raw)
In-Reply-To: <6735aa91.050a0220.2a2fcc.0062.GAE@google.com>

syzbot suspects this issue was fixed by commit:

commit fb8c835b18d48dac953a5d755a8e90b0d8fb9c29
Author: Kent Overstreet <kent.overstreet@linux.dev>
Date:   Sat Oct 12 02:50:48 2024 +0000

    bcachefs: bch2_journal_meta() takes ref on c->writes

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=1487d074580000
start commit:   bcde95ce32b6 Merge tag 'devicetree-fixes-for-6.13-1' of gi..
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=1234f097ee657d8b
dashboard link: https://syzkaller.appspot.com/bug?extid=53bb24d476ef8368a7f0
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=16ff98c4580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=11ff98c4580000

If the result looks correct, please mark the issue as fixed by replying with:

#syz fix: bcachefs: bch2_journal_meta() takes ref on c->writes

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

      parent reply	other threads:[~2025-03-10 14:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-14  7:45 [syzbot] [bcachefs?] kernel BUG in __journal_res_get (2) syzbot
2024-12-16  8:10 ` syzbot
2025-03-10 14:05 ` 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=67cef193.050a0220.3d01d1.0010.GAE@google.com \
    --to=syzbot+53bb24d476ef8368a7f0@syzkaller.appspotmail.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