From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nathan Straz Date: Tue, 11 Dec 2012 17:01:24 -0500 Subject: [Cluster-devel] [PATCH] GFS2: Initialize hex string to '0' Message-ID: <20121211220124.GR1396@redhat.com> List-Id: To: cluster-devel.redhat.com MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit When generating the DLM lock name, a value of 0 would skip the loop and leave the string unchanged. This left locks with a value of 0 unlabeled. Initializing the string to '0' fixes this. --- fs/gfs2/lock_dlm.c | 1 + 1 file changed, 1 insertion(+) diff --git a/fs/gfs2/lock_dlm.c b/fs/gfs2/lock_dlm.c index 0fb6539..a924b6a 100644 --- a/fs/gfs2/lock_dlm.c +++ b/fs/gfs2/lock_dlm.c @@ -239,6 +239,7 @@ static u32 make_flags(struct gfs2_glock *gl, const unsigned int gfs_flags, static void gfs2_reverse_hex(char *c, u64 value) { + *c = '0'; while (value) { *c-- = hex_asc[value & 0x0f]; value >>= 4; -- 1.7.11.7