From: "John W. Linville" <linville@tuxdriver.com>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: johannes@sipsolutions.net, linux-wireless@vger.kernel.org,
stable@kernel.org
Subject: Re: [PATCH 3/4] cfg80211: fix in nl80211_set_reg()
Date: Mon, 18 May 2009 14:46:41 -0400 [thread overview]
Message-ID: <20090518184641.GI2814@tuxdriver.com> (raw)
In-Reply-To: <1242248682-22051-4-git-send-email-lrodriguez@atheros.com>
On Wed, May 13, 2009 at 05:04:41PM -0400, Luis R. Rodriguez wrote:
> There is a race on access to last_request and its alpha2
> through reg_is_valid_request() and us possibly processing
> first another regulatory request on another CPU. We avoid
> this improbably race by locking with the cfg80211_mutex as
> we should have done in the first place. While at it add
> the assert on locking on reg_is_valid_request().
>
> Cc: stable@kernel.org
> Signed-off-by: Luis R. Rodriguez <lrodriguez@atheros.com>
What is the effect of this race? What justifies this for 2.6.30
and/or stable? It is getting late in the cycle for 2.6.30...
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2009-05-18 19:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-13 21:04 [PATCH 0/4] cfg80211: two reg fixes Luis R. Rodriguez
2009-05-13 21:04 ` [PATCH 1/4] cfg80211: return immediately if num reg rules > NL80211_MAX_SUPP_REG_RULES Luis R. Rodriguez
2009-05-13 21:04 ` [PATCH 2/4] cfg80211: cleanup return calls on nl80211_set_reg() Luis R. Rodriguez
2009-05-13 21:04 ` [PATCH 3/4] cfg80211: fix in nl80211_set_reg() Luis R. Rodriguez
2009-05-18 18:46 ` John W. Linville [this message]
2009-05-18 20:02 ` Luis R. Rodriguez
2009-05-13 21:04 ` [PATCH 4/4] cfg80211: fix race between core hint and driver's custom apply Luis R. Rodriguez
2009-05-13 22:08 ` Johannes Berg
2009-05-13 22:29 ` Luis R. Rodriguez
2009-05-13 22:35 ` Johannes Berg
2009-05-13 22:37 ` Luis R. Rodriguez
2009-05-14 18:05 ` Luis R. Rodriguez
2009-05-18 18:47 ` John W. Linville
2009-05-18 20:04 ` Luis R. Rodriguez
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=20090518184641.GI2814@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=lrodriguez@atheros.com \
--cc=stable@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 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.