summaryrefslogtreecommitdiff
path: root/fs/ocfs2/stackglue.c
diff options
context:
space:
mode:
authorMark Fasheh <mfasheh@suse.com>2008-01-30 03:59:56 +0300
committerMark Fasheh <mfasheh@suse.com>2008-04-18 19:56:04 +0400
commit0abd6d1803b01c741430af270026d1d95a103d9c (patch)
treec1aca3d286990be6f9043e28ad0bacaf3443ef54 /fs/ocfs2/stackglue.c
parent6953b4c008628b945bfe0cee97f6e78a98773859 (diff)
downloadlinux-0abd6d1803b01c741430af270026d1d95a103d9c.tar.xz
ocfs2: Fill node number during cluster stack init
It doesn't make sense to query for a node number before connecting to the cluster stack. This should be safe to do because node_num is only just printed, and we're actually only moving the setting of node num a small amount further in the mount process. [ Disconnect when node query fails -- Joel ] Reviewed-by: Joel Becker <joel.becker@oracle.com> Signed-off-by: Mark Fasheh <mfasheh@suse.com>
Diffstat (limited to 'fs/ocfs2/stackglue.c')
0 files changed, 0 insertions, 0 deletions