From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH rfc 1/2] nvme: support smart read-only critical warning event
Date: Mon, 4 Dec 2017 21:07:21 +0100 [thread overview]
Message-ID: <20171204200721.GB17023@lst.de> (raw)
In-Reply-To: <20171204092435.20000-2-sagi@grimberg.me>
On Mon, Dec 04, 2017@11:24:34AM +0200, Sagi Grimberg wrote:
> In case a controller sent us a critical warning AER,
> we should query the smart information and in case the
> media was placed in read only mode, we need to set
> all the controller namespaces (and the namespaces heads)
> in read-only (or set to rw in case its not set).
>
> Given that in fabrics we may also connect to a read-only
> subsystem, we add the disk as read-only to start with.
> Once the subsystem will be in rw mode, we restore
> the disk rw permissions.
We are sending the smart log notification on to userspace, so with this
we now have two parties that are trying to clear the log page..
next prev parent reply other threads:[~2017-12-04 20:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-04 9:24 [PATCH rfc 0/2] Support read-only subsystem critical warning Sagi Grimberg
2017-12-04 9:24 ` [PATCH rfc 1/2] nvme: support smart read-only critical warning event Sagi Grimberg
2017-12-04 20:07 ` Christoph Hellwig [this message]
2017-12-05 7:28 ` Sagi Grimberg
2017-12-05 7:57 ` Johannes Thumshirn
2017-12-06 22:47 ` Christoph Hellwig
2017-12-07 6:45 ` Sagi Grimberg
2017-12-04 9:24 ` [PATCH rfc 2/2] nvmet: expose option to emulate a nvm subsystem in read-only mode Sagi Grimberg
2017-12-04 16:19 ` Christoph Hellwig
2017-12-04 18:11 ` Sagi Grimberg
2017-12-04 20:06 ` Christoph Hellwig
2017-12-05 7:22 ` Sagi Grimberg
2017-12-06 22:46 ` Christoph Hellwig
2017-12-07 6:41 ` Sagi Grimberg
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=20171204200721.GB17023@lst.de \
--to=hch@lst.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.