Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: kbusch@kernel.org (Keith Busch)
Subject: [PATCHv3 2/2] nvme: validate cntlid during controller initialisation
Date: Fri, 3 May 2019 10:16:38 -0600	[thread overview]
Message-ID: <20190503161637.GB30291@localhost.localdomain> (raw)
In-Reply-To: <20190503133736.111201-3-hare@suse.de>

On Fri, May 03, 2019@03:37:36PM +0200, Hannes Reinecke wrote:
> The CNTLID value is required to be unique, and we do rely on this
> for correct operation. So reject any controller for which a non-unique
> CNTLID has been detected.

Looks good. 

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

  reply	other threads:[~2019-05-03 16:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-03 13:37 [PATCHv3 0/2] nvme: validate CNTLID Hannes Reinecke
2019-05-03 13:37 ` [PATCHv3 1/2] nvme-multipath: avoid crash on invalid subsystem cntlid enumeration Hannes Reinecke
2019-05-03 16:01   ` Keith Busch
2019-05-08  7:54   ` Christoph Hellwig
2019-05-03 13:37 ` [PATCHv3 2/2] nvme: validate cntlid during controller initialisation Hannes Reinecke
2019-05-03 16:16   ` Keith Busch [this message]
2019-05-03 19:12   ` Max Gurtovoy
2019-05-04 14:20   ` Minwoo Im
2019-05-08  7:54   ` Christoph Hellwig
2019-05-10 14:51   ` John Donnelly
2019-05-10 18:12     ` Chaitanya Kulkarni

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=20190503161637.GB30291@localhost.localdomain \
    --to=kbusch@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox