From: Steven Whitehouse <swhiteho@redhat.com>
To: Jonghwan Choi <jhbird.choi@samsung.com>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
"'Wei Yongjun'" <yongjun_wei@trendmicro.com.cn>
Subject: Re: [PATCH 3.8-stable] GFS2: return error if malloc failed in gfs2_rs_alloc()
Date: Thu, 11 Apr 2013 08:59:57 +0100 [thread overview]
Message-ID: <1365667197.2701.13.camel@menhir> (raw)
In-Reply-To: <000501ce3658$b3022fd0$19068f70$%choi@samsung.com>
Hi,
On Thu, 2013-04-11 at 11:03 +0900, Jonghwan Choi wrote:
> This patch looks like it should be in the 3.8-stable tree, should we apply
> it?
>
Yes, again looks like a good plan,
Steve.
> ------------------
>
> From: "Wei Yongjun <yongjun_wei@trendmicro.com.cn>"
>
> commit 441362d06be349430d06e37286adce4b90e6ce96 upstream
>
> The error code in gfs2_rs_alloc() is set to ENOMEM when error
> but never be used, instead, gfs2_rs_alloc() always return 0.
> Fix to return 'error'.
>
> Signed-off-by: Wei Yongjun <yongjun_wei@trendmicro.com.cn>
> Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>
> Signed-off-by: Jonghwan Choi <jhbird.choi@samsung.com>
> ---
> fs/gfs2/rgrp.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/gfs2/rgrp.c b/fs/gfs2/rgrp.c
> index b7eff07..9afba3d6 100644
> --- a/fs/gfs2/rgrp.c
> +++ b/fs/gfs2/rgrp.c
> @@ -576,7 +576,7 @@ int gfs2_rs_alloc(struct gfs2_inode *ip)
> RB_CLEAR_NODE(&ip->i_res->rs_node);
> out:
> up_write(&ip->i_rw_mutex);
> - return 0;
> + return error;
> }
>
> static void dump_rs(struct seq_file *seq, const struct gfs2_blkreserv *rs)
prev parent reply other threads:[~2013-04-11 7:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-11 2:03 [PATCH 3.8-stable] GFS2: return error if malloc failed in gfs2_rs_alloc() Jonghwan Choi
2013-04-11 7:59 ` Steven Whitehouse [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=1365667197.2701.13.camel@menhir \
--to=swhiteho@redhat.com \
--cc=jhbird.choi@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=yongjun_wei@trendmicro.com.cn \
/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