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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20170706232253.GA11119@lst.de>
Date:   Fri, 7 Jul 2017 01:22:53 +0200
From:   Christoph Hellwig <hch@....de>
To:     Keith Busch <keith.busch@...el.com>
Cc:     Christoph Hellwig <hch@....de>,
        David Wayne Fugate <david.fugate@...el.com>,
        Jens Axboe <axboe@...com>, Sagi Grimberg <sagi@...mberg.me>,
        linux-nvme@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] NVMe: Added another device ID with stripe quirk

On Thu, Jul 06, 2017 at 06:39:56PM -0400, Keith Busch wrote:
> 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>