From: Johannes Berg <johannes@sipsolutions.net>
To: Ola Olsson <ola1olsson@gmail.com>
Cc: linux-wireless@vger.kernel.org, Ola Olsson <ola.olsson@sonymobile.com>
Subject: Re: [PATCH] nl80211: Potential memory leaks in reg.c
Date: Tue, 15 Dec 2015 13:09:45 +0100 [thread overview]
Message-ID: <1450181385.3356.6.camel@sipsolutions.net> (raw)
In-Reply-To: <1450030323-6637-1-git-send-email-ola1olsson@gmail.com> (sfid-20151213_191210_429467_A915DC81)
On Sun, 2015-12-13 at 19:12 +0100, Ola Olsson wrote:
> The first leak occurs when entering the default case
> in the switch for the initiator in set_regdom.
> The second leaks a platform_device struct if the
> platform registration in regulatory_init succeeds but
> the sub sequent regulatory hint fails due to no memory.
Applied, thanks. How are you finding these?? They seems so obscure :)
johannes
next prev parent reply other threads:[~2015-12-15 12:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-13 18:12 [PATCH] nl80211: Potential memory leaks in reg.c Ola Olsson
2015-12-15 12:09 ` Johannes Berg [this message]
2015-12-15 12:19 ` Ola Olsson
2015-12-15 12:33 ` Johannes Berg
2015-12-16 9:14 ` Ola Olsson
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=1450181385.3356.6.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=ola.olsson@sonymobile.com \
--cc=ola1olsson@gmail.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).