[PATCH 0/2] nvme: handle partially unique NID value

[Javier Gonzalez]

On 05.05.2025 09:49, Laurence Oberman wrote:
>On Mon, 2025-05-05 at 15:08 +0200, Javier Gonzalez wrote:
>> On 05.05.2025 13:11, Christoph Hellwig wrote:
>> > On Mon, May 05, 2025 at 11:51:39AM +0200, Javier Gonzalez wrote:
>> > > I think we should let HPE distros carry this quirk for drives
>> > > where they
>> > > would not want to roll a FW update.
>> >
>> > Or just goddamn people to upgrade the broken firmware.  Without it
>> > their data is at risk, so they'd better do it.
>> >
>> > Also maybe this is a lesson to SSDs vendors (and I really mean all
>> > of
>> > them) that if they can't push back ob broken "features" due to
>> > market
>> > dynamics they should at least OEM brand the devices in the identify
>> > data so that the blame gets deflected to the right party.
>>
>> Agree. The dynamics of how OEMs want to apply FW updates is up to
>> them,
>> but there is no doubt this has been a mess. Hope we have learned a
>> lesson...
>>
>
>Seems what I sent last week is the same issue.
>For now we will fix this in a RHEL only kernel until the vendor gets
>F/W fixes out.

This is great. Thanks for the support Laurence!

Curtis,

With SUSE and RedHat picking this quirk, is it enough on your end?