From: Richard Weinberger <richard@nod.at>
To: Ricard Wanderlof <ricard.wanderlof@axis.com>
Cc: "Chris Packham" <Chris.Packham@alliedtelesis.co.nz>,
"Henry Shen" <Henry.Shen@alliedtelesis.co.nz>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"Bean Huo 霍斌斌 (beanhuo)" <beanhuo@micron.com>,
"Han Xu" <han.xu@nxp.com>
Subject: Re: secure file deletion/SECRM support for JFFS2 and UBIFS
Date: Thu, 28 Apr 2016 10:49:06 +0200 [thread overview]
Message-ID: <5721CE82.7010907@nod.at> (raw)
In-Reply-To: <alpine.DEB.2.02.1604281037050.31333@lnxricardw1.se.axis.com>
Am 28.04.2016 um 10:40 schrieb Ricard Wanderlof:
>
> On Thu, 28 Apr 2016, Richard Weinberger wrote:
>
>> Am 28.04.2016 um 00:35 schrieb Chris Packham:
>>>> Well, UBIFS and JFFS2 work on generic MTD, so having a special hack for NOR
>>>> is not really what we want.
>>>
>>> Agreed. I was hoping there was a similar trick for NAND which I'm less
>>> familiar with. The fallback behavior of an immediate erase is still
>>> doable but it has more corner cases that we'd need to be weary of.
>>
>> Nope, on NAND you're forced to erase.
>
> I know generally there is a recommendation not to overwrite bits already
> set to 0 with 0 for NAND, but I can't remember if that is related to the
> subsequent readability of surrounding data, or if may cause a future erase
> not to perform properly, or actually physically damages the bit cell (or
> there is some other reason).
I have been told that overwriting data on NAND can lead to physically damage,
but don't ask for a reference. ;-)
Maybe NAND fracturing folks can give more details on this topic.
Thanks,
//richard
prev parent reply other threads:[~2016-04-28 8:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-27 5:07 secure file deletion/SECRM support for JFFS2 and UBIFS Chris Packham
2016-04-27 7:05 ` Richard Weinberger
2016-04-27 7:05 ` Richard Weinberger
2016-04-27 21:49 ` Chris Packham
2016-04-27 21:55 ` Richard Weinberger
2016-04-27 22:35 ` Chris Packham
2016-04-28 7:27 ` Richard Weinberger
2016-04-28 8:40 ` Ricard Wanderlof
2016-04-28 8:49 ` 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=5721CE82.7010907@nod.at \
--to=richard@nod.at \
--cc=Chris.Packham@alliedtelesis.co.nz \
--cc=Henry.Shen@alliedtelesis.co.nz \
--cc=beanhuo@micron.com \
--cc=han.xu@nxp.com \
--cc=linux-mtd@lists.infradead.org \
--cc=ricard.wanderlof@axis.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.