From: Keith Busch <kbusch@kernel.org>
To: Venkat Rao Bagalkote <venkat88@linux.ibm.com>
Cc: Ming Lei <ming.lei@redhat.com>,
Christoph Hellwig <hch@infradead.org>,
linux-block@vger.kernel.org, linux-scsi@vger.kernel.org,
Jens Axboe <axboe@kernel.dk>,
James.Bottomley@hansenpartnership.com, leonro@nvidia.com,
kch@nvidia.com, LKML <linux-kernel@vger.kernel.org>,
Madhavan Srinivasan <maddy@linux.ibm.com>,
riteshh@linux.ibm.com, ojaswin@linux.ibm.com
Subject: Re: [next-20260108]kernel BUG at drivers/scsi/scsi_lib.c:1173!
Date: Fri, 9 Jan 2026 07:38:37 -0700 [thread overview]
Message-ID: <aWES7e7iB9DoZSg7@kbusch-mbp> (raw)
In-Reply-To: <4c85df85-58f7-4e44-8201-2f0562f93439@linux.ibm.com>
On Fri, Jan 09, 2026 at 07:53:00PM +0530, Venkat Rao Bagalkote wrote:
> On 09/01/26 7:35 pm, Ming Lei wrote:
>
> Apologies for back and forth. But I did apply the whole patch. Below is the
> git diff from my machine. Let me know, if I am missing anything.
Are you saying that this bug is preventing you from even compiling the
requested kernel patches? If so, you need to revert to a kernel that was
successful, then recompile and install the new kernel with Ming's
suggestions.
next prev parent reply other threads:[~2026-01-09 14:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-09 4:58 [next-20260108]kernel BUG at drivers/scsi/scsi_lib.c:1173! Venkat Rao Bagalkote
2026-01-09 5:56 ` Christoph Hellwig
2026-01-09 6:49 ` Ming Lei
2026-01-09 7:21 ` Christoph Hellwig
2026-01-09 15:08 ` Christoph Hellwig
2026-01-09 11:44 ` Venkat Rao Bagalkote
2026-01-09 11:55 ` Ming Lei
2026-01-09 12:21 ` Venkat Rao Bagalkote
2026-01-09 12:58 ` Ming Lei
2026-01-09 13:56 ` Venkat Rao Bagalkote
2026-01-09 14:05 ` Ming Lei
2026-01-09 14:23 ` Venkat Rao Bagalkote
2026-01-09 14:38 ` Keith Busch [this message]
2026-01-09 14:40 ` Ming Lei
2026-01-09 16:33 ` Venkat Rao Bagalkote
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=aWES7e7iB9DoZSg7@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=axboe@kernel.dk \
--cc=hch@infradead.org \
--cc=kch@nvidia.com \
--cc=leonro@nvidia.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=maddy@linux.ibm.com \
--cc=ming.lei@redhat.com \
--cc=ojaswin@linux.ibm.com \
--cc=riteshh@linux.ibm.com \
--cc=venkat88@linux.ibm.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