From: David Miller <davem@davemloft.net>
To: colin.king@canonical.com
Cc: kuznet@ms2.inr.ac.ru, jmorris@namei.org, yoshfuji@linux-ipv6.org,
kaber@trash.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] calipso: fix resource leak on calipso_genopt failure
Date: Sat, 13 Aug 2016 14:56:41 -0700 (PDT) [thread overview]
Message-ID: <20160813.145641.1944190186523562997.davem@davemloft.net> (raw)
In-Reply-To: <1470935842-13884-1-git-send-email-colin.king@canonical.com>
From: Colin King <colin.king@canonical.com>
Date: Thu, 11 Aug 2016 18:17:22 +0100
> From: Colin Ian King <colin.king@canonical.com>
>
> Currently, if calipso_genopt fails then the error exit path
> does not free the ipv6_opt_hdr new causing a memory leak. Fix
> this by kfree'ing new on the error exit path.
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
Applied, thanks.
prev parent reply other threads:[~2016-08-13 21:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-11 17:17 [PATCH] calipso: fix resource leak on calipso_genopt failure Colin King
2016-08-13 21:56 ` 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=20160813.145641.1944190186523562997.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=colin.king@canonical.com \
--cc=jmorris@namei.org \
--cc=kaber@trash.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.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).