All of lore.kernel.org
 help / color / mirror / Atom feed
From: keith.busch@linux.intel.com (Keith Busch)
Subject: [PATCH] nvme: don't rely on the changed namespace list log
Date: Mon, 11 Jun 2018 10:00:02 -0600	[thread overview]
Message-ID: <20180611160002.GA791@localhost.localdomain> (raw)
In-Reply-To: <20180611143009.GA14441@lst.de>

Thanks, this looks fine. The main thing I want to prevent is reading from
a namespace with the wrong block size, which may corrupt memory. I don't
think it's possible to fix every scenario, but this patch at least narrows
it down even if the scenario this is guarding against is pretty unlikely.

Reviewed-by: Keith Busch <keith.busch at linux.intel.com>

      reply	other threads:[~2018-06-11 16:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-06 12:37 [PATCH] nvme: don't rely on the changed namespace list log Christoph Hellwig
2018-06-11 14:30 ` Christoph Hellwig
2018-06-11 16:00   ` 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=20180611160002.GA791@localhost.localdomain \
    --to=keith.busch@linux.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 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.