From: Sunil Mushran <sunil.mushran@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: Re: [patch] ocfs2: cleanup error handling in o2hb_alloc_hb_set()
Date: Mon, 13 Feb 2012 19:39:27 +0000 [thread overview]
Message-ID: <4F3966EF.9070405@oracle.com> (raw)
In-Reply-To: <20120213135047.GA10683@elgon.mountain>
hmm... I would say NAK because config_group_item_type_name() could
change in the future. And there is nothing wrong with the current
code.
On 02/13/2012 05:50 AM, Dan Carpenter wrote:
> If "ret" is NULL, then "hs" is also NULL, so there is no need to free
> it. config_group_init_type_name() can't fail if the name ("heartbeat"
> in this case) is less than CONFIGFS_ITEM_NAME_LEN (20) characters long
> so we can just remove this error handling code.
>
> Signed-off-by: Dan Carpenter<dan.carpenter@oracle.com>
>
> diff --git a/fs/ocfs2/cluster/heartbeat.c b/fs/ocfs2/cluster/heartbeat.c
> index f3f2d95..0bca51b 100644
> --- a/fs/ocfs2/cluster/heartbeat.c
> +++ b/fs/ocfs2/cluster/heartbeat.c
> @@ -2306,20 +2306,14 @@ static struct config_item_type o2hb_heartbeat_group_type = {
> struct config_group *o2hb_alloc_hb_set(void)
> {
> struct o2hb_heartbeat_group *hs = NULL;
> - struct config_group *ret = NULL;
>
> hs = kzalloc(sizeof(struct o2hb_heartbeat_group), GFP_KERNEL);
> if (hs = NULL)
> - goto out;
> + return NULL;
>
> config_group_init_type_name(&hs->hs_group, "heartbeat",
> &o2hb_heartbeat_group_type);
> -
> - ret =&hs->hs_group;
> -out:
> - if (ret = NULL)
> - kfree(hs);
> - return ret;
> + return&hs->hs_group;
> }
>
> void o2hb_free_hb_set(struct config_group *group)
WARNING: multiple messages have this Message-ID (diff)
From: Sunil Mushran <sunil.mushran@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [patch] ocfs2: cleanup error handling in o2hb_alloc_hb_set()
Date: Mon, 13 Feb 2012 11:39:27 -0800 [thread overview]
Message-ID: <4F3966EF.9070405@oracle.com> (raw)
In-Reply-To: <20120213135047.GA10683@elgon.mountain>
hmm... I would say NAK because config_group_item_type_name() could
change in the future. And there is nothing wrong with the current
code.
On 02/13/2012 05:50 AM, Dan Carpenter wrote:
> If "ret" is NULL, then "hs" is also NULL, so there is no need to free
> it. config_group_init_type_name() can't fail if the name ("heartbeat"
> in this case) is less than CONFIGFS_ITEM_NAME_LEN (20) characters long
> so we can just remove this error handling code.
>
> Signed-off-by: Dan Carpenter<dan.carpenter@oracle.com>
>
> diff --git a/fs/ocfs2/cluster/heartbeat.c b/fs/ocfs2/cluster/heartbeat.c
> index f3f2d95..0bca51b 100644
> --- a/fs/ocfs2/cluster/heartbeat.c
> +++ b/fs/ocfs2/cluster/heartbeat.c
> @@ -2306,20 +2306,14 @@ static struct config_item_type o2hb_heartbeat_group_type = {
> struct config_group *o2hb_alloc_hb_set(void)
> {
> struct o2hb_heartbeat_group *hs = NULL;
> - struct config_group *ret = NULL;
>
> hs = kzalloc(sizeof(struct o2hb_heartbeat_group), GFP_KERNEL);
> if (hs == NULL)
> - goto out;
> + return NULL;
>
> config_group_init_type_name(&hs->hs_group, "heartbeat",
> &o2hb_heartbeat_group_type);
> -
> - ret =&hs->hs_group;
> -out:
> - if (ret == NULL)
> - kfree(hs);
> - return ret;
> + return&hs->hs_group;
> }
>
> void o2hb_free_hb_set(struct config_group *group)
next prev parent reply other threads:[~2012-02-13 19:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-13 13:50 [patch] ocfs2: cleanup error handling in o2hb_alloc_hb_set() Dan Carpenter
2012-02-13 13:50 ` [Ocfs2-devel] " Dan Carpenter
2012-02-13 19:39 ` Sunil Mushran [this message]
2012-02-13 19:39 ` Sunil Mushran
2012-02-13 20:06 ` Dan Carpenter
2012-02-13 20:08 ` Dan Carpenter
2012-02-13 20:17 ` Sunil Mushran
2012-02-13 20:17 ` [Ocfs2-devel] " Sunil Mushran
2012-04-17 21:13 ` [Ocfs2-devel] Ocfs2 + Quota! Marek Królikowski
2012-02-13 20:04 ` [patch] ocfs2: cleanup error handling in o2hb_alloc_hb_set() Joel Becker
2012-02-13 20:04 ` [Ocfs2-devel] " Joel Becker
2012-02-13 20:27 ` Dan Carpenter
2012-02-13 20:29 ` Dan Carpenter
2012-02-13 20:41 ` Sunil Mushran
2012-02-13 20:41 ` [Ocfs2-devel] " Sunil Mushran
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=4F3966EF.9070405@oracle.com \
--to=sunil.mushran@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 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.