[PATCH rfc 2/2] nvmet: expose option to emulate a nvm subsystem in read-only mode

[Sagi Grimberg]

Hey Christoph,

> I don't think that is what the SMART log is inteded for.

Can you please elaborate what you mean? are you talking about this
patch in particular (simply an emulation)? or support for this
altogether? A subsystem can, at any point, be placed in read-only mode.
In that case it needs to send SMART AER to indicate health status
change. I think that if the media has been placed in read-only mode, we
need to log it, and set all the subsystem namespaces in read-only mode.

Anything different you think we need to do here?

> Please review the write protected namespace TP in the working group instead
> and make sure it passes soon so that we can use it.

I did look at write protect, this is not the use-case here.
write-protect is a per-namespace attribute which is controlled by
the host, this addresses NVMe subsystem critical warning scenario.