From: "Lukáš Turek" <8an@praha12.net>
To: Bruno Randolf <br1@einfach.org>
Cc: "Luis R. Rodriguez" <lrodriguez@atheros.com>,
"ath5k-devel@lists.ath5k.org" <ath5k-devel@lists.ath5k.org>,
"linux-wireless" <linux-wireless@vger.kernel.org>
Subject: Re: [ath5k-devel] Race condition in CRDA calls?
Date: Mon, 11 Oct 2010 20:13:03 +0200 [thread overview]
Message-ID: <201010112013.09521.8an@praha12.net> (raw)
In-Reply-To: <201010081657.17326.br1@einfach.org>
[-- Attachment #1: Type: Text/Plain, Size: 889 bytes --]
On Friday 08 October 2010 09:57:17 you wrote:
> root@RMR1:~# 1284335259.046129: phy #1: regulatory domain change:
> intersection used due to a request made by a driver on phy1
> 1284335263.403515: phy #1: regulatory domain change: intersection used due
> to a request made by a driver on phy1
>
> interesting that phy #1 appears twice...
When I hit this bug my idea was that the problem lies in the CRDA API: the
wiphy identifier is not sent to CRDA, instead a global variable last_request
is used. However, if a new request is started before the previous one is
finished, the old last_request value is replaced, both replies use the same
last_request and strange think happen...
I hoped someone who knows the kernel-userspace interaction better will confirm
or disprove it, so I didn't investigate it further, and then I just forgot
about it...
Lukas Turek
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2010-10-11 18:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201003251801.57951.8an@praha12.net>
2010-05-26 21:46 ` [ath5k-devel] Race condition in CRDA calls? Luis R. Rodriguez
2010-06-17 4:47 ` Bruno Randolf
2010-06-17 5:05 ` Luis R. Rodriguez
2010-10-08 7:57 ` Bruno Randolf
2010-10-11 18:13 ` Lukáš Turek [this message]
2010-10-11 18:50 ` Luis R. Rodriguez
2010-06-17 10:04 ` Lukáš Turek
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=201010112013.09521.8an@praha12.net \
--to=8an@praha12.net \
--cc=ath5k-devel@lists.ath5k.org \
--cc=br1@einfach.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lrodriguez@atheros.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.