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:42:11 +0100 |
| commit | 7d1e51681d25f6e6d2c20744825723ad5c83861c (patch) | |
| tree | 93036f85a8e2be4300cd35722db5c25c55b8b7b8 /meta/recipes-devtools/e2fsprogs/e2fsprogs-1.42.8/debugfs-too-short.patch | |
| parent | ad8452196c5b1a54c14fd00bbf421f68aea65186 (diff) | |
| download | openembedded-core-7d1e51681d25f6e6d2c20744825723ad5c83861c.tar.gz openembedded-core-7d1e51681d25f6e6d2c20744825723ad5c83861c.tar.bz2 openembedded-core-7d1e51681d25f6e6d2c20744825723ad5c83861c.zip | |
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]
Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Diffstat (limited to 'meta/recipes-devtools/e2fsprogs/e2fsprogs-1.42.8/debugfs-too-short.patch')
0 files changed, 0 insertions, 0 deletions