[U-Boot] ext4: crash when writing a file

["Brüns, Stefan" <Stefan.Bruens@rwth-aachen.de>]

On Freitag, 20. Januar 2017 18:32:49 CET S?bastien Szymanski wrote:
[...]
> Then under the sandbox I do the following:
> 
> U-Boot 2017.01-00002-g558e41e-dirty (Jan 20 2017 - 16:19:47 +0100)
> 
> DRAM:  256 MiB
> MMC:
> Using default environment
> 
> In:    serial
> Out:   serial
> Err:   serial
> SCSI:  Net:   No ethernet found.
> IDE:   Bus 0: not available
> 
> => host bind 0 /tftproot/rootfs.raw
> 
> => ls host 0:2
> <DIR>       1024 .
> <DIR>       1024 ..
> <DIR>      16384 lost+found
> <DIR>       1024 var
> <DIR>       1024 run
> <DIR>       1024 root
> <DIR>       1024 media
> <DIR>       1024 mnt
> <DIR>       1024 tmp
> <SYM>          3 lib32
> <DIR>       1024 usr
> <DIR>       1024 proc
> <DIR>       1024 dev
> <DIR>       1024 boot
> <DIR>       1024 sys
> <DIR>       3072 sbin
> <DIR>       3072 bin
> <SYM>         11 linuxrc
> <DIR>       1024 etc
> <DIR>       1024 opt
> <DIR>       3072 lib
> 
> => ls host 0:2 /boot
> <DIR>       1024 .
> <DIR>       1024 ..
>            26909 imx6ul-opos6uldev.dtb
> <SYM>          1 dtbs
>          5359984 opos6ul-linux.bin
> 
> => host load hostfs - 0 /tftproot/opos6ul-linux.bin
> 5359984 bytes read in 2 ms (2.5 GiB/s)
> 
> => printenv filesize
> filesize=51c970
> 
> => ext4write host 0:2 0 /boot/opos6ul-linux.bin ${filesize}
> File System is consistent
> file found, deleting
> update journal finished
> File System is consistent
> update journal finished
> Segmentation fault

As you can repeat this under sandbox, the next step would be to run sandbox 
under gdb, e.g.:
$> gdb --args sandbox -c "host bind 0 /tftproot/rootfs.raw ; host load hostfs 
- 0 /tftproot/opos6ul-linux.bin ; ext4write host 0:2 0 /boot/opos6ul-linux.bin 
${filesize}"

Kind regards,

Stefan