[OpenWrt-Devel] Factory startup issues since mount_root / libfstools improvements in Chaos Calmer
pieter.smith at philips.com
Wed Mar 29 10:01:55 EDT 2017
> On 03/28/2017 03:26 PM, Smith, Pieter wrote:
> > The refactoring in ba019965 eliminated an unneeded call to
> > volume_find() when
> > done() calls jffs2_switch(). Unfortunately the refactoring did not
> > take into account that volume_identify() has side-effects with the mtd
> > driver implementation and a second call to volume_identify() on the
> > same struct volume may render a different result.
> AFAIU this is about mtd driver, so volume_identify basically means
> Can you do some extra debugging for me and check which exact part of
> mtd_volume_identify has this side effect? I don't see which part of this
> function would affect volume identification in further calls.
I will see what I can do tomorrow.
> This may be a bit tricky to debug as you can't call volume_identify inside
> (at least without some recursive check). Can you handle this somehow?
> I'd like to make sure I understand this bug fully before pushing a fix.
> Also: which target uses jffs2 with ubi?!
A concession I grudgingly had to accept from Qualcomm on their IoE platform in
order to hit our market release. OpenWRT at that point in time still lacked a
lot of infrastructure, putting UBI/FS out of reach given the time constraints.
The information contained in this message may be confidential and legally protected under applicable law. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, forwarding, dissemination, or reproduction of this message is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original message.
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
More information about the openwrt-devel