The same cpio that generates the archive seems to give checksum errors when extracting it.

Triacta

unread,

Mar 6, 2017, 11:45:56 PM3/6/17

to swupdate

I am having checksum errors with SWUpdate, so I wanted to make sure that my version of cpio works with the cpio library that SWUpdate is using. However, I found that even cpio itself is not working as I expect it (but perhaps I have an incorrect understanding on how it should work):

>0< alain@mbp-vmw-ub1 Mon Mar 06 11:27 PM ~/swupdate/images > uname -a

Linux mbp-vmw-ub1 4.4.0-62-generic #83~14.04.1-Ubuntu SMP Wed Jan 18 18:10:30 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

>0< alain@mbp-vmw-ub1 Mon Mar 06 11:31 PM ~/swupdate/images > which cpio

/bin/cpio

>0< alain@mbp-vmw-ub1 Mon Mar 06 11:31 PM ~/swupdate/images > cpio --version

cpio (GNU cpio) 2.11

License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>.

This is free software: you are free to change and redistribute it.

There is NO WARRANTY, to the extent permitted by law.

Written by Phil Nelson, David MacKenzie, John Oleynick,

and Sergey Poznyakoff.

>2< alain@mbp-vmw-ub1 Mon Mar 06 11:27 PM ~/swupdate/images > ls -l

total 192524

-rw-r--r-- 1 alain alain 121634816 Mar 6 23:17 g5-dev-image-imx6ul-var-dart.ext4

-rw-r--r-- 1 alain alain 75497472 Mar 6 23:17 g5-prod-image-imx6ul-var-dart.ext4

-rw-r--r-- 1 alain alain 1065 Mar 6 23:17 sw-description

>0< alain@mbp-vmw-ub1 Mon Mar 06 11:27 PM ~/swupdate/images >

>0< alain@mbp-vmw-ub1 Mon Mar 06 11:23 PM ~/swupdate/images > ls -r | cpio -ov -H crc > ../cpio/with-crc.swu

sw-description

g5-prod-image-imx6ul-var-dart.ext4

g5-dev-image-imx6ul-var-dart.ext4

385028 blocks

>0< alain@mbp-vmw-ub1 Mon Mar 06 11:23 PM ~/swupdate/images > ls -r | cpio -ov > ../cpio/no-crc.swu

sw-description

g5-prod-image-imx6ul-var-dart.ext4

g5-dev-image-imx6ul-var-dart.ext4

385027 blocks

>0< alain@mbp-vmw-ub1 Mon Mar 06 11:23 PM ~/swupdate/images > cd ../cpio/

>0< alain@mbp-vmw-ub1 Mon Mar 06 11:23 PM ~/swupdate/cpio > ls

no-crc.swu with-crc.swu

>0< alain@mbp-vmw-ub1 Mon Mar 06 11:23 PM ~/swupdate/cpio > cpio -t < no-crc.swu

sw-description

g5-prod-image-imx6ul-var-dart.ext4

g5-dev-image-imx6ul-var-dart.ext4

385027 blocks

>0< alain@mbp-vmw-ub1 Mon Mar 06 11:24 PM ~/swupdate/cpio > cpio -t < with-crc.swu

sw-description

g5-prod-image-imx6ul-var-dart.ext4

g5-dev-image-imx6ul-var-dart.ext4

385028 blocks

>0< alain@mbp-vmw-ub1 Mon Mar 06 11:24 PM ~/swupdate/cpio > cpio -t --only-verify-crc < no-crc.swu

sw-description

cpio: sw-description: checksum error (0x0, should be 0xf07392ec)

g5-prod-image-imx6ul-var-dart.ext4

cpio: g5-prod-image-imx6ul-var-dart.ext4: checksum error (0x0, should be 0xf07392ec)

g5-dev-image-imx6ul-var-dart.ext4

cpio: g5-dev-image-imx6ul-var-dart.ext4: checksum error (0x0, should be 0xf07392ec)

385027 blocks

>0< alain@mbp-vmw-ub1 Mon Mar 06 11:24 PM ~/swupdate/cpio > cpio -t --only-verify-crc < with-crc.swu

sw-description

g5-prod-image-imx6ul-var-dart.ext4

cpio: g5-prod-image-imx6ul-var-dart.ext4: checksum error (0x117c24ad9, should be 0x17c24ad9)

g5-dev-image-imx6ul-var-dart.ext4

cpio: g5-dev-image-imx6ul-var-dart.ext4: checksum error (0x1bd77e6f4, should be 0xbd77e6f4)

385028 blocks

>0< alain@mbp-vmw-ub1 Mon Mar 06 11:25 PM ~/swupdate/cpio > cpio -iv < no-crc.swu

sw-description

g5-prod-image-imx6ul-var-dart.ext4

g5-dev-image-imx6ul-var-dart.ext4

385027 blocks

>0< alain@mbp-vmw-ub1 Mon Mar 06 11:25 PM ~/swupdate/cpio > rm sw-description g5*

>0< alain@mbp-vmw-ub1 Mon Mar 06 11:25 PM ~/swupdate/cpio > cpio -iv < with-crc.swu

sw-description

cpio: g5-prod-image-imx6ul-var-dart.ext4: checksum error (0x117c24ad9, should be 0x17c24ad9)

g5-prod-image-imx6ul-var-dart.ext4

cpio: g5-dev-image-imx6ul-var-dart.ext4: checksum error (0x1bd77e6f4, should be 0xbd77e6f4)

g5-dev-image-imx6ul-var-dart.ext4

385028 blocks

>0< alain@mbp-vmw-ub1 Mon Mar 06 11:25 PM ~/swupdate/cpio > ls

g5-dev-image-imx6ul-var-dart.ext4 g5-prod-image-imx6ul-var-dart.ext4 no-crc.swu sw-description with-crc.swu

>0< alain@mbp-vmw-ub1 Mon Mar 06 11:25 PM ~/swupdate/cpio > diff g5-prod-image-imx6ul-var-dart.ext4 ../images/g5-prod-image-imx6ul-var-dart.ext4

>0< alain@mbp-vmw-ub1 Mon Mar 06 11:25 PM ~/swupdate/cpio > diff g5-dev-image-imx6ul-var-dart.ext4 ../images/g5-dev-image-imx6ul-var-dart.ext4

>0< alain@mbp-vmw-ub1 Mon Mar 06 11:26 PM ~/swupdate/cpio > diff sw-description ../images/sw-description

>0< alain@mbp-vmw-ub1 Mon Mar 06 11:26 PM ~/swupdate/cpio > rm sw* g5*

>0< alain@mbp-vmw-ub1 Mon Mar 06 11:26 PM ~/swupdate/cpio > ls

no-crc.swu with-crc.swu

>0< alain@mbp-vmw-ub1 Mon Mar 06 11:26 PM ~/swupdate/cpio > cpio -iv -H crc < with-crc.swu

sw-description

cpio: g5-prod-image-imx6ul-var-dart.ext4: checksum error (0x117c24ad9, should be 0x17c24ad9)

g5-prod-image-imx6ul-var-dart.ext4

cpio: g5-dev-image-imx6ul-var-dart.ext4: checksum error (0x1bd77e6f4, should be 0xbd77e6f4)

g5-dev-image-imx6ul-var-dart.ext4

385028 blocks

>0< alain@mbp-vmw-ub1 Mon Mar 06 11:26 PM ~/swupdate/cpio > ls

g5-dev-image-imx6ul-var-dart.ext4 g5-prod-image-imx6ul-var-dart.ext4 no-crc.swu sw-description with-crc.swu

>0< alain@mbp-vmw-ub1 Mon Mar 06 11:26 PM ~/swupdate/cpio > diff g5-prod-image-imx6ul-var-dart.ext4 ../images/g5-prod-image-imx6ul-var-dart.ext4

>0< alain@mbp-vmw-ub1 Mon Mar 06 11:26 PM ~/swupdate/cpio > diff g5-dev-image-imx6ul-var-dart.ext4 ../images/g5-dev-image-imx6ul-var-dart.ext4

>0< alain@mbp-vmw-ub1 Mon Mar 06 11:27 PM ~/swupdate/cpio > diff sw-description ../images/sw-description

Note the following:

1. In swupdate.bbclass, I see that it uses the command '... cpio -ov -H crc ...' so assuming that the cpio library that SWUpdate uses is the same as what the cpio binary links with, it is not surprising that SWupdate gives the same checksum errors as I'm getting with the command-line (for the file with-crc.swu)

2. I can understand that if I don't generate a checksum, then checksum verification fails (for the file no-crc.swu)

3. In both cases (with or without checksum) cpio continues to extract the files. When I diff them, they are the exact same as the originals. However, SWUpdate refuses to extract the files if a checksum error occurs.

Please help.

okt...@gmail.com

unread,

Mar 7, 2017, 6:10:22 AM3/7/17

to swupdate

> However, I found that even cpio itself is not working as I expect it

See for example <https://bugzilla.redhat.com/show_bug.cgi?id=1415081>; the issue is not RHEL-related, but affects cpio on Ubuntu as well.

However, I have not seen SWUpdate to refuse to extract files from affected .swu image.

Message has been deleted

Stefano Babic

unread,

Mar 7, 2017, 10:12:20 AM3/7/17

to alain.j...@gmail.com, swupdate, okt...@gmail.com

On 07/03/2017 16:08, alain.j...@gmail.com wrote:

> Thanks but the bug you link to relates to files > 200 MB. As I show in my original post, my files are less than 200MB.
>
> Stefano, I forgot to mention that I'm running Swupdate v2016.07.0
>

There are not know issues regarding CPIO on any distributions together
with SWUpdate. Try to build with meta-swupdate - rather, it is not
possible to understand what is going wrong on your PC.

Best regards,
Stefano Babic

--
Meet DENX at the Embedded World Trade Show
14 Mar - 16 Mar 2017, Nuremberg Trade Fair Centre, Hall 4, Booth 581
--
=====================================================================
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sba...@denx.de
=====================================================================

Triacta

unread,

Mar 7, 2017, 11:09:47 AM3/7/17

to swupdate, sba...@denx.de

Hi Stefano,

1. a) Could you please run:

cpio --version

on your system and provide the output?

1. b) what library are you using to extract the files and check the checksum? Is it the same as the library that cpio links with?

1. c) Is there an configuration option to skip checksum verification?

2. I did build swupdate with meta-swupdate.

3. I used the bitbake devshell to find out which cpio the swupdate.bbclass line 162 [

line = 'for i in ' + ' '.join(list_for_cpio) + '; do echo $i;done | cpio -ov -H crc >' + os.path.join(deploydir,d.getVar('IMAGE_NAME', True) + '.swu')

] is calling:

>0< alain@mbp-vmw-ub1 Tue Mar 07 10:28 AM /media/alain/Yocto/var-mx6ul-mx7-yocto-jethro/build-fb > bitbake g5-swu-image -c devshell

Loading cache: 100% |########################################################################################################################################################| ETA: 00:00:00

Loaded 2785 entries from dependency cache.

Parsing recipes: 100% |######################################################################################################################################################| Time: 00:00:00

Parsing of 2223 .bb files complete (2218 cached, 5 parsed). 2789 targets, 429 skipped, 5 masked, 0 errors.

NOTE: Resolving any missing task queue dependencies

Build Configuration:

BB_VERSION = "1.28.0"

BUILD_SYS = "x86_64-linux"

NATIVELSBSTRING = "Ubuntu-14.04"

TARGET_SYS = "arm-poky-linux-gnueabi"

MACHINE = "imx6ul-var-dart"

DISTRO = "fsl-imx-fb"

DISTRO_VERSION = "4.1.15-1.2.0"

TUNE_FEATURES = "arm armv7a vfp neon callconvention-hard cortexa7"

TARGET_FPU = "vfp-neon"

Stefano Babic

unread,

Mar 7, 2017, 11:14:37 AM3/7/17

to Triacta, swupdate, sba...@denx.de

On 07/03/2017 17:09, Triacta wrote:
> *Hi Stefano,*
> *
> *
> *1. a) Could you please run:*
> *
> *
> *cpio --version*
> *
> *
> *on your system and provide the output?*
> *

stefano@papero:~$ cpio --version

cpio (GNU cpio) 2.11
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by Phil Nelson, David MacKenzie, John Oleynick,
and Sergey Poznyakoff.

But I have no idea what you want to prove...

Best regards,
Stefano Babic

> *
> *1. b) what library are you using to extract the files and check the
> checksum? Is it the same as the library that cpio links with?*
> *
> *
> *1. c) Is there an configuration option to skip checksum verification?*

>
>
>
>
>
> 2. I did build swupdate with meta-swupdate.
>
> 3. I used the bitbake devshell to find out which cpio the
> swupdate.bbclass line 162 [
> line = 'for i in ' + ' '.join(list_for_cpio) + '; do echo $i;done |

> *cpio -ov -H crc* >' + os.path.join(deploydir,d.getVar('IMAGE_NAME',

> True) + '.swu')
> ] is calling:
>
>>0< alain@mbp-vmw-ub1 Tue Mar 07 10:28 AM

> /media/alain/Yocto/var-mx6ul-mx7-yocto-jethro/build-fb > *bitbake
> g5-swu-image -c devshell*

> *meta-swupdate = "master:6cc053531bce76a1fe98b83e36b4a97ca9c672c3"*

>
> NOTE: Preparing RunQueue
> NOTE: Executing SetScene Tasks
> NOTE: Executing RunQueue Tasks
> Currently 1 running tasks (95 of 95):
> 0: g5-swu-image-1.0-r0 do_devshell (pid 12031)
> NOTE: Tasks Summary: Attempted 95 tasks of which 94 didn't need to be
> rerun and all succeeded.
>
>
>>0< root@mbp-vmw-ub1 Tue Mar 07 10:29 AM
> /media/alain/Yocto/var-mx6ul-mx7-yocto-jethro/build-fb/tmp/work/imx6ul_var_dart-poky-linux-gnueabi/g5-swu-image/1.0-r0/g5-swu-image

>> *which cpio*

> /bin/cpio
>>0< root@mbp-vmw-ub1 Tue Mar 07 10:29 AM
> /media/alain/Yocto/var-mx6ul-mx7-yocto-jethro/build-fb/tmp/work/imx6ul_var_dart-poky-linux-gnueabi/g5-swu-image/1.0-r0/g5-swu-image

>> *cpio --version*
> *cpio (GNU cpio) 2.11*

> Copyright (C) 2010 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later
> <http://gnu.org/licenses/gpl.html>.
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.
>
> Written by Phil Nelson, David MacKenzie, John Oleynick,
> and Sergey Poznyakoff.
>
> Therefore swupdate.bbclass calls whatever cpio is in the PATH, and given
> that Yocto does not provide one, it is picked up from the system's
> /bin/cpio.
>
> 4. I provisioned a virtual server on Vultr.com with an Ubuntu 16.10 x64
> from scratch. I ran the following commands:
>
>

> alain@vultr1:~/swupdate/images$ *which cpio*
> /bin/cpio
> alain@vultr1:~/swupdate/images$ *cpio --version*
> *cpio (GNU cpio) 2.11*

> Copyright (C) 2010 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later
> <http://gnu.org/licenses/gpl.html>.
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.
>
> Written by Phil Nelson, David MacKenzie, John Oleynick,
> and Sergey Poznyakoff.
>
> Then, I tested to see if I can reproduce the mentioned cpio bug:
>

> alain@vultr1:~/swupdate/images$ *SIZES="1 2 4 8 16 32 64 128 10 20 30 40

> 50 60 70 80 90 100 110 120 130 140 150 160 170 180 190 200 210 220 230

> 240 250"*
> alain@vultr1:~/swupdate/images$ *for i in $SIZES; do*
>> *dd if=/dev/urandom of=rand-$i bs=1M count=$i*
>> *echo rand-$i | cpio --create --format=crc --verbose > rand-$i.cpio*
>> *cpio --extract --only-verify-crc < rand-$i.cpio*
>> *done*

> *cpio: rand-64: checksum error (0x1fdf3ccca, should be 0xfdf3ccca)*

> *cpio: rand-40: checksum error (0x13ebb7a7e, should be 0x3ebb7a7e)*

> sba...@denx.de <javascript:>
> =====================================================================
>
> --
> You received this message because you are subscribed to the Google
> Groups "swupdate" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to swupdate+u...@googlegroups.com
> <mailto:swupdate+u...@googlegroups.com>.
> To post to this group, send email to swup...@googlegroups.com
> <mailto:swup...@googlegroups.com>.
> For more options, visit https://groups.google.com/d/optout.

Triacta

unread,

Mar 7, 2017, 11:54:37 AM3/7/17

to swupdate, alain....@triacta.com, sba...@denx.de

I am not trying to prove anything. I am simply trying to make SWUpdate work in my setup.

It seems that the difference between cpio and swupdate is that cpio extracts the files even though it displays that there is a checksum error, but swupdate does not extract the files when it encounters a checksum error.

With cpio, even if it says there is a checksum error, when I compare the extracted file to the original file, there is no difference.

So, if the library you are using inside swupdate is the same as the one that cpio is using, perhaps this library has a bug that it doesn't calculate checksums properly, and incorrectly reports back to the caller that there was an error in the checksum.

In the case of cpio, the caller seems to be ignoring the checksum error and continuing with the extraction.

In the case of swupdate, the caller seems to be stopping if it gets a checksum error.

So, if I could replicate your setup where your version of cpio does actually generate the proper checksum, then my swupdate will properly verify the checksum and continue to extract it.

Another question is: have you tried images larger than 40MB ?

Stefano Babic

unread,

Mar 7, 2017, 12:11:10 PM3/7/17

to Triacta, swupdate, sba...@denx.de

On 07/03/2017 17:54, Triacta wrote:
> I am not trying to prove anything. I am simply trying to make SWUpdate
> work in my setup.
>
> It seems that the difference between cpio and swupdate is that cpio
> extracts the files even though it displays that there is a checksum
> error, but swupdate does not extract the files when it encounters a
> checksum error.
>
> With cpio, even if it says there is a checksum error, when I compare the
> extracted file to the original file, there is no difference.
>
> So, if the library you are using inside swupdate is the same as the one
> that cpio is using, perhaps this library has a bug that it doesn't
> calculate checksums properly, and incorrectly reports back to the caller
> that there was an error in the checksum.
>
> In the case of cpio, the caller seems to be ignoring the checksum error
> and continuing with the extraction.
> In the case of swupdate, the caller seems to be stopping if it gets a
> checksum error.
>
> So, if I could replicate your setup where your version of cpio does
> actually generate the proper checksum, then my swupdate will properly
> verify the checksum and continue to extract it.
>
> Another question is: have you tried images larger than 40MB ?
>

See log, file is quite 890MB:

stefano@papero:~/Projects/swupdate$ ./swupdate -Hpc:1.0 -v -i
tests/auto/boards/pc/test4/software_pc_test4.swu
Swupdate v2017.1.0

Licensed under GPLv2. See source distribution for detailed copyright
notices.

Searching for custom LUA handlers :[string "require
("swupdate_handlers")"]:1: module 'swupdate_handlers' not found:
no field package.preload['swupdate_handlers']
no file '/usr/local/share/lua/5.2/swupdate_handlers.lua'
no file '/usr/local/share/lua/5.2/swupdate_handlers/init.lua'
no file '/usr/local/lib/lua/5.2/swupdate_handlers.lua'
no file '/usr/local/lib/lua/5.2/swupdate_handlers/init.lua'
no file '/usr/share/lua/5.2/swupdate_handlers.lua'
no file '/usr/share/lua/5.2/swupdate_handlers/init.lua'
no file './swupdate_handlers.lua'
no file '/usr/local/lib/lua/5.2/swupdate_handlers.so'
no file '/usr/lib/x86_64-linux-gnu/lua/5.2/swupdate_handlers.so'
no file '/usr/lib/lua/5.2/swupdate_handlers.so'
no file '/usr/local/lib/lua/5.2/loadall.so'
no file './swupdate_handlers.so'
Custom handlers not found, no error, skipping...

Running on pc Revision 1.0
Registered handlers:
archive
tar
flash
flash-hamming1
raw
rawfile
ubivol
ubipartition
lua
shellscript
preinstall
postinstall
remote
Main loop Daemon
[NOTIFY] : SWUPDATE running : [extract_sw_description] : Found file:
filename sw-description
size 291
checksum 0x4e01 VERIFIED

Version 0.1.0
[NOTIFY] : SWUPDATE running : [parse_hw_compatibility] : Accepted Hw
Revision : 1.0
[NOTIFY] : SWUPDATE running : [parse_scripts] : Found Script:
shellscript_logger.sh

[NOTIFY] : SWUPDATE running : [parse_files] : Found File :
IncrediblePBX13.2.iso --> /tmp/test (ROOTFS)

[NOTIFY] : SWUPDATE running : [check_hw_compatibility] : Hardware pc
Revision: 1.0
[NOTIFY] : SWUPDATE running : [check_hw_compatibility] : Hardware
compatibility verified
[NOTIFY] : SWUPDATE running : [cpio_scan] : Found file:
filename IncrediblePBX13.2.iso
size 890241024
REQUIRED

[NOTIFY] : SWUPDATE running : [cpio_scan] : Found file:
filename shellscript_logger.sh
size 261
REQUIRED

[NOTIFY] : SWUPDATE running : [extract_next_file] : Copied file:
filename shellscript_logger.sh
size 261
checksum 0x5476 VERIFIED

[NOTIFY] : SWUPDATE running : [execute_shell_script] : Calling shell
script /tmp/shellscript_logger.sh preinst: return with 0
[NOTIFY] : SWUPDATE running : [install_single_image] : Found installer
for stream IncrediblePBX13.2.iso rawfile
[NOTIFY] : SWUPDATE running : [install_raw_file] : Installing file
IncrediblePBX13.2.iso on /tmp/test

[NOTIFY] : SWUPDATE running : [execute_shell_script] : Calling shell
script /tmp/shellscript_logger.sh postinst: return with 0
Software updated successfully
Please reboot the device to start the new software
[NOTIFY] : SWUPDATE successful !

Best regards,
Stefano Babic

--
Meet DENX at the Embedded World Trade Show
14 Mar - 16 Mar 2017, Nuremberg Trade Fair Centre, Hall 4, Booth 581
--
=====================================================================
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sba...@denx.de

=====================================================================

Roman Kalashnikov

unread,

Aug 23, 2017, 6:29:14 PM8/23/17

to swupdate

Hi!

I agree, for example if raw image size larger then 2.147Gb swupdate read incorrect image size and can not verify checksum. It occurs because cpio have bug in file src/copyout.c function read_for_checksum getting incorrect file size type - int. This means file_size can be less then zero when your file size larger then 2Gb... It should have type off_t for correct storing file size. Also in same function should be:

off_t bytes_left;

вторник, 7 марта 2017 г., 7:45:56 UTC+3 пользователь Triacta написал:

Stefano Babic

unread,

Aug 24, 2017, 2:39:48 AM8/24/17

to Roman Kalashnikov, swupdate

On 24/08/2017 00:29, Roman Kalashnikov wrote:
> Hi!
> I agree, for example if raw image size larger then 2.147Gb swupdate read
> incorrect image size and can not verify checksum. It occurs because cpio

> have bug in file *src/copyout.c* function *read_for_checksum* getting
> incorrect file size type - *int*. This means *file_size* can be less

> then zero when your file size larger then 2Gb... It should have

> type *off_t*for correct storing file size. Also in same function should be:
> *off_t* bytes_left;

>
> вторник, 7 марта 2017 г., 7:45:56 UTC+3 пользователь Triacta написал:
>
> I am having checksum errors with SWUpdate, so I wanted to make sure
> that my version of cpio works with the cpio library that SWUpdate is
> using. However, I found that even cpio itself is not working as I
> expect it (but perhaps I have an incorrect understanding on how it
> should work):
>
> >0< alain@mbp-vmw-ub1 Mon Mar 06 11:27 PM ~/swupdate/images >

> *uname -a*

> Linux mbp-vmw-ub1 4.4.0-62-generic #83~14.04.1-Ubuntu SMP Wed Jan 18
> 18:10:30 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
> >0< alain@mbp-vmw-ub1 Mon Mar 06 11:31 PM ~/swupdate/images >

> *which cpio*

> /bin/cpio
> >0< alain@mbp-vmw-ub1 Mon Mar 06 11:31 PM ~/swupdate/images >

> *cpio --version*

> cpio (GNU cpio) 2.11
> Copyright (C) 2010 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later

> <http://gnu.org/licenses/gpl.html <http://gnu.org/licenses/gpl.html>>.

> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.
>
> Written by Phil Nelson, David MacKenzie, John Oleynick,
> and Sergey Poznyakoff.
>

> >2< alain@mbp-vmw-ub1 Mon Mar 06 11:27 PM ~/swupdate/images > *ls -l*

> total 192524
> -rw-r--r-- 1 alain alain 121634816 Mar 6 23:17
> g5-dev-image-imx6ul-var-dart.ext4
> -rw-r--r-- 1 alain alain 75497472 Mar 6 23:17
> g5-prod-image-imx6ul-var-dart.ext4
> -rw-r--r-- 1 alain alain 1065 Mar 6 23:17 sw-description
> >0< alain@mbp-vmw-ub1 Mon Mar 06 11:27 PM ~/swupdate/images >
>

> >0< alain@mbp-vmw-ub1 Mon Mar 06 11:23 PM ~/swupdate/images > *ls
> -r | cpio -ov -H crc > ../cpio/with-crc.swu*

> sw-description
> g5-prod-image-imx6ul-var-dart.ext4
> g5-dev-image-imx6ul-var-dart.ext4
> 385028 blocks

> >0< alain@mbp-vmw-ub1 Mon Mar 06 11:23 PM ~/swupdate/images > *ls
> -r | cpio -ov > ../cpio/no-crc.swu*

> sw-description
> g5-prod-image-imx6ul-var-dart.ext4
> g5-dev-image-imx6ul-var-dart.ext4
> 385027 blocks

> >0< alain@mbp-vmw-ub1 Mon Mar 06 11:23 PM ~/swupdate/images > *cd
> ../cpio/*
> >0< alain@mbp-vmw-ub1 Mon Mar 06 11:23 PM ~/swupdate/cpio > *ls*
> no-crc.swu with-crc.swu
> >0< alain@mbp-vmw-ub1 Mon Mar 06 11:23 PM ~/swupdate/cpio > *cpio
> -t < no-crc.swu*

> sw-description
> g5-prod-image-imx6ul-var-dart.ext4
> g5-dev-image-imx6ul-var-dart.ext4
> 385027 blocks

> >0< alain@mbp-vmw-ub1 Mon Mar 06 11:24 PM ~/swupdate/cpio > *cpio
> -t < with-crc.swu*

> sw-description
> g5-prod-image-imx6ul-var-dart.ext4
> g5-dev-image-imx6ul-var-dart.ext4
> 385028 blocks

> >0< alain@mbp-vmw-ub1 Mon Mar 06 11:24 PM ~/swupdate/cpio > *cpio
> -t --only-verify-crc < no-crc.swu*

> sw-description
> cpio: sw-description: checksum error (0x0, should be 0xf07392ec)
> g5-prod-image-imx6ul-var-dart.ext4
> cpio: g5-prod-image-imx6ul-var-dart.ext4: checksum error (0x0,
> should be 0xf07392ec)
> g5-dev-image-imx6ul-var-dart.ext4
> cpio: g5-dev-image-imx6ul-var-dart.ext4: checksum error (0x0, should
> be 0xf07392ec)
> 385027 blocks

> >0< alain@mbp-vmw-ub1 Mon Mar 06 11:24 PM ~/swupdate/cpio > *cpio
> -t --only-verify-crc < with-crc.swu*

> sw-description
> g5-prod-image-imx6ul-var-dart.ext4
> cpio: g5-prod-image-imx6ul-var-dart.ext4: checksum error
> (0x117c24ad9, should be 0x17c24ad9)
> g5-dev-image-imx6ul-var-dart.ext4
> cpio: g5-dev-image-imx6ul-var-dart.ext4: checksum error
> (0x1bd77e6f4, should be 0xbd77e6f4)
> 385028 blocks

> >0< alain@mbp-vmw-ub1 Mon Mar 06 11:25 PM ~/swupdate/cpio > *cpio
> -iv < no-crc.swu*

> sw-description
> g5-prod-image-imx6ul-var-dart.ext4
> g5-dev-image-imx6ul-var-dart.ext4
> 385027 blocks
> >0< alain@mbp-vmw-ub1 Mon Mar 06 11:25 PM ~/swupdate/cpio > rm
> sw-description g5*
> >0< alain@mbp-vmw-ub1 Mon Mar 06 11:25 PM ~/swupdate/cpio > cpio
> -iv < with-crc.swu
> sw-description
> cpio: g5-prod-image-imx6ul-var-dart.ext4: checksum error
> (0x117c24ad9, should be 0x17c24ad9)
> g5-prod-image-imx6ul-var-dart.ext4
> cpio: g5-dev-image-imx6ul-var-dart.ext4: checksum error
> (0x1bd77e6f4, should be 0xbd77e6f4)
> g5-dev-image-imx6ul-var-dart.ext4
> 385028 blocks

> >0< alain@mbp-vmw-ub1 Mon Mar 06 11:25 PM ~/swupdate/cpio > *ls*

> g5-dev-image-imx6ul-var-dart.ext4
> g5-prod-image-imx6ul-var-dart.ext4 no-crc.swu sw-description
> with-crc.swu

> >0< alain@mbp-vmw-ub1 Mon Mar 06 11:25 PM ~/swupdate/cpio > *diff
> g5-prod-image-imx6ul-var-dart.ext4
> ../images/g5-prod-image-imx6ul-var-dart.ext4*
> >0< alain@mbp-vmw-ub1 Mon Mar 06 11:25 PM ~/swupdate/cpio > *diff
> g5-dev-image-imx6ul-var-dart.ext4
> ../images/g5-dev-image-imx6ul-var-dart.ext4*
> >0< alain@mbp-vmw-ub1 Mon Mar 06 11:26 PM ~/swupdate/cpio > *diff
> sw-description ../images/sw-description*
> >0< alain@mbp-vmw-ub1 Mon Mar 06 11:26 PM ~/swupdate/cpio > *rm
> sw* g5**
> >0< alain@mbp-vmw-ub1 Mon Mar 06 11:26 PM ~/swupdate/cpio > *ls*
> no-crc.swu with-crc.swu
> >0< alain@mbp-vmw-ub1 Mon Mar 06 11:26 PM ~/swupdate/cpio > *cpio
> -iv -H crc < with-crc.swu*

> sw-description
> cpio: g5-prod-image-imx6ul-var-dart.ext4: checksum error
> (0x117c24ad9, should be 0x17c24ad9)
> g5-prod-image-imx6ul-var-dart.ext4
> cpio: g5-dev-image-imx6ul-var-dart.ext4: checksum error
> (0x1bd77e6f4, should be 0xbd77e6f4)
> g5-dev-image-imx6ul-var-dart.ext4
> 385028 blocks

> >0< alain@mbp-vmw-ub1 Mon Mar 06 11:26 PM ~/swupdate/cpio > *ls*

> g5-dev-image-imx6ul-var-dart.ext4
> g5-prod-image-imx6ul-var-dart.ext4 no-crc.swu sw-description
> with-crc.swu

> >0< alain@mbp-vmw-ub1 Mon Mar 06 11:26 PM ~/swupdate/cpio > *diff
> g5-prod-image-imx6ul-var-dart.ext4
> ../images/g5-prod-image-imx6ul-var-dart.ext4*
> >0< alain@mbp-vmw-ub1 Mon Mar 06 11:26 PM ~/swupdate/cpio > *diff
> g5-dev-image-imx6ul-var-dart.ext4
> ../images/g5-dev-image-imx6ul-var-dart.ext4*
> >0< alain@mbp-vmw-ub1 Mon Mar 06 11:27 PM ~/swupdate/cpio > *diff
> sw-description ../images/sw-description*
>
>
> Note the following:
>
> 1. In swupdate.bbclass, I see that it uses the command '*... cpio
> -ov -H crc ...*' so assuming that the cpio library that SWUpdate

> uses is the same as what the cpio binary links with, it is not
> surprising that SWupdate gives the same checksum errors as I'm
> getting with the command-line (for the file with-crc.swu)
>
> 2. I can understand that if I don't generate a checksum, then
> checksum verification fails (for the file no-crc.swu)
>
> 3. In both cases (with or without checksum) cpio continues to
> extract the files. When I diff them, they are the exact same as the
> originals. However, SWUpdate refuses to extract the files if a
> checksum error occurs.
>
> Please help.
>
>

Check the ML archive this was already analyzed:

Bug analyses here:
https://groups.google.com/forum/#!topic/swupdate/ABFNVf9hYOo

Fix to cpio in meta-swupdate:
https://groups.google.com/forum/#!topic/swupdate/u3-7YxeW5wU

Patch to cpio ML:
http://lists.gnu.org/archive/html/bug-cpio/2017-07/index.html

Best regards,
Stefano Babic

--

Roman Kalashnikov

unread,

Aug 24, 2017, 2:55:54 AM8/24/17

to Stefano Babic, swupdate

It was reproduced on arch linux kernel 4.12 and cpio 2.12, also on ubuntu 16.10 kernel 4.8 the same error.
I was tried to use original source code from gnu.org and i was confused when found this error in latest original code (4.12).

Reply all

Reply to author

Forward