From: Coly Li <coly.li@suse.de>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH] indexed-dirs: fix brelse order in ocfs2_find_entry_dx(), v2
Date: Thu, 22 Oct 2009 13:56:22 +0800 [thread overview]
Message-ID: <4ADFF406.5010700@suse.de> (raw)
In ocfs2_find_entry_dx(), if ocfs2_read_inode_block() failed, both di_bh and dx_root_bh are both released. In this case,
for dx_root_bh, it's unnecessary (even buggy if refcount of dx_root_bh is non-zero).
This patch fixes this issue by change brelse order of di_bh and dx_root_bh.
Signed-off-by: Coly Li <coly.li@suse.de>
---
fs/ocfs2/dir.c | 14 ++++++++------
1 files changed, 8 insertions(+), 6 deletions(-)
diff --git a/fs/ocfs2/dir.c b/fs/ocfs2/dir.c
index 28c3ec2..502a3e9 100644
--- a/fs/ocfs2/dir.c
+++ b/fs/ocfs2/dir.c
@@ -1048,7 +1048,7 @@ static int ocfs2_find_entry_dx(const char *name, int namelen,
ret = ocfs2_read_inode_block(dir, &di_bh);
if (ret) {
mlog_errno(ret);
- goto out;
+ goto brelse_di;
}
di = (struct ocfs2_dinode *)di_bh->b_data;
@@ -1056,7 +1056,7 @@ static int ocfs2_find_entry_dx(const char *name, int namelen,
ret = ocfs2_read_dx_root(dir, di, &dx_root_bh);
if (ret) {
mlog_errno(ret);
- goto out;
+ goto brelse_dx_root;
}
dx_root = (struct ocfs2_dx_root_block *) dx_root_bh->b_data;
@@ -1064,14 +1064,16 @@ static int ocfs2_find_entry_dx(const char *name, int namelen,
if (ret) {
if (ret != -ENOENT)
mlog_errno(ret);
- goto out;
+ goto brelse_dx_root;
}
lookup->dl_dx_root_bh = dx_root_bh;
- dx_root_bh = NULL;
-out:
- brelse(di_bh);
+ goto brelse_di;
+
+brelse_dx_root:
brelse(dx_root_bh);
+brelse_di:
+ brelse(di_bh);
return ret;
}
--
Coly Li
SuSE Labs
next reply other threads:[~2009-10-22 5:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-22 5:56 Coly Li [this message]
2009-10-22 6:07 ` [Ocfs2-devel] [PATCH] indexed-dirs: fix brelse order in ocfs2_find_entry_dx(), v2 Coly Li
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=4ADFF406.5010700@suse.de \
--to=coly.li@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 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.