From: Sascha Hauer <s.hauer@pengutronix.de>
To: Alexander Stein <alexander.stein@systec-electronic.com>
Cc: barebox@lists.infradead.org,
"Daniel Krüger" <daniel.krueger@systec-electronic.com>
Subject: Re: UBIFS recovery fails in barebox while Linux suceeds
Date: Wed, 2 Mar 2016 20:56:13 +0100 [thread overview]
Message-ID: <20160302195613.GU9224@pengutronix.de> (raw)
In-Reply-To: <3665455.GH0lG2JcVq@ws-stein>
On Wed, Mar 02, 2016 at 05:19:08PM +0100, Alexander Stein wrote:
> Hi,
>
> in case a UBIFS needs recovery (unclean write or whatever on NOR
> flash) it is possible that barebox fails to do so while Linux suceeds.
> The main cause, IMHO, is that Linux takes max_write_size into account
> (starting with commit 2765df7da540687c4d57ca840182122f074c5b9c "UBIFS:
> use max_write_size during recovery") while barebox doesn't. Apparently
> is_last_write (fs/ubifs/recovery.c) results differently due to that
> fact which explains why recovery progress differently. I don't know
> which linux version the ubifs code in barebox is taken from but I
> guess this needs to be updated. Are there any plans?
The barebox UBIFS code is taken from U-Boot 2013.07 which is taken from
Linux-2.6.29-rc6, so indeed the code is quite old. U-Boot has updated
UBIFS support to Linux-4.2. The question is if we update UBIFS from
U-Boot or directly from the Kernel, I have no idea which way is easier.
Currently there are no plans to update UBIFS, but of course you are
invited to create them ;)
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2016-03-02 19:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-02 16:19 UBIFS recovery fails in barebox while Linux suceeds Alexander Stein
2016-03-02 19:56 ` Sascha Hauer [this message]
2016-03-03 7:16 ` Alexander Stein
2016-03-03 8:28 ` Sascha Hauer
2016-03-03 8:38 ` Alexander Stein
2016-03-03 9:23 ` Sascha Hauer
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=20160302195613.GU9224@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=alexander.stein@systec-electronic.com \
--cc=barebox@lists.infradead.org \
--cc=daniel.krueger@systec-electronic.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.