Hi, On Tue, 15 Jun 2021 at 15:31, Pintu Agarwal <pintu.ping@xxxxxxxxx> wrote: > > On Tue, 15 Jun 2021 at 10:42, Pintu Agarwal <pintu.ping@xxxxxxxxx> wrote: > > > > On Tue, 15 Jun 2021 at 03:53, Florian Fainelli <f.fainelli@xxxxxxxxx> wrote: > > > > > > > > > > > > On 6/14/2021 3:39 AM, Pintu Agarwal wrote: > > > > Hi All, > > > > > > > > With Kernel 4.14 we are getting squashfs error during bootup resulting > > > > in kernel panic. > > > > The details are below: > > > > Device: ARM-32 board with Cortex-A7 (Single Core) > > > > Storage: NAND Flash 512MiB > > > > Kernel Version: 4.14.170 (maybe with some Linaro updates) > > > > File system: Simple busybox with systemd (without Android) > > > > File system type: UBIFS + SQUASHFS > > > > UBI Volumes supported: rootfs (ro), others (rw) > > > > ------------------- > > > > > > > > When we try to flash the UBI images and then try to boot the device, > > > > we observe the below errors: > > > > > > Someone in The OpenWrt community seems to have run into this problem, > > > possibly on the exact same QCOM SoC than you and came up with the following: > > > > > > https://forum.openwrt.org/t/patch-squashfs-data-probably-corrupt/70480 > > > > > Thanks! > > Yes I have already seen this and even one more. > > https://www.programmersought.com/article/31513579159/ > > > > But I think these changes are not yet in the mainline right ? > > > > So, I wanted to know which are the exact patches which are already > > accepted in mainline ? > > Or, is it already mainlined ? > > > > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/log/fs/squashfs?h=next-20210611 > > From here, I see that we are only till this: > > ==> 2018-08-02: Squashfs: Compute expected length from inode size > > rather than block length > > > @Phillip Lougher, do you have any suggestions/comments on these errors ? > Why do you think these errors occur ? > Also, I noticed that even if these errors occur, the device may boot normally. > However, for some people it does not boot at all. > It seems we have fixed this issue now from bootloader. I think it is related to -F (free space fixup) flag for ubifs partition. http://www.linux-mtd.infradead.org/faq/ubifs.html#L_free_space_fixup During flashing, we are trying to remove -F flag from ubifs image, but I think this should be avoided for squashfs image. I guess this issue might occur if we are trying to mixup squashfs/ubifs volumes together ? Or, we are trying to flash squashfs image on UBIFS volume ?
