From: Keith Busch <kbusch@kernel.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: Avinash M N <Avinash.M.N@sandisk.com>,
Jeffrey Lien <Jeff.Lien@sandisk.com>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
Rahul Jain <Rahul.Jain@sandisk.com>
Subject: Re: NVMe CLI Invalid PRP Entry Status Failures
Date: Tue, 27 May 2025 09:44:09 -0600 [thread overview]
Message-ID: <aDXdyXtp5D6PpV-F@kbusch-mbp> (raw)
In-Reply-To: <aDQToX9eVtNF39G6@infradead.org>
On Mon, May 26, 2025 at 12:09:21AM -0700, Christoph Hellwig wrote:
> On Sat, May 24, 2025 at 08:26:17AM -0600, Keith Busch wrote:
>
> bio_split_rw_at doesn't look at max_sectors unless that is passed
> in as the argument.
Oh right, this passthrough path uses the max_hw_sectors limit instead.
> It would be good to just throw in debug printks to see which splitting
> decision in bio_split_rw_at triggers, including checking the exact
> condition in bvec_split_segs.
FWIW, I can't reproduce the issue on 6.10.
prev parent reply other threads:[~2025-05-27 15:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <MW3PR16MB3897F0E659B34877C4D5197CF391A@MW3PR16MB3897.namprd16.prod.outlook.com>
2025-05-15 14:01 ` NVMe CLI Invalid PRP Entry Status Failures Jeffrey Lien
2025-05-15 14:18 ` Keith Busch
[not found] ` <LV3PR16MB606775F391112B2DADF64463B590A@LV3PR16MB6067.namprd16.prod.outlook.com>
2025-05-16 12:33 ` Keith Busch
[not found] ` <LV3PR16MB6067E928D739DCB65F31FE46B593A@LV3PR16MB6067.namprd16.prod.outlook.com>
2025-05-16 14:41 ` Keith Busch
2025-05-24 4:22 ` Avinash M N
2025-05-24 14:26 ` Keith Busch
2025-05-26 7:09 ` Christoph Hellwig
2025-05-27 15:44 ` Keith Busch [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=aDXdyXtp5D6PpV-F@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=Avinash.M.N@sandisk.com \
--cc=Jeff.Lien@sandisk.com \
--cc=Rahul.Jain@sandisk.com \
--cc=hch@infradead.org \
--cc=linux-nvme@lists.infradead.org \
/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