From: "Darrick J. Wong" <djwong@kernel.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-block <linux-block@vger.kernel.org>,
linux-scsi@vger.kernel.org,
"Martin K. Petersen" <martin.petersen@oracle.com>,
fstests <fstests@vger.kernel.org>,
xfs <linux-xfs@vger.kernel.org>
Subject: Re: regression on generic/351 in 6.11-rc5?
Date: Tue, 27 Aug 2024 10:51:24 -0700 [thread overview]
Message-ID: <20240827175124.GA1977952@frogsfrogsfrogs> (raw)
In-Reply-To: <Zs1bL4H1dR_HVPmT@infradead.org>
On Mon, Aug 26, 2024 at 09:50:55PM -0700, Christoph Hellwig wrote:
> On Mon, Aug 26, 2024 at 07:07:14PM -0700, Darrick J. Wong wrote:
> > Has anyone else noticed the following regression in generic/351 between
> > 6.11-rc4 and -rc5?
>
> Yes, I'm seeing this with a fresh -rc5 build.
Aha, it wasn't the scsi lbpme patch like I thought; it was a different
patch in the block layer that got overly aggressive about not querying
write same queue limits. Patch incoming.
--D
next prev parent reply other threads:[~2024-08-27 17:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-27 2:07 regression on generic/351 in 6.11-rc5? Darrick J. Wong
2024-08-27 4:50 ` Christoph Hellwig
2024-08-27 17:51 ` Darrick J. Wong [this message]
2024-08-28 5:05 ` Zorro Lang
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=20240827175124.GA1977952@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=hch@infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=martin.petersen@oracle.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