[PATCH] nvme: fix command limits status code

Christoph Hellwig hch at lst.de
Tue May 20 23:14:00 PDT 2025


On Tue, May 20, 2025 at 01:20:37PM -0700, Keith Busch wrote:
> From: Keith Busch <kbusch at kernel.org>
> 
> The command specific status code, 0x183, was introduced in nvme 2.0
> specification defined to "Command Size Limits Exceeded" and only ever
> applied to DSM and Copy commands.

Yeah, that's weird.  Chaitanya, did you implement this off an early
draft?

> Fix the name and remove the incorrect
> special handling for it.

Where the incorrect handling is the mappings in nvme_error_status
and nvme_status_to_pr_err?  Yes, limit exceed should not be a not
supported, so this looks fine.  But it would be good to actually
spell that out in the commit message.  I'll fix it up if you don't
object.




More information about the Linux-nvme mailing list