From: Richard Weinberger <richard@nod.at>
To: Chris Packham <Chris.Packham@alliedtelesis.co.nz>
Cc: Takahiro Kuwano <Takahiro.Kuwano@infineon.com>,
Ronan Dalton <Ronan.Dalton@alliedtelesis.co.nz>,
Miquel Raynal <miquel.raynal@bootlin.com>,
pratyush <pratyush@kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Vignesh Raghavendra <vigneshr@ti.com>,
linux-mtd <linux-mtd@lists.infradead.org>,
Michael Walle <mwalle@kernel.org>,
Aryan Srivastava <Aryan.Srivastava@alliedtelesis.co.nz>
Subject: Re: [PATCH v2 1/3] Revert "mtd: spi-nor: remove Fujitsu MB85RS1MT support"
Date: Thu, 2 Jul 2026 07:39:18 +0200 (CEST) [thread overview]
Message-ID: <490633873.5619.1782970758317.JavaMail.zimbra@nod.at> (raw)
In-Reply-To: <e946b3c6-304a-4015-a144-285e7f2f4e6a@alliedtelesis.co.nz>
----- Ursprüngliche Mail -----
> Von: "Chris Packham" <Chris.Packham@alliedtelesis.co.nz>
>>> On Wed, 2026-07-01 at 09:49 +0000, Takahiro.Kuwano@infineon.com wrote:
>>>> I didn't mean any kernel features, but we can dump tmpfs contents
>>>> from/to FRAM chip (exposed as NVMEM device) by 'dd'. Doesn't it meet
>>>> your system's requirement?
>>> Do you mean something like creating a tmpfs and then say, using `tar`
>>> and copying the data to nvmem with dd and restoring this data at boot?
>> Yes, I meant something like that (sorry, my comment was still not clear).
>> Hope that's worth considering.
>
> It won't quite work. Because we have requirements involving ensuring
> when a file is erased it is gone ASAP (i.e. shred). It's all a bit of
> security theater because in reality the safest thing would be to keep
> such secrets in a TPM or protected with a key stored in a TPM.
Do you really need (POSIX) file system semantics?
You could partition the FRAM into cells and then work with them.
e.g. Just dd into it and erase it when needed...
Maybe the NVMEM cells mechanism needs some polishing but this sounds
reasonable to me.
Thanks,
//richard
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
prev parent reply other threads:[~2026-07-02 5:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-26 2:21 [PATCH v2 1/3] Revert "mtd: spi-nor: remove Fujitsu MB85RS1MT support" Ronan Dalton
2026-06-26 2:21 ` [PATCH v2 2/3] mtd: spi-nor: fujitsu: Convert to new flash_info format Ronan Dalton
2026-06-26 2:21 ` [PATCH v2 3/3] mtd: spi-nor: fujitsu: Add support for MB85RS4MTY chip Ronan Dalton
2026-07-01 8:05 ` Michael Walle
2026-07-01 23:48 ` Ronan Dalton
2026-06-30 7:47 ` [PATCH v2 1/3] Revert "mtd: spi-nor: remove Fujitsu MB85RS1MT support" Takahiro.Kuwano
2026-06-30 21:05 ` Chris Packham
2026-07-01 1:10 ` Takahiro.Kuwano
2026-07-01 2:08 ` Ronan Dalton
2026-07-01 8:12 ` Michael Walle
2026-07-01 23:42 ` Ronan Dalton
2026-07-01 9:49 ` Takahiro.Kuwano
2026-07-02 1:21 ` Ronan Dalton
2026-07-02 2:41 ` Takahiro.Kuwano
2026-07-02 3:06 ` Chris Packham
2026-07-02 5:39 ` Richard Weinberger [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=490633873.5619.1782970758317.JavaMail.zimbra@nod.at \
--to=richard@nod.at \
--cc=Aryan.Srivastava@alliedtelesis.co.nz \
--cc=Chris.Packham@alliedtelesis.co.nz \
--cc=Ronan.Dalton@alliedtelesis.co.nz \
--cc=Takahiro.Kuwano@infineon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=mwalle@kernel.org \
--cc=pratyush@kernel.org \
--cc=vigneshr@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox