From: Richard Weinberger <richard@nod.at>
To: Chris Packham <Chris.Packham@alliedtelesis.co.nz>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
Henry Shen <Henry.Shen@alliedtelesis.co.nz>
Subject: Re: secure file deletion/SECRM support for JFFS2 and UBIFS
Date: Wed, 27 Apr 2016 23:55:15 +0200 [thread overview]
Message-ID: <57213543.2070107@nod.at> (raw)
In-Reply-To: <66249822349e4de191f8f67ca1a5c35c@svr-chch-ex1.atlnz.lc>
Am 27.04.2016 um 23:49 schrieb Chris Packham:
> On 04/27/2016 07:06 PM, Richard Weinberger wrote:
>> On Wed, Apr 27, 2016 at 9:05 AM, Richard Weinberger
>> <richard.weinberger@gmail.com> wrote:
>>>> Is that something people on this list would be interested in? I realize
>>>> JFFS2 is kind of in a twilight phase but we're really not able to
>>>> migrate some customers away from it.
>>>
>>> This is definitely a nice feature.
>>> But please keep in mind that you can overwrite data on flash. :-)
>>
>> Should be read "can't", of course...
>>
>
> You can't overwrite with arbitrary data. But for NOR flash at least you
> _can_ overwrite with 0 (at least I think you can). In other words if the
> erased state is 0xff you can write 0xaa you would not be able to write
> 0x55 without erasing the block first but you would be able to write 0x00.
>
> I was hoping to avoid having to do an immediate erase but if I'm wrong
> that's what we'd have to do.
Well, UBIFS and JFFS2 work on generic MTD, so having a special hack for NOR
is not really what we want.
Thanks,
//richard
next prev parent reply other threads:[~2016-04-27 21:55 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 [this message]
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
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=57213543.2070107@nod.at \
--to=richard@nod.at \
--cc=Chris.Packham@alliedtelesis.co.nz \
--cc=Henry.Shen@alliedtelesis.co.nz \
--cc=linux-mtd@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).