public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Ming Lei <ming.lei@redhat.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	Venkat Rao Bagalkote <venkat88@linux.ibm.com>,
	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: Thu, 8 Jan 2026 23:21:53 -0800	[thread overview]
Message-ID: <aWCskbTyA18x-JyT@infradead.org> (raw)
In-Reply-To: <aWClEA6KuLP6E1cP@fedora>

On Fri, Jan 09, 2026 at 02:49:52PM +0800, Ming Lei wrote:
> Unfortunately I can't duplicate the issue in my environment, can you test
> the following patch?

This fixes xfs/049 for me, which was by bisection test.  I'll kick off
a full xfstests run once VM capacity becomes available later today.


  reply	other threads:[~2026-01-09  7:22 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 [this message]
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
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=aWCskbTyA18x-JyT@infradead.org \
    --to=hch@infradead.org \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=axboe@kernel.dk \
    --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