From: David Miller <davem@davemloft.net>
To: geyslan@gmail.com
Cc: arvid.brodin@xdin.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net/hsr: Fix possible leak in 'hsr_get_node_status()'
Date: Thu, 14 Nov 2013 17:26:37 -0500 (EST) [thread overview]
Message-ID: <20131114.172637.288809112911669556.davem@davemloft.net> (raw)
In-Reply-To: <1384456378-29970-1-git-send-email-geyslan@gmail.com>
From: "Geyslan G. Bem" <geyslan@gmail.com>
Date: Thu, 14 Nov 2013 16:12:54 -0300
> If 'hsr_get_node_data()' returns error, going directly to 'fail' label
> doesn't free the memory pointed by 'skb_out'.
>
> Signed-off-by: Geyslan G. Bem <geyslan@gmail.com>
Looks good, applied, thanks!
prev parent reply other threads:[~2013-11-14 22:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-14 19:12 [PATCH] net/hsr: Fix possible leak in 'hsr_get_node_status()' Geyslan G. Bem
2013-11-14 20:29 ` Geyslan Gregório Bem
2013-11-14 22:26 ` David Miller [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=20131114.172637.288809112911669556.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=arvid.brodin@xdin.com \
--cc=geyslan@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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).