From: hch@infradead.org (Christoph Hellwig)
Subject: [PATCH] nvme: freeze IO accesses around format
Date: Fri, 27 Oct 2017 23:45:08 -0700 [thread overview]
Message-ID: <20171028064508.GA20977@infradead.org> (raw)
In-Reply-To: <6951d74c-e765-1b5d-6e39-d88d261bf9b9@kernel.dk>
And what about sanitize? I guess instead of looking at opcodes directly
we'd better look at the indications in the Commands Supported and Effects
log. That's what the Windows driver does, btw.
next prev parent reply other threads:[~2017-10-28 6:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-27 16:35 [PATCH] nvme: freeze IO accesses around format Jens Axboe
2017-10-27 16:44 ` Keith Busch
2017-10-27 23:07 ` Keith Busch
2017-10-30 14:29 ` Jens Axboe
2017-11-01 15:56 ` Christoph Hellwig
2017-11-01 16:21 ` Keith Busch
2017-11-01 16:21 ` Christoph Hellwig
2017-10-28 6:45 ` Christoph Hellwig [this message]
2017-10-30 14:30 ` Jens Axboe
2017-11-01 15:42 ` Christoph Hellwig
2017-11-01 15:49 ` Keith Busch
2017-11-01 15:43 ` Christoph Hellwig
2017-11-01 15:45 ` Jens Axboe
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=20171028064508.GA20977@infradead.org \
--to=hch@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 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.