linux-kernel - Re: [PATCH 1/2] ABI: sysfs-nvmem-cells: Expose cells through sysfs

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: <2023052303-bless-elevation-6905@gregkh>
Date:   Tue, 23 May 2023 17:59:40 +0100
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Miquel Raynal <miquel.raynal@...tlin.com>
Cc:     Srinivas Kandagatla <srinivas.kandagatla@...aro.org>,
        Luka Perkov <luka.perkov@...tura.hr>,
        Robert Marko <robert.marko@...tura.hr>,
        Thomas Petazzoni <thomas.petazzoni@...tlin.com>,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] ABI: sysfs-nvmem-cells: Expose cells through sysfs

On Tue, May 23, 2023 at 12:02:38PM +0200, Miquel Raynal wrote:
> +		The cells/ folder contains one file per cell exposed by
> +		the nvmem device. The name of the file is the cell name.
> +		The length of the file is the size of the cell (when
> +		known). The content of the file is the binary content of
> +		the cell (may sometimes be ASCII, likely without
> +		trailing character).
> +		There is currently no write permission but this could
> +		evolve in the future if the need arises.

No need to have these 2 lines, you don't know what will happen in the
future, don't tease people :)

thanks,

greg k-h