From: Christoph Hellwig <hch@infradead.org>
To: Gilles Buloz <Gilles.Buloz@kontron.com>
Cc: Christoph Hellwig <hch@infradead.org>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Subject: Re: NVMe write protection support
Date: Sat, 6 Aug 2022 01:35:03 -0700 [thread overview]
Message-ID: <Yu4nt1bzSynhmeUF@infradead.org> (raw)
In-Reply-To: <DU0PR10MB62528A77489B4ADE66503166809D9@DU0PR10MB6252.EURPRD10.PROD.OUTLOOK.COM>
On Tue, Aug 02, 2022 at 09:20:02AM +0000, Gilles Buloz wrote:
> Sorry Christoph, I'm completely newbie in NVMe and don't know what "Namespace Write Protection Config" means.
Take a look at
https://nvmexpress.org/wp-content/uploads/NVM-Express-Base-Specification-2.0b-2021.12.18-Ratified.pdf
and search for this term.
> What I mean is that all the NVMe content seen by the user is write protected.
And that is what this feature is abut.
> Our NVMe manufacturer partner has dedicated a pin of the module for global write protection.
There is no concept of a 'module' in NVMe.
> But if we enable this protection and attempt a write (we should not), we get a "critical medium error" which seems a bit brutal for a disk that is still valid but just write protected. So I would like to make sure the NVMe manufacturer has used the right method/status to report this write protection, and if possible get a less fatal error feedback.
It seems like your manufacturer needs to read the NVMe spec and
implement the correct features.
next prev parent reply other threads:[~2022-08-06 8:35 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 [this message]
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
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=Yu4nt1bzSynhmeUF@infradead.org \
--to=hch@infradead.org \
--cc=Gilles.Buloz@kontron.com \
--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