public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Sagi Grimberg <sagi@grimberg.me>
Cc: "Christoph Hellwig" <hch@lst.de>,
	"Linux regressions mailing list" <regressions@lists.linux.dev>,
	"Pankaj Raghav" <p.raghav@samsung.com>,
	"Keith Busch" <kbusch@kernel.org>,
	"Bagas Sanjaya" <bagasdotme@gmail.com>,
	"Jens Axboe" <axboe@kernel.dk>,
	"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 NVMe" <linux-nvme@lists.infradead.org>,
	"Kanchan Joshi" <joshi.k@samsung.com>,
	"Javier Gonzalez" <javier.gonz@samsung.com>,
	박진환 <jh.i.park@samsung.com>,
	"Linus Torvalds" <torvalds@linux-foundation.org>
Subject: Re: Fwd: Need NVME QUIRK BOGUS for SAMSUNG MZ1WV480HCGL-000MV (Samsung SM-953 Datacenter SSD)
Date: Tue, 11 Jul 2023 16:12:06 +0200	[thread overview]
Message-ID: <2023071135-opt-choosing-51dd@gregkh> (raw)
In-Reply-To: <23017407-83eb-8fb0-5d91-2c7c4ae02544@grimberg.me>

On Tue, Jul 11, 2023 at 03:14:54PM +0300, Sagi Grimberg wrote:
> 
> > > Well, that "They keep pumping out more and more devices with the same
> > > breakage" and the "new device" comment from Pankaj below bear the
> > > question: should we stop trying to play "whack a mole" with all those
> > > quirk entries and handle devices with duplicate ids just like Windows does?
> > 
> > As far as I can tell Windows completely ignores the IDs.  Which, looking
> > back, I'd love to be able to do as well, but they are already used
> > by udev for the /dev/disk/by-id/ links.   Those are usually not used
> > on desktop systems, as they use the file system labels and UUIDs, but
> > that doesn't work for non-file system uses.
> > 
> > And all this has been working really well with the good old enterprise
> > SSDs, it's just that the cheap consumer devices keep fucking it up.
> > 
> > If we'd take it away now we'd break existing users, which puts us between
> > a rock and a hard place.
> 
> Maybe the compromise would be to add a modparam that tells the driver
> to ignore it altogether (like allow_bogus_identifiers) that would
> default to false. Then people can just workaround the problem instead
> of having the back-and-fourth with the vendor?
> 

Module parameters do not work on a per-device basis, sorry.  This isn't
the 1990's anymore, please do not attempt to add new ones :)

thanks,

greg k-h

  reply	other threads:[~2023-07-11 14:12 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-26  1:15 Fwd: Need NVME QUIRK BOGUS for SAMSUNG MZ1WV480HCGL-000MV (Samsung SM-953 Datacenter SSD) 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
     [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 [this message]
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=2023071135-opt-choosing-51dd@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=axboe@kernel.dk \
    --cc=bagasdotme@gmail.com \
    --cc=cspringsguth@gmail.com \
    --cc=hare@suse.de \
    --cc=hch@lst.de \
    --cc=javier.gonz@samsung.com \
    --cc=jh.i.park@samsung.com \
    --cc=jmeneghi@redhat.com \
    --cc=joshi.k@samsung.com \
    --cc=kbusch@kernel.org \
    --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 \
    --cc=torvalds@linux-foundation.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