All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+80e5d6f453f14a53383a@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, ayaanmirza.788@gmail.com,
	 ayaanmirzabaig85@gmail.com, josh@joshtriplett.org,
	kent.overstreet@linux.dev,  linux-bcachefs@vger.kernel.org,
	linux-kernel@vger.kernel.org,  linux-mm@kvack.org,
	luto@kernel.org, paulmck@kernel.org, peterz@infradead.org,
	 rcu@vger.kernel.org, syzkaller-bugs@googlegroups.com,
	tglx@linutronix.de
Subject: Re: [syzbot] [bcachefs?] [rcu?] BUG: unable to handle kernel NULL pointer dereference in rcu_core (3)
Date: Sat, 07 Jun 2025 23:58:03 -0700	[thread overview]
Message-ID: <6845347b.050a0220.d8705.000c.GAE@google.com> (raw)
In-Reply-To: <67a2b20a.050a0220.50516.0003.GAE@google.com>

syzbot has bisected this issue to:

commit 14152654805256d760315ec24e414363bfa19a06
Author: Kent Overstreet <kent.overstreet@linux.dev>
Date:   Mon Nov 25 05:21:27 2024 +0000

    bcachefs: Bad btree roots are now autofix

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=12fa0a82580000
start commit:   99fa936e8e4f Merge tag 'affs-6.14-rc5-tag' of git://git.ke..
git tree:       upstream
final oops:     https://syzkaller.appspot.com/x/report.txt?x=11fa0a82580000
console output: https://syzkaller.appspot.com/x/log.txt?x=16fa0a82580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=523d3ff8e053340a
dashboard link: https://syzkaller.appspot.com/bug?extid=80e5d6f453f14a53383a
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=119d35a8580000

Reported-by: syzbot+80e5d6f453f14a53383a@syzkaller.appspotmail.com
Fixes: 141526548052 ("bcachefs: Bad btree roots are now autofix")

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

  parent reply	other threads:[~2025-06-08  6:58 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-05  0:34 [syzbot] [rcu?] [bcachefs?] BUG: unable to handle kernel NULL pointer dereference in rcu_core (3) syzbot
2025-02-05 14:56 ` Paul E. McKenney
2025-06-08 15:26   ` Kent Overstreet
2025-06-08 18:23     ` Uladzislau Rezki
2025-06-09  0:25       ` Paul E. McKenney
2025-06-09  8:35         ` Uladzislau Rezki
2025-06-09  9:47           ` Paul E. McKenney
2025-06-09 14:20             ` Joel Fernandes
2025-06-10 12:19               ` Uladzislau Rezki
2025-06-09 18:28       ` Vlastimil Babka
2025-06-10 12:33         ` Uladzislau Rezki
2025-06-08  6:58 ` syzbot [this message]
2025-06-11 15:58 ` Uladzislau Rezki
2025-06-11 18:02   ` [syzbot] [bcachefs?] [rcu?] " syzbot
2025-06-11 19:15     ` Uladzislau Rezki
2025-06-11 19:57       ` syzbot
2025-06-11 20:58         ` Boqun Feng
2025-06-12  7:42           ` Aleksandr Nogikh
2025-06-12  9:37             ` Uladzislau Rezki
2025-06-12 17:20               ` Boqun Feng
     [not found] <20250609052925.971-1-hdanton@sina.com>
2025-06-09  6:01 ` syzbot

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=6845347b.050a0220.d8705.000c.GAE@google.com \
    --to=syzbot+80e5d6f453f14a53383a@syzkaller.appspotmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=ayaanmirza.788@gmail.com \
    --cc=ayaanmirzabaig85@gmail.com \
    --cc=josh@joshtriplett.org \
    --cc=kent.overstreet@linux.dev \
    --cc=linux-bcachefs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=luto@kernel.org \
    --cc=paulmck@kernel.org \
    --cc=peterz@infradead.org \
    --cc=rcu@vger.kernel.org \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tglx@linutronix.de \
    /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.