linux-kernel - Re: [PATCH v3 2/2] nvme: prevent admin controller from smart log fetch (LID 2)

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 for Android: free password hash cracker in your pocket

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

Message-ID: <f80ffee3-60aa-46d6-bd1c-7240ad171ee4@kernel.org>
Date: Fri, 18 Jul 2025 13:17:44 +0900
From: Damien Le Moal <dlemoal@...nel.org>
To: Kamaljit Singh <kamaljit.singh1@....com>, kbusch@...nel.org,
 axboe@...nel.dk, hch@....de, sagi@...mberg.me,
 linux-nvme@...ts.infradead.org, linux-kernel@...r.kernel.org
Cc: cassel@...nel.org
Subject: Re: [PATCH v3 2/2] nvme: prevent admin controller from smart log
 fetch (LID 2)

On 2025/07/18 9:14, Kamaljit Singh wrote:
> Similar to a discovery ctrl, prevent an admin-ctrl from getting a smart
> log. LID 2 is optional for admin controllers to support.
> 
> In the future when support for LID=0 (supported log pages) is added,
> GLP accesses can be made smarter by basing such calls on response
> from LID=0 reads.
> 
> Reference: NVMe Base rev 2.2, sec 3.1.3.5, fig 31.
> Signed-off-by: Kamaljit Singh <kamaljit.singh1@....com>

Reviewed-by: Damien Le Moal <dlemoal@...nel.org>


-- 
Damien Le Moal
Western Digital Research