lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOuPNLgquwOJg85kDcf67+4kTYP9N=45FvV+VDTJr6txYi5-wg@mail.gmail.com>
Date:   Tue, 9 Nov 2021 16:45:54 +0530
From:   Pintu Agarwal <pintu.ping@...il.com>
To:     open list <linux-kernel@...r.kernel.org>,
        linux-mtd <linux-mtd@...ts.infradead.org>,
        linux-fsdevel <linux-fsdevel@...r.kernel.org>,
        dm-devel@...hat.com, Phillip Lougher <phillip@...ashfs.org.uk>,
        Mikulas Patocka <mpatocka@...hat.com>,
        Richard Weinberger <richard@....at>,
        Florian Fainelli <f.fainelli@...il.com>,
        sumit.semwal@...aro.org, adriens@...gle.com
Subject: Re: Kernel-4.14: With ubuntu-18.04 building rootfs images and booting
 gives SQUASHFS error: xz decompression failed, data probably corrupt

Hi,

On Mon, 8 Nov 2021 at 20:00, Pintu Agarwal <pintu.ping@...il.com> wrote:
>
> Hi,
> Here are few details.
> * Linux Kernel: 4.14
> * Processor: Qualcomm Arm32 Cortex-A7
> * Storage: NAND 512MB
> * Platform: Simple busybox
> * Filesystem: UBIFS, Squashfs
> * Build system: Linux Ubuntu 18.04 with Yocto build system
> * Consists of nand raw partitions, squashfs ubi volumes.
>
> What we are trying to do:
> We are trying to boot dm-verity enabled rootfs on our system.
> The images for rootfs were generated on Ubuntu 18.04 machine using
> Yocto build system.
>
> Issue:
> Earlier, when we were using Ubuntu 16.04 to generate our images, the
> system was booting fine even with dm-verity enabled.
> Recently we switched to Ubuntu 18.04 build machine, and now with the
> same changes we are seeing the below squashfs error, just after the
> mount.
> Note: with 18.04 also our rootfs is mounting successfully and
> dm-verity is also working fine.
> We only get these squashfs errors flooded in the boot logs:
> {{{
> ....
> [    5.153479] device-mapper: init: dm-0 is ready
> [    5.334282] VFS: Mounted root (squashfs filesystem) readonly on device 253:0.
> ....
> [    8.954120] SQUASHFS error: xz decompression failed, data probably corrupt
> [    8.954153] SQUASHFS error: squashfs_read_data failed to read block 0x1106
> [    8.970316] SQUASHFS error: Unable to read data cache entry [1106]
> [    8.970349] SQUASHFS error: Unable to read page, block 1106, size 776c
> [    8.980298] SQUASHFS error: Unable to read data cache entry [1106]
> [    8.981911] SQUASHFS error: Unable to read page, block 1106, size 776c
> [    8.988280] SQUASHFS error: Unable to read data cache entry [1106]
> ....
> }}}
>
Just one question:
Is there any history about these squashfs errors while cross-compiling
images on Ubuntu 18.04 or higher ?


Thanks,
Pintu

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ