From: Jeff Liu <jeff.liu@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH Resend] ocfs2: add the missing return value check of ocfs2_get_clusters
Date: Tue, 06 Aug 2013 13:44:55 +0800 [thread overview]
Message-ID: <52008D57.7050100@oracle.com> (raw)
In-Reply-To: <51FA2BA3.2090009@huawei.com>
On 08/01/2013 05:34 PM, Joseph Qi wrote:
> In ocfs2_attach_refcount_tree() and ocfs2_duplicate_extent_list(), if
> error occurs when calling ocfs2_get_clusters(), it will go with
> unexpected behavior as local variables p_cluster, num_clusters and
> ext_flags are declared without initialization.
>
> Signed-off-by: Joseph Qi <joseph.qi@huawei.com>
Looks good, thanks.
Reviewed-by: Jie Liu <jeff.liu@oracle.com>
> ---
> fs/ocfs2/refcounttree.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/fs/ocfs2/refcounttree.c b/fs/ocfs2/refcounttree.c
> index 998b17e..3589ec1 100644
> --- a/fs/ocfs2/refcounttree.c
> +++ b/fs/ocfs2/refcounttree.c
> @@ -3886,6 +3886,10 @@ static int ocfs2_attach_refcount_tree(struct inode *inode,
> while (cpos < clusters) {
> ret = ocfs2_get_clusters(inode, cpos, &p_cluster,
> &num_clusters, &ext_flags);
> + if (ret) {
> + mlog_errno(ret);
> + goto unlock;
> + }
>
> if (p_cluster && !(ext_flags & OCFS2_EXT_REFCOUNTED)) {
> ret = ocfs2_add_refcount_flag(inode, &di_et,
> @@ -4057,6 +4061,10 @@ static int ocfs2_duplicate_extent_list(struct inode *s_inode,
> while (cpos < clusters) {
> ret = ocfs2_get_clusters(s_inode, cpos, &p_cluster,
> &num_clusters, &ext_flags);
> + if (ret) {
> + mlog_errno(ret);
> + goto out;
> + }
>
> if (p_cluster) {
> ret = ocfs2_add_refcounted_extent(t_inode, &et,
prev parent reply other threads:[~2013-08-06 5:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-01 9:34 [Ocfs2-devel] [PATCH Resend] ocfs2: add the missing return value check of ocfs2_get_clusters Joseph Qi
2013-08-06 5:44 ` Jeff Liu [this message]
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=52008D57.7050100@oracle.com \
--to=jeff.liu@oracle.com \
--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