The upstream patch integrated in LIN10-3644 introduced a regression causing the following errors to be intermittently present in the logs: [ 27.342757] EXT4-fs (vdb1): mounting ext3 file system using the ext4 subsystem [ 27.345646] EXT4-fs (vdb1): mounted filesystem with ordered data mode. Opts: (null) [ 70.211734] EXT4-fs error (device vdb1): ext4_validate_block_bitmap:385: comm tar: bg 15: block 495851: invalid block bitmap [ 70.213620] EXT4-fs error (device vdb1): ext4_validate_block_bitmap:385: comm tar: bg 16: block 528875: invalid block bitmap [ 70.216565] EXT4-fs error (device vdb1): ext4_validate_block_bitmap:385: comm tar: bg 17: block 561899: invalid block bitmap [ 70.219591] EXT4-fs error (device vdb1): ext4_validate_block_bitmap:385: comm tar: bg 18: block 594923: invalid block bitmap [ 70.222537] EXT4-fs error (device vdb1): ext4_validate_block_bitmap:385: comm tar: bg 19: block 627947: invalid block bitmap [ 70.225442] EXT4-fs error (device vdb1): ext4_validate_block_bitmap:385: comm tar: bg 20: block 660971: invalid block bitmap [ 70.228336] EXT4-fs error (device vdb1): ext4_validate_block_bitmap:385: comm tar: bg 21: block 693995: invalid block bitmap The regression was fixed in upstream by commit https://github.com/torvalds/linux/commit/22be37acce25d66ecf6403fc8f44df9c5ded2372
setup.sh --machine intel-x86-64 --repo-jobs=40 --dl-layers IMAGE_INSTALL_append = " xz" bitbake wrlinux-image-glibc-std -- Boot in qemu with two disks -- mkfs -t ext3 -E stride=256 /dev/vdb1 mount /dev/vdb1 /mnt/test cd /mnt/test wget https://cdn.kernel.org/pub/linux/kernel/v4.x/linux-4.16.3.tar.xz tar xf linux-4.16.3.tar.xz
