[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <1469850669-64815-1-git-send-email-zhongjiang@huawei.com>
Date: Sat, 30 Jul 2016 11:51:09 +0800
From: zhongjiang <zhongjiang@...wei.com>
To: <akpm@...ux-foundation.org>
CC: <linux-mm@...ck.org>, <linux-kernel@...r.kernel.org>
Subject: [PATCH] fs: fix a bug when new_insert_key is not initialization
From: zhong jiang <zhongjiang@...wei.com>
when compile the kenrel code, I happens to the following warn.
fs/reiserfs/ibalance.c:1156:2: warning: ‘new_insert_key’ may be used
uninitialized in this function.
memcpy(new_insert_key_addr, &new_insert_key, KEY_SIZE);
The patch fix it by check the new_insert_ptr. if new_insert_ptr is not
NULL, we ensure that new_insert_key is assigned. therefore, memcpy will
saftly exec the operatetion.
Signed-off-by: zhong jiang <zhongjiang@...wei.com>
---
fs/reiserfs/ibalance.c | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/fs/reiserfs/ibalance.c b/fs/reiserfs/ibalance.c
index b751eea..2c46829 100644
--- a/fs/reiserfs/ibalance.c
+++ b/fs/reiserfs/ibalance.c
@@ -1153,8 +1153,10 @@ int balance_internal(struct tree_balance *tb,
insert_ptr);
}
- memcpy(new_insert_key_addr, &new_insert_key, KEY_SIZE);
- insert_ptr[0] = new_insert_ptr;
+ if (new_insert_ptr) {
+ memcpy(new_insert_key_addr, &new_insert_key, KEY_SIZE);
+ insert_ptr[0] = new_insert_ptr;
+ }
return order;
}
--
1.8.3.1
Powered by blists - more mailing lists