linux-kernel - Re: [PATCH] nvme-pci: add quirk for Wodposit WPBSNM8-256GTP to disable secondary temp thresholds

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: <84cb474d-c41e-40dd-9a75-704b9ebaaf45@aosc.io>
Date: Tue, 16 Dec 2025 21:47:48 +0800
From: Ilikara Zheng <ilikara@...c.io>
To: Keith Busch <kbusch@...nel.org>
Cc: linux-kernel@...r.kernel.org, Wu Haotian <rigoligo03@...il.com>,
 Mingcong Bai <jeffbai@...c.io>, Kexy Biscuit <kexybiscuit@...c.io>,
 stable@...r.kernel.org, Jens Axboe <axboe@...nel.dk>,
 Christoph Hellwig <hch@....de>, Sagi Grimberg <sagi@...mberg.me>,
 "open list:NVM EXPRESS DRIVER" <linux-nvme@...ts.infradead.org>
Subject: Re: [PATCH] nvme-pci: add quirk for Wodposit WPBSNM8-256GTP to
 disable secondary temp thresholds

Hi Keith,

On 12/15/2025 11:32 PM, Keith Busch wrote:
> I'm not finding vendor 1FA0 registered on the public pci-ids, nor in the
> pcisig.com members list.

When I run command lspci -vvnnk, I got outputs below:

     01:00.0 Non-Volatile memory controller [0108]: Device [1fa0:2283] 
(prog-if 02 [NVM Express])
             Subsystem: Device [1fa0:2283]
             Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- 
ParErr- Stepping- SERR- FastB2B- DisINTx+
             Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast 
 >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
             Latency: 0
             Interrupt: pin A routed to IRQ 37
             NUMA node: 0
             Region 0: Memory at 40110000 (64-bit, non-prefetchable) 
[size=16K]
             Expansion ROM at 40000000 [disabled] [size=64K]
             Capabilities: <access denied>
             Kernel driver in use: nvme

 > I just want to make sure the identifier is officially registered.

I have no idea why they didn't use their PCI Vendor ID, see 
https://pcisig.com/membership/member-companies where they used a 
different Vendor ID (0x2094).