mirror of
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
synced 2024-08-21 08:19:28 +00:00
ext4: Fix coding style in fs/ext4/move_extent.c
Making sure ee_block is initialized to zero to prevent gcc from kvetching. It's harmless (although it's not obvious that it's harmless) from code inspection: fs/ext4/move_extent.c:478: warning: 'start_ext.ee_block' may be used uninitialized in this function Thanks to Stefan Richter for first bringing this to the attention of linux-ext4@vger.kernel.org. Signed-off-by: LiuQi <lingjiujianke@gmail.com> Signed-off-by: "Theodore Ts'o" <tytso@mit.edu> Cc: Stefan Richter <stefanr@s5r6.in-berlin.de>
This commit is contained in:
parent
0671e70465
commit
c26d0bad3d
1 changed files with 1 additions and 0 deletions
|
@ -482,6 +482,7 @@ mext_leaf_block(handle_t *handle, struct inode *orig_inode,
|
|||
int depth = ext_depth(orig_inode);
|
||||
int ret;
|
||||
|
||||
start_ext.ee_block = end_ext.ee_block = 0;
|
||||
o_start = o_end = oext = orig_path[depth].p_ext;
|
||||
oext_alen = ext4_ext_get_actual_len(oext);
|
||||
start_ext.ee_len = end_ext.ee_len = 0;
|
||||
|
|
Loading…
Reference in a new issue