* [Ocfs2-devel] [PATCH] ocfs2: cleanup error handling in ocfs2_super_lock
@ 2012-12-22 8:38 Xue jiufei
0 siblings, 0 replies; only message in thread
From: Xue jiufei @ 2012-12-22 8:38 UTC (permalink / raw)
To: ocfs2-devel
There is no need to determine whether ocfs2_should_refresh_lock_res()
returns less than 0 because it never returns such a value.
Signed-off-by: xuejiufei <xuejiufei@huawei.com>
---
fs/ocfs2/dlmglue.c | 4 ----
1 files changed, 0 insertions(+), 4 deletions(-)
diff --git a/fs/ocfs2/dlmglue.c b/fs/ocfs2/dlmglue.c
index 4f7795f..e35ee3e 100644
--- a/fs/ocfs2/dlmglue.c
+++ b/fs/ocfs2/dlmglue.c
@@ -2544,10 +2544,6 @@ int ocfs2_super_lock(struct ocfs2_super *osb,
* refreshed, so we do it here. Of course, making sense of
* everything is up to the caller :) */
status = ocfs2_should_refresh_lock_res(lockres);
- if (status < 0) {
- mlog_errno(status);
- goto bail;
- }
if (status) {
status = ocfs2_refresh_slot_info(osb);
--
1.7.8.6
^ permalink raw reply related [flat|nested] only message in thread
only message in thread, other threads:[~2012-12-22 8:38 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-12-22 8:38 [Ocfs2-devel] [PATCH] ocfs2: cleanup error handling in ocfs2_super_lock Xue jiufei
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.