public inbox for linux-nvme@lists.infradead.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Keith Busch <kbusch@kernel.org>, Sagi Grimberg <sagi@grimberg.me>
Cc: Luis Chamberlain <mcgrof@kernel.org>,
	Klaus Jensen <its@irrelevant.dk>,
	linux-nvme@lists.infradead.org
Subject: quirk broken namespace identifiers v2
Date: Wed, 13 Apr 2022 06:49:02 +0200	[thread overview]
Message-ID: <20220413044905.376785-1-hch@lst.de> (raw)

Hi all,

this series adds a quirk to ignore namespace identifiers on controllers
where they are completely broken and then quirks two controllers for it.

Changes since v1:
 - validate namespace descriptor sizes even if ignoring them
 - also handle another MAXIO controller with the same problem
 - fix up a few commit messages


             reply	other threads:[~2022-04-13  4:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-13  4:49 Christoph Hellwig [this message]
2022-04-13  4:49 ` [PATCH 1/3] nvme: add a quirk to disable namespace identifiers Christoph Hellwig
2022-04-13  4:49 ` [PATCH 2/3] nvme-pci: disable namespace identifiers for the MAXIO MAP1002/1202 Christoph Hellwig
2022-04-13  4:49 ` [PATCH 3/3] nvme-pci: disable namespace identifiers for Qemu controllers Christoph Hellwig
2022-04-13  7:34   ` Niklas Cassel
2022-04-13  8:40     ` Klaus Jensen
2022-04-13 15:34       ` Christoph Hellwig
2022-04-13 15:49         ` Klaus Jensen
2022-04-13 15:50           ` Christoph Hellwig
2022-04-13 20:08             ` Klaus Jensen
2022-04-13 20:38               ` Keith Busch
2022-04-14  4:19               ` Christoph Hellwig
2022-04-13 14:42 ` quirk broken namespace identifiers v2 Keith Busch

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=20220413044905.376785-1-hch@lst.de \
    --to=hch@lst.de \
    --cc=its@irrelevant.dk \
    --cc=kbusch@kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=mcgrof@kernel.org \
    --cc=sagi@grimberg.me \
    /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