From: Artem Bityutskiy <dedekind1@gmail.com>
To: Atlant Schmidt <aschmidt@dekaresearch.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: Does UBI LEB-level access interlock happily with UBIfs access?
Date: Fri, 19 Sep 2014 20:24:11 +0300 [thread overview]
Message-ID: <1411147451.23429.20.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <0A40042D85E7C84DB443060EC44B3FD36D986A301C@dekaexchange07.deka.local>
On Fri, 2014-09-19 at 13:17 -0400, Atlant Schmidt wrote:
> But as I pointed, this will not force re-read of the volume table LEBs.
> To address this, you'd need to do some additional, not very difficult
> work.
Oh, and this won't make UBI re-read the EC and VID headers, so they may
bit-rot too.
So indeed it sounds like UBI needs a separate interface for this kind of
"scrub all bit-flips" issues. I do not think it is hard to do - all the
mechanisms are already implemented, so this would mostly be about
inventing good API.
--
Best Regards,
Artem Bityutskiy
next prev parent reply other threads:[~2014-09-19 17:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-16 14:04 Does UBI LEB-level access interlock happily with UBIfs access? Atlant Schmidt
2014-09-19 15:27 ` Artem Bityutskiy
2014-09-19 16:58 ` Atlant Schmidt
2014-09-19 17:13 ` Artem Bityutskiy
2014-09-19 17:17 ` Atlant Schmidt
2014-09-19 17:24 ` Artem Bityutskiy [this message]
2014-09-20 12:54 ` Richard Weinberger
2014-09-22 8:34 ` Ricard Wanderlof
2014-09-22 8:42 ` Richard Weinberger
2014-09-19 17:06 ` Brian Norris
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=1411147451.23429.20.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=aschmidt@dekaresearch.com \
--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