From: keith.busch@intel.com (Keith Busch)
Subject: [PATCH] nvme: freeze IO accesses around format
Date: Wed, 1 Nov 2017 09:49:51 -0600 [thread overview]
Message-ID: <20171101154951.GK17245@localhost.localdomain> (raw)
In-Reply-To: <20171101154232.GA25317@infradead.org>
On Wed, Nov 01, 2017@08:42:32AM -0700, Christoph Hellwig wrote:
> On Mon, Oct 30, 2017@08:30:04AM -0600, Jens Axboe wrote:
> > On 10/28/2017 12:45 AM, Christoph Hellwig wrote:
> > > 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.
> >
> > Isn't that exactly what Keith's patch did?
>
> Ooops I had missed his patch was a completely different approach.
I'll send it out in a new thread. I have fix the command effects log
page memory leak, anyway.
next prev parent reply other threads:[~2017-11-01 15:49 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
2017-10-30 14:30 ` Jens Axboe
2017-11-01 15:42 ` Christoph Hellwig
2017-11-01 15:49 ` Keith Busch [this message]
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=20171101154951.GK17245@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