From: syzbot <syzbot+a96175a4ea467a49c546@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] kernel panic: bch_dev->ref underflow, last put: bch2_get_next_dev
Date: Thu, 22 Aug 2024 10:34:29 -0700 [thread overview]
Message-ID: <00000000000029482306204912bc@google.com> (raw)
In-Reply-To: <000000000000d38be106186a5e45@google.com>
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.
***
Subject: kernel panic: bch_dev->ref underflow, last put: bch2_get_next_dev
Author: kent.overstreet@linux.dev
#syz fix bcachefs: Fix ref in trans_mark_dev_sbs() error path
prev parent reply other threads:[~2024-08-22 17:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-14 13:56 [syzbot] [bcachefs?] kernel panic: bch_dev->ref underflow, last put: bch2_get_next_dev syzbot
2024-08-22 17:34 ` 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=00000000000029482306204912bc@google.com \
--to=syzbot+a96175a4ea467a49c546@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.