linux-kernel - Re: [RFC PATCH] nvme: add NO APST quirk for Kioxia device

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]

Date:   Wed, 10 Nov 2021 12:23:52 -0300
From:   Enzo Matsumiya <ematsumiya@...e.de>
To:     Chaitanya Kulkarni <chaitanyak@...dia.com>
Cc:     "linux-nvme@...ts.infradead.org" <linux-nvme@...ts.infradead.org>,
        Keith Busch <kbusch@...nel.org>, Jens Axboe <axboe@...com>,
        Sagi Grimberg <sagi@...mberg.me>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Christoph Hellwig <hch@....de>
Subject: Re: [RFC PATCH] nvme: add NO APST quirk for Kioxia device

Hi Chaitanya,

On 11/10, Chaitanya Kulkarni wrote:
>Enzo,
>
>> I didn't, had to google. I see it listed on Kioxia's website as
>> CD6-V Series (6.4T model), but since customer was running on an
>> DL380 Gen10, I suspect it could also be HPE PE8030 (PN P19837-B21).
>>
>
>You can get more information about this controller using nvme-cli
>id-ctrl command.

I'm aware.

I don't have access to the system, but id-ctrl output was shared with
us.

AFAICS these are the only identifying fields, which all indicate to be
Kioxia's:

NVME Identify Controller:
vid       : 0x1e0f
ssvid     : 0x1e0f
sn        : [redacted]
mn        : KCD6XVUL6T40
fr        : GPK1
rab       : 2
ieee      : 8ce38e
...

Now something that I'm not aware. Would these change even if another
brand was using this Kioxia's chipset?

Is it crucial to have the product information (vs only chipset information)
for quirks? I'm already querying the customer for this anyway.


Cheers,

Enzo