From: Artem Bityutskiy <dedekind1@gmail.com>
To: Atlant Schmidt <aschmidt@dekaresearch.com>
Cc: Linux mtd <linux-mtd@lists.infradead.org>,
Ricard Wanderlof <ricardw@axis.com>,
'Ricard Wanderlof' <ricard.wanderlof@axis.com>,
Shmulik Ladkani <shmulik.ladkani@gmail.com>
Subject: RE: Userspace write to UBI partitions
Date: Wed, 08 Feb 2012 15:58:06 +0200 [thread overview]
Message-ID: <1328709486.22240.65.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <0A40042D85E7C84DB443060EC44B3FD332A14AAF7D@dekaexchange07.deka.local>
[-- Attachment #1: Type: text/plain, Size: 670 bytes --]
On Wed, 2012-02-08 at 08:49 -0500, Atlant Schmidt wrote:
> All:
>
> But there are times when you really want a block erased
> and erased NOW; in that case, "unmap" isn't what you
> want as it only schedules the PEB for erasure at some
> future time. And if a power cut intervenes, that
> scheduling for erasure may be lost and the ultimate
> erasure may not take place for a long, long time.
>
> So if you really intended to destroy the data, "unmap"
> is not the correct function to call.
In this case you should first unmap and than map:
http://www.linux-mtd.infradead.org/doc/ubi.html#L_map
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2012-02-08 13:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-07 15:20 Userspace write to UBI partitions Ricard Wanderlof
2012-02-07 16:29 ` Shmulik Ladkani
2012-02-07 16:36 ` Ricard Wanderlof
2012-02-07 17:09 ` Shmulik Ladkani
2012-02-08 7:35 ` Ricard Wanderlof
2012-02-08 12:00 ` Artem Bityutskiy
2012-02-08 12:20 ` Ricard Wanderlof
2012-02-08 11:59 ` Artem Bityutskiy
2012-02-08 12:18 ` Ricard Wanderlof
2012-02-08 13:49 ` Atlant Schmidt
2012-02-08 13:58 ` Artem Bityutskiy [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=1328709486.22240.65.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=aschmidt@dekaresearch.com \
--cc=linux-mtd@lists.infradead.org \
--cc=ricard.wanderlof@axis.com \
--cc=ricardw@axis.com \
--cc=shmulik.ladkani@gmail.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