From: Goldwyn Rodrigues <rgoldwyn@suse.de>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH] Use bigger nodestr to accomodate 32-bit node numbers
Date: Tue, 27 Aug 2013 23:15:52 -0500 [thread overview]
Message-ID: <20130828041547.GA4404@shrek.cartoons> (raw)
While using pacemaker/corosync, the node numbers are generated using
IP address as opposed to serial node number generation. This may
not fit in a 8-byte string. Use a bigger string to print the
complete node number.
Signed-off-by: Goldwyn Rodrigues <rgoldwyn@suse.com>
---
diff --git a/fs/ocfs2/super.c b/fs/ocfs2/super.c
index 854d809..bc947e0 100644
--- a/fs/ocfs2/super.c
+++ b/fs/ocfs2/super.c
@@ -1022,7 +1022,7 @@ static int ocfs2_fill_super(struct super_block *sb, void *data, int silent)
struct inode *inode = NULL;
struct ocfs2_super *osb = NULL;
struct buffer_head *bh = NULL;
- char nodestr[8];
+ char nodestr[12];
struct ocfs2_blockcheck_stats stats;
trace_ocfs2_fill_super(sb, data, silent);
--
Goldwyn
next reply other threads:[~2013-08-28 4:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-28 4:15 Goldwyn Rodrigues [this message]
2013-08-29 9:52 ` [Ocfs2-devel] [PATCH] Use bigger nodestr to accomodate 32-bit node numbers Jeff Liu
2013-08-29 12:15 ` Goldwyn Rodrigues
2013-08-29 19:26 ` Andrew Morton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130828041547.GA4404@shrek.cartoons \
--to=rgoldwyn@suse.de \
--cc=ocfs2-devel@oss.oracle.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).