mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Keith Busch <kbusch@kernel.org>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: Jens Axboe <axboe@kernel.dk>, Christoph Hellwig <hch@lst.de>,
	Sagi Grimberg <sagi@grimberg.me>,
	"Clemens S." <cspringsguth@gmail.com>,
	Martin Belanger <martin.belanger@dell.com>,
	Chaitanya Kulkarni <kch@nvidia.com>,
	John Meneghini <jmeneghi@redhat.com>,
	Hannes Reinecke <hare@suse.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Regressions <regressions@lists.linux.dev>,
	Linux NVMe <linux-nvme@lists.infradead.org>,
	Pankaj Raghav <p.raghav@samsung.com>,
	Kanchan Joshi <joshi.k@samsung.com>
Subject: Re: Fwd: Need NVME QUIRK BOGUS for SAMSUNG MZ1WV480HCGL-000MV (Samsung SM-953 Datacenter SSD)
Date: Tue, 27 Jun 2023 10:10:46 -0600	[thread overview]
Message-ID: <ZJsKBkPqoWzYyngS@kbusch-mbp.dhcp.thefacebook.com> (raw)
In-Reply-To: <d18d2a08-9d24-0209-c2cf-baf60bbf5048@gmail.com>

On Mon, Jun 26, 2023 at 08:15:49AM +0700, Bagas Sanjaya wrote:
> See Bugzilla for the full thread.
> 
> The reporter had a quirk (see above) that fixed this regression,
> nevertheless I'm adding it to regzbot to make sure it doesn't fall
> through cracks unnoticed:
> 
> #regzbot introduced: 86c2457a8e8112f https://bugzilla.kernel.org/show_bug.cgi?id=217593
> #regzbot title: NVME_QUIRK_BOGUS_NID is needed for SAMSUNG MZ1WV480HCGL-000MV

These bug reports really should go to the vendors that created the
broken device with non-unique "unique" fields. It's easy enough for me
to write the quirk patch, but it's not the ideal solution and may harm
devices/firmwares with the same VID:DID that don't have this problem.
Not being the vendor, I'm not in a postition to know that, so CC'ing
some Samsung folks.

  parent reply	other threads:[~2023-06-27 16:10 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-26  1:15 Bagas Sanjaya
     [not found] ` <8f4e6d32-55b3-9df5-de91-1afbcb30ce13@nvidia.com>
2023-06-26 18:26   ` Linux regression tracking (Thorsten Leemhuis)
2023-06-27 16:10 ` Keith Busch [this message]
     [not found]   ` <9b778d59-c8d5-b037-0eb7-34cee5f273cc@samsung.com>
2023-06-30 15:18     ` Clemens Springsguth
2023-06-30 16:21       ` Pankaj Raghav
2023-07-03 13:25         ` Clemens Springsguth
2023-07-10  8:52   ` Linux regression tracking (Thorsten Leemhuis)
2023-07-10 15:58     ` Keith Busch
     [not found]       ` <f0fdf86e-4293-8e07-835d-b5a866252068@samsung.com>
2023-07-11  9:39         ` Linux regression tracking (Thorsten Leemhuis)
2023-07-11 12:06           ` Christoph Hellwig
2023-07-11 12:14             ` Sagi Grimberg
2023-07-11 14:12               ` Greg KH
2023-07-11 14:39                 ` Sagi Grimberg
2023-07-11 15:33             ` Keith Busch
2023-07-11 16:47             ` Linus Torvalds
2023-07-11 17:21               ` Keith Busch
2023-07-11 22:07                 ` John Meneghini
2023-07-12  7:38                 ` Sagi Grimberg
2023-07-12 16:48                   ` Linus Torvalds
2023-07-12 16:45               ` Christoph Hellwig
2023-07-12 16:51                 ` Linus Torvalds
2023-07-12 16:57                   ` Christoph Hellwig
2023-07-12 17:34                     ` Linus Torvalds
2023-07-13 11:44                       ` Christoph Hellwig
2023-07-13 16:53                         ` Linus Torvalds
2023-07-16 19:19         ` August Wikerfors

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=ZJsKBkPqoWzYyngS@kbusch-mbp.dhcp.thefacebook.com \
    --to=kbusch@kernel.org \
    --cc=axboe@kernel.dk \
    --cc=bagasdotme@gmail.com \
    --cc=cspringsguth@gmail.com \
    --cc=hare@suse.de \
    --cc=hch@lst.de \
    --cc=jmeneghi@redhat.com \
    --cc=joshi.k@samsung.com \
    --cc=kch@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=martin.belanger@dell.com \
    --cc=p.raghav@samsung.com \
    --cc=regressions@lists.linux.dev \
    --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
all inboxes | Powered by JetHome®