From: keith.busch@intel.com (Keith Busch)
Subject: [RFD] passthrough ioctl interface considered harmful?
Date: Wed, 24 Jan 2018 08:59:35 -0700 [thread overview]
Message-ID: <20180124155935.GD14790@localhost.localdomain> (raw)
In-Reply-To: <20180124150101.rxalj4x44bmwtaba@linux-x5ow.site>
On Wed, Jan 24, 2018@04:01:01PM +0100, Johannes Thumshirn wrote:
> Inspired by the discussion at [1] I've distilled a small test-case [1] which
> deletes QID 1 submission and completions queues. When running this while I/O
> is in-flight we obviously get timeouts and thus force controller resets.
>
> For some commands commands (nvme_admin_format_nvm, nvme_admin_sanitize_nvm) we
> do already check whether it is a good idea or not and at least warn the user
> about the possible side effects.
>
> Question here is, should we extend the list and/or block specific commands (at
> least while I/O is running)?
I like to think if you misuse the interface, you get to keep both
pieces. With great power comes great responsibility.
prev parent reply other threads:[~2018-01-24 15:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-24 15:01 [RFD] passthrough ioctl interface considered harmful? Johannes Thumshirn
2018-01-24 15:59 ` Keith Busch [this message]
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=20180124155935.GD14790@localhost.localdomain \
--to=keith.busch@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).