linux-kernel - Re: [PATCH 08/10] spi: espi_amd: Add support for IO/MMIO configuration

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: <836f2d63-7b9a-4fef-ba52-3d481ea91077@amd.com>
Date: Wed, 26 Mar 2025 15:42:06 +0530
From: "Rangoju, Raju" <raju.rangoju@....com>
To: Mark Brown <broonie@...nel.org>
Cc: linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org,
 krishnamoorthi.m@....com, akshata.mukundshetty@....com
Subject: Re: [PATCH 08/10] spi: espi_amd: Add support for IO/MMIO
 configuration



On 3/17/2025 7:40 PM, Mark Brown wrote:
> On Fri, Mar 14, 2025 at 12:04:38AM +0530, Raju Rangoju wrote:
> 
>> Add support to configure the eSPI slave0 IO/MMIO address before
>> initiating the peripheral channel IO/MMIO read and write operations.
>> This patch introduces new IOCTLs to enable, disable and read IO/MMIO
>> configurations.
> 
> This absolutely does not seem like something that should be exposed to
> userspace, if there is some reason for this to be runtime configured it
> needs to be clearly explained.

Hi Mark,

Thanks for reviewing this. In subsequent series we are planning to drop 
the IOCTLS that are exposed to userspace