From: Johannes Berg <johannes@sipsolutions.net>
To: amit.khatri@samsung.com
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Rahul Jain <rahul.jain@samsung.com>,
HEMANSHU SRIVASTAVA <hemanshu.s@samsung.com>,
Nitin Jhanwar <nitin.j@samsung.com>
Subject: Re: [PATCH 2/4] iw: Avoid possible memory leak for cb. cb got memory from nl_cb_alloc() but not doing free
Date: Thu, 13 Aug 2015 10:52:56 +0200 [thread overview]
Message-ID: <1439455976.2114.1.camel@sipsolutions.net> (raw)
In-Reply-To: <2034214352.309341435309836730.JavaMail.weblogic@ep2mlwas06c>
On Fri, 2015-06-26 at 09:10 +0000, Amit Khatri wrote:
> Hi Johannes,
>
> Subject: [PATCH 2/4] iw: Avoid possible memory leak for cb. cb got
> memory from
> nl_cb_alloc() but not doing free
Please fix your submission process to not mangle patches. I've applied
patch 1 in this series and fixed it up manually, but having the subject
again inside the email just makes it harder for me to pick up the
patches.
> Signed-off-by: Amit Khatri <amit.khatri@samsung.com>
> Signed-off-by: Rahul Jain <rahul.jain@samsung.com>
> ---
> iw.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/iw.c b/iw.c
> index dc99566..1e913b6 100644
> --- a/iw.c
> +++ b/iw.c
> @@ -477,8 +477,8 @@ static int __handle_cmd(struct nl80211_state
> *state, enum id_input idby,
> while (err > 0)
> nl_recvmsgs(state->nl_sock, cb);
> out:
> - nl_cb_put(cb);
> out_free_msg:
> + nl_cb_put(cb);
>
Please don't leave two equivalent labels, remove one of them and
replace the users.
johannes
prev parent reply other threads:[~2015-08-13 8:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-26 9:10 [PATCH 2/4] iw: Avoid possible memory leak for cb. cb got memory from nl_cb_alloc() but not doing free Amit Khatri
2015-08-13 8:52 ` Johannes Berg [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=1439455976.2114.1.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=amit.khatri@samsung.com \
--cc=hemanshu.s@samsung.com \
--cc=linux-wireless@vger.kernel.org \
--cc=nitin.j@samsung.com \
--cc=rahul.jain@samsung.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;
as well as URLs for NNTP newsgroup(s).