linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Will Hawkins <hawkinsw@opentechinstitute.org>
Cc: linux-wireless@vger.kernel.org, linville@tuxdriver.com,
	Antonio Quartulli <ordex@autistici.org>
Subject: Re: [PATCH 0/2 v3] mac80211/cfg80211: add support for userspace to handle auth frames on adhoc ifaces
Date: Tue, 19 Jun 2012 09:05:58 +0200	[thread overview]
Message-ID: <1340089558.4482.5.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <4FDFC5AE.1080004@opentechinstitute.org>

Hi Will,

> I am sending along 2 patches to add support for user space applications
> to register for authentication frames on adhoc interfaces. These are
> revisions to a previous patch that I submitted to accomplish the same
> thing.

Thanks.

> Patch 1/2 adds a cfg80211_mgmt_reg_match function to cfg80211 to
> check whether a user space application is registered for a particular
> type of management frame rx'd on a particular device. The new function
> is very similar to cfg80211_rx_mgmt. cfg80211_rx_mgmt could not be
> reused because of its side-effect of transmitting the "query" frames to
> the registered userspace applications. This patch modifies the
> documentation for cfg80211_rx_mgmt to reflect that.

I think this isn't needed: if you look at mac80211/cfg.c, there's a
handler called ieee80211_mgmt_frame_register() where cfg80211 tells
mac80211 when a handler is registered/unregistered. mac80211 could just
keep track (for IBSS type interfaces) all by itself, and then just needs
to check some flag/variable instead of calling a function.

> Patch 2/2 sets the necessary flags to allow userspace
> applications to register for authentication frames on adhoc interfaces.
> It also adds a check to make sure that "open" authentication frames are
> not sent when a user space application is registered for authentication
> frames.

Makes sense. I'll need to check if you caught all conditions, maybe
Antonio can help out.

> As I've said before, I'm still new to this process so I look forward to
> your feedback on improving.

There's not a lot of room for improvement :-)

A small detail: the first patch should have been labelled only
"cfg80211" and the second only "mac80211".

Also, if you could send the patches (1/2 and 2/2) as a reply to the
cover letter (0/2) that helps keep the series together due to threading.
With git send-email you can instruct it to do that, but it didn't look
like you used it.

Thanks!

johannes


      reply	other threads:[~2012-06-19  7:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-19  0:19 [PATCH 0/2 v3] mac80211/cfg80211: add support for userspace to handle auth frames on adhoc ifaces Will Hawkins
2012-06-19  7:05 ` 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=1340089558.4482.5.camel@jlt3.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=hawkinsw@opentechinstitute.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=ordex@autistici.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).