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

[Javier Gonzalez]

On 02.05.2025 21:46, Keith Busch wrote:
>On Fri, May 02, 2025 at 11:26:47PM +0000, Judy Brock wrote:
>> For example, both companies have "admitted failure" but you haven't
>> heard it: the FW in question definitely has a defect. Neither company
>> is holding it out as compliant. Both companies have indicated going
>> forward, the defective behavior has been corrected.
>>
>> Not sure why you keep saying that neither company is willing to fix it.
>
>I'm a little confused. If the conflicting behavior has been corrected,
>why is this being discussed here? A device side fix is surely the best
>possible outcome for everyone here. Requiring a kernel upgrade to work
>around undesirable firmware behavior is a bit unpleasant for end users
>when you already have a solution that works with any nvme capable OS. ?

Agree. I think Hannes' approach to add dynamic quirks was the closest to
an upstreamable solution, as a general quick for the PM177xx is not
acceptable. But I completely understand Christoph's NAK.

I think we should let HPE distros carry this quirk for drives where they
would not want to roll a FW update.