All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+291aef749c5cbb9ca2fd@syzkaller.appspotmail.com>
To: bfoster@redhat.com, kent.overstreet@linux.dev,
	 linux-bcachefs@vger.kernel.org, linux-kernel@vger.kernel.org,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bcachefs?] WARNING in bch2_trans_put
Date: Sat, 21 Dec 2024 18:31:01 -0800	[thread overview]
Message-ID: <676779e5.050a0220.25abdd.0135.GAE@google.com> (raw)
In-Reply-To: <00000000000047b2a506189dfc1a@google.com>

syzbot has bisected this issue to:

commit bcf77a05fb3d6210026483703bcacb22ed961c99
Author: Kent Overstreet <kent.overstreet@linux.dev>
Date:   Fri Nov 8 05:25:18 2024 +0000

    bcachefs: Fix hidden btree errors when reading roots

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=175672df980000
start commit:   e9b8ffafd20a Merge tag 'usb-6.13-rc4' of git://git.kernel...
git tree:       upstream
final oops:     https://syzkaller.appspot.com/x/report.txt?x=14d672df980000
console output: https://syzkaller.appspot.com/x/log.txt?x=10d672df980000
kernel config:  https://syzkaller.appspot.com/x/.config?x=1234f097ee657d8b
dashboard link: https://syzkaller.appspot.com/bug?extid=291aef749c5cbb9ca2fd
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=10246f30580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=176540c4580000

Reported-by: syzbot+291aef749c5cbb9ca2fd@syzkaller.appspotmail.com
Fixes: bcf77a05fb3d ("bcachefs: Fix hidden btree errors when reading roots")

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

      parent reply	other threads:[~2024-12-22  2:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-17  3:31 [syzbot] [bcachefs?] WARNING in bch2_trans_put syzbot
2024-12-21 10:19 ` syzbot
2024-12-22  2: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=676779e5.050a0220.25abdd.0135.GAE@google.com \
    --to=syzbot+291aef749c5cbb9ca2fd@syzkaller.appspotmail.com \
    --cc=bfoster@redhat.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 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.