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: Thu, 28 Apr 2016 09:27:15 +0200 [thread overview]
Message-ID: <5721BB53.6010008@nod.at> (raw)
In-Reply-To: <808151eb1f5a4d63ae100d9e6b29e550@svr-chch-ex1.atlnz.lc>
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.
Also erase itself is a problem (at least on UBIFS), it does not erase blocks
synchronous and also not immediately after they are no longer needed.
So, you'd have to touch some code...
Blindly doing a synchronous erase will hurt the performance as you
block the callers.
Thanks,
//richard
next prev parent reply other threads:[~2016-04-28 7:27 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 [this message]
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=5721BB53.6010008@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).