From: Ben Greear <greearb@candelatech.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH-WN 1/3] wireless: Make sure __cfg80211_connect_result always puts bss.
Date: Mon, 24 Jun 2013 07:46:16 -0700 [thread overview]
Message-ID: <51C85BB8.30000@candelatech.com> (raw)
In-Reply-To: <1372082182.8439.5.camel@jlt4.sipsolutions.net>
On 06/24/2013 06:56 AM, Johannes Berg wrote:
> On Wed, 2013-06-19 at 14:06 -0700, greearb@candelatech.com wrote:
>> From: Ben Greear <greearb@candelatech.com>
>>
>> Otherwise, we can leak a bss reference.
>
> Applied all 3, still trying to make up my mind about the debugfs one
> patch :)
With regard to that one, how about I allow it to be enabled based on
cfg80211 module option (and only when cfg80211 debugfs is enabled).
That way, no new kernel option, and no significant hit to any runtime
performance unless users specifically enable the feature.
Thanks for applying the other three.
Thanks,
Ben
>
> johannes
>
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
prev parent reply other threads:[~2013-06-24 14:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-19 21:06 [PATCH-WN 1/3] wireless: Make sure __cfg80211_connect_result always puts bss greearb
2013-06-19 21:06 ` [PATCH-WN 2/3] wireless: Check for dangling wdev->current_bss pointer greearb
2013-06-19 21:06 ` [PATCH-WN 3/3] wireless: Add comments about bss refcounting greearb
2013-06-24 13:56 ` [PATCH-WN 1/3] wireless: Make sure __cfg80211_connect_result always puts bss Johannes Berg
2013-06-24 14:46 ` Ben Greear [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=51C85BB8.30000@candelatech.com \
--to=greearb@candelatech.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@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).