From: Michael Buesch <mb@bu3sch.de>
To: Jiri Benc <jbenc@suse.cz>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 3/4] mac80211: document requirement for atomicity of callbacks
Date: Sun, 29 Apr 2007 14:53:47 +0200 [thread overview]
Message-ID: <200704291453.47601.mb@bu3sch.de> (raw)
In-Reply-To: <20070429124929.417ef7da@logostar.upir.cz>
On Sunday 29 April 2007 12:49:29 Jiri Benc wrote:
> On Sun, 29 Apr 2007 11:15:43 +0200, Michael Buesch wrote:
> > On Sunday 29 April 2007 02:33:45 Jiri Benc wrote:
> > > + * Must be atomic. */
> > > int (*set_key)(struct ieee80211_hw *hw, set_key_cmd cmd,
> > > u8 *addr, struct ieee80211_key_conf *key, int aid);
> >
> > I think USB drivers and bcm43xx violate that. We can't easily workaround it
> > without doing the operation async.
>
> I know. Unfortunately, it's not easy to fix that in mac80211. I really want
> this call not to be atomic and will try to change it later, but it's not a
> priority now.
>
> For now, just always return success and complain to dmesg if something goes
> wrong during setting of the key in a workqueue.
Ok, I see. But I want to note that this might be more problematic
then just a lost error code. It might race.
For example it might race with the EAPOL KEY authentication stuff.
So I think we must also workaround that by disabling TX queues
until the key configuration request has actually happened
on the device.
--
Greetings Michael.
next prev parent reply other threads:[~2007-04-29 12:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-29 0:32 [PATCH 1/4] mac80211: remove unused code Jiri Benc
2007-04-29 0:33 ` [PATCH 2/4] mac80211: remove test_mode Jiri Benc
2007-04-29 0:33 ` [PATCH 3/4] mac80211: document requirement for atomicity of callbacks Jiri Benc
2007-04-29 9:15 ` Michael Buesch
2007-04-29 9:20 ` Ivo van Doorn
2007-04-29 10:49 ` Jiri Benc
2007-04-29 12:53 ` Michael Buesch [this message]
2007-04-29 0:34 ` [PATCH] mac80211: add copyrights Jiri Benc
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=200704291453.47601.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=jbenc@suse.cz \
--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).