From: Alexander Motin <mav@ixsystems.com>
To: Keith Busch <kbusch@kernel.org>, Ameer Hamza <ahamza@ixsystems.com>
Cc: linux-nvme@lists.infradead.org, axboe@kernel.dk, hch@lst.de,
sagi@grimberg.me, linux-kernel@vger.kernel.org,
edmund.nadolski@ixsystems.com
Subject: Re: [PATCH] nvme: prevent id ctrl csi for specs below 2.0
Date: Mon, 11 Sep 2023 15:29:34 -0400 [thread overview]
Message-ID: <2f1414ab-9152-17ab-d2c6-96f4f5de7d45@ixsystems.com> (raw)
In-Reply-To: <ZP9fOBSl59u8u0hq@kbusch-mbp.dhcp.thefacebook.com>
On 11.09.2023 14:40, Keith Busch wrote:
> On Mon, Sep 11, 2023 at 02:26:41AM +0500, Ameer Hamza wrote:
>> The 'id ctrl csi' command was introduced in version 2.0, as specified
>> in Section 5.17.2.6 of the NVME Base Specification 2.0. Executing this
>> command on previous NVMe versions returns an "Invalid Field" error,
>> and the error entry is saved in the log page. Although, Commit
>> c917dd96fe41 ("nvme: skip optional id ctrl csi if it failed") reduced
>> the error occurrences, but the error persisted during the initial
>> module load. This patch ensures the command isn't executed on versions
>> older than 2.0, and it also eliminates the skip implementation because
>> NVME_ID_CNS_CS_CTRL is expected to succeed with version 2.0.
>
> NVMe TP's are allowed to be implemented by versions lower than the
> release that first included it. I recall the first nvme controller I'd
> seen that implemented this identification reported itself as 1.4.
Then there must be a way to detect it. How otherwise it is not a
standard violation to send arbitrary effectively vendor-specific
commands to a drive?
--
Alexander Motin
next prev parent reply other threads:[~2023-09-11 21:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-10 21:26 Ameer Hamza
2023-09-11 18:40 ` Keith Busch
2023-09-11 19:29 ` Alexander Motin [this message]
2023-09-11 20:21 ` Keith Busch
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=2f1414ab-9152-17ab-d2c6-96f4f5de7d45@ixsystems.com \
--to=mav@ixsystems.com \
--cc=ahamza@ixsystems.com \
--cc=axboe@kernel.dk \
--cc=edmund.nadolski@ixsystems.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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
all inboxes | Powered by JetHome®