From: Artem Bityutskiy <dedekind1@gmail.com>
To: Matthieu CASTET <matthieu.castet@parrot.com>
Cc: linux-mtd@lists.infradead.org, Adrian Hunter <adrian.hunter@nokia.com>
Subject: Re: [PATCH 2/2] UBIFS: add unstable pages problem description
Date: Tue, 19 Oct 2010 10:57:48 +0300 [thread overview]
Message-ID: <1287475068.9272.8.camel@localhost> (raw)
In-Reply-To: <1287396125-1890-1-git-send-email-dedekind1@gmail.com>
On Mon, 2010-10-18 at 13:02 +0300, Artem Bityutskiy wrote:
> From: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
>
> Describe a problem reported by Matthieu CASTET which is currently
> not handled by UBIFS.
>
> Signed-off-by: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
Matthiew, are you happy with this description? Does it properly reflect
your findings? Could you please correct, if not?
I'm starting working on your problem. Since I do not have much time,
I'll do a little everyday, but hope to come up with some patches this
week already. The thing is that it is a lot of work. We need to go
through a lot of UBI/UBIFS subsystems and analyze them.
Why a lot of work? Because we assumed everywhere we can rely on CRC - if
it is correct, we are safe. However, according to you this is not
reliable for unstable pages - you do not have guarantee that next time
you read it you will get correct data.
Also, I do not have HW to test this, so I expect you to help by testing,
are your testing set-ups kept ready? :-)
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2010-10-19 8:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-18 10:02 [PATCH 2/2] UBIFS: add unstable pages problem description Artem Bityutskiy
2010-10-19 7:57 ` Artem Bityutskiy [this message]
2010-10-20 9:52 ` Matthieu CASTET
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=1287475068.9272.8.camel@localhost \
--to=dedekind1@gmail.com \
--cc=adrian.hunter@nokia.com \
--cc=linux-mtd@lists.infradead.org \
--cc=matthieu.castet@parrot.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.