linux-kernel - Re: [RFC PATCH] nvmem: core: add sysfs cell write support

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: <CZ9TU33SEHWS.1HK9XLFPKBROY@walle.cc>
Date: Tue, 20 Feb 2024 11:16:40 +0100
From: "Michael Walle" <michael@...le.cc>
To: "Marco Felsch" <m.felsch@...gutronix.de>, "Miquel Raynal"
 <miquel.raynal@...tlin.com>
Cc: <srinivas.kandagatla@...aro.org>, <gregkh@...uxfoundation.org>,
 <rafal@...ecki.pl>, <linux-kernel@...r.kernel.org>, <kernel@...gutronix.de>
Subject: Re: [RFC PATCH] nvmem: core: add sysfs cell write support

On Tue Feb 20, 2024 at 10:50 AM CET, Marco Felsch wrote:
> > Read-copy-update would probably work but would as well be very
> > sub-optimal. I guess we could live with it, but as for now there has
> > not been any real request for it, I'd also advise to keep this feature
> > out of the mtd world in general.
>
> SPI-NORs are very typical for storing production-data as well but as I
> said this is another story. I'm fine with limiting it to EEPROMs since
> this is my use-case :)

Right, that is just what we are doing on our boards. But we do that
in one go in our production environment, like just writing to the
mtd partition or the OTP region. The nvmem cells are then just for
connecting the devices to this information (like the nvmem-cells
property of an ethernet device).

Also usually, there is more to it, like removing write protection of
said flash (sometimes in a proprietary way).

-michael

Download attachment "signature.asc" of type "application/pgp-signature" (253 bytes)