diff options
author | Robert Yang <liezhi.yang@windriver.com> | 2013-08-22 15:47:23 +0800 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2013-08-26 11:47:19 +0100 |
commit | 1b214059be350a3abfc57140cbad00f5bab437bf (patch) | |
tree | db6ed9da603aa7ce515e353595e78e04a8722190 /meta/classes/metadata_scm.bbclass | |
parent | 2cece576b351228cb24bf24a53845646a51f7f6b (diff) | |
download | poky-1b214059be350a3abfc57140cbad00f5bab437bf.tar.gz |
e2fsprogs: properly set up extent header in do_write
do_write doesn't fully set up the first extent header on a new
inode, so if we write a 0-length file, and don't write any data
to the new file, we end up creating something that looks corrupt
to kernelspace:
EXT4-fs error (device loop0): ext4_ext_check_inode:464: inode #12: comm
ls: bad header/extent: invalid magic - magic 0, entries 0, max 0(0),
depth 0(0)
Do something similar to ext4_ext_tree_init() here, and
fill out the first extent header upon creation to avoid this.
[YOCTO #3848]
(From OE-Core rev: 7d1e51681d25f6e6d2c20744825723ad5c83861c)
Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/classes/metadata_scm.bbclass')
0 files changed, 0 insertions, 0 deletions