public inbox for linux-nvme@lists.infradead.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Gilles BULOZ <gilles.buloz@kontron.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	Jonathan Derrick <jonathan.derrick@linux.dev>,
	"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Subject: Re: NVMe write protection support
Date: Sun, 2 Oct 2022 23:24:49 -0700	[thread overview]
Message-ID: <YzqAMcFwXysfS0Le@infradead.org> (raw)
In-Reply-To: <9ae13173-44ec-707f-46f0-edbe3c35e0cb@kontron.com>

On Fri, Sep 30, 2022 at 07:49:38PM +0200, Gilles BULOZ wrote:
> Hi Christoph,
> Our disk manufacturer told me their NVMe does not follow NVMe specification 2.0 but 1.3.
> Is there also something in 1.3 to handle the write protection cleanly ?

NVMe 1.3 has not write protection feature.  That being NVMe is designed
so that new functionality (new TPs in NVMe terms) can be implemented by
devices that comply to older versions.  So if you just set the bit as
described earlier Linux (and other drivers that know about the feature)
will still do the right thing even if the compliance level is left as
NVM 1.3.


  reply	other threads:[~2022-10-03  6:24 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-01  8:36 NVMe write protection support Gilles Buloz
2022-08-01 10:01 ` Chao Leng
2022-08-01 12:41   ` Gilles BULOZ
2022-08-01 16:39     ` Keith Busch
2022-08-01 18:34 ` Christoph Hellwig
2022-08-02  9:20   ` Gilles Buloz
2022-08-06  8:35     ` Christoph Hellwig
2022-08-25  8:26       ` Gilles Buloz
2022-08-26 19:39         ` Jonathan Derrick
2022-08-26 19:40           ` Jonathan Derrick
2022-09-13 17:17             ` Gilles BULOZ
2022-09-19 14:59               ` Christoph Hellwig
2022-09-30 17:49                 ` Gilles BULOZ
2022-10-03  6:24                   ` Christoph Hellwig [this message]
2022-10-20 17:31                     ` Gilles BULOZ

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=YzqAMcFwXysfS0Le@infradead.org \
    --to=hch@infradead.org \
    --cc=gilles.buloz@kontron.com \
    --cc=jonathan.derrick@linux.dev \
    --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