linux-kernel - Re: [PATCH] NVMe: Added another device ID with stripe quirk

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <a01eeb47-7566-05fb-4d8b-db5ddef36b82@grimberg.me>
Date:   Mon, 10 Jul 2017 08:52:09 +0300
From:   Sagi Grimberg <sagi@...mberg.me>
To:     Christoph Hellwig <hch@....de>, Keith Busch <keith.busch@...el.com>
Cc:     David Wayne Fugate <david.fugate@...el.com>,
        Jens Axboe <axboe@...com>, linux-nvme@...ts.infradead.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] NVMe: Added another device ID with stripe quirk


>> That's true for all Intel controllers going forward, but this
>> is actually an older controller that pre-dates NOIOB. It's the exact
>> same as the 8086:0A54 model, but a particular vendor decided their
>> rebranded device needs to be made special with a different DID.
> 
> Meh..
> 
>>
>> We all agree that's a terrible way to go about this for mutliple reasons,
>> but we can't go back in time to tell the decision makers of this folly. So
>> I think we need to let this last one go through with the quirk.
>>
>> Acked-by: Keith Busch <keith.busch@...el.com>
> 
> Reluctantly-accepted-by: Christoph Hellwig <hch@....de>
> 

David, can you resend the patch? For some reason I
can't locate it in my mailbox...