netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Ingo Oeser <netdev@axxeo.de>
Cc: "John W. Linville" <linville@tuxdriver.com>,
	davem@davemloft.net, linux-wireless@vger.kernel.org,
	netdev@vger.kernel.org
Subject: [PATCH wireless-dev, net-2.6.22] cfg80211: fix locking in wiphy_new
Date: Thu, 26 Apr 2007 15:14:22 +0200	[thread overview]
Message-ID: <1177593262.6814.75.camel@johannes.berg> (raw)
In-Reply-To: <200704251806.46270.netdev@axxeo.de>

This patch fixes the locking in wiphy new. Ingo Oeser <netdev@axxeo.de>
noticed that locking in the error case was wrong and also suggested this
fix.

Signed-off-by: Johannes Berg <johannes@sipsolutions.net>

---
As with other patches, this is diffed against wireless-dev but applies
against net-2.6.22 (or is that net-2.6 now?) with some offset (but no
fuzz.)

---
 net/wireless/core.c |   16 ++++++++++------
 1 file changed, 10 insertions(+), 6 deletions(-)

--- wireless-dev.orig/net/wireless/core.c	2007-04-26 15:01:15.623251869 +0200
+++ wireless-dev/net/wireless/core.c	2007-04-26 15:07:27.933251869 +0200
@@ -189,21 +189,25 @@ struct wiphy *wiphy_new(struct cfg80211_
 
 	mutex_lock(&cfg80211_drv_mutex);
 
-	if (unlikely(wiphy_counter<0)) {
+	drv->idx = wiphy_counter;
+
+	/* now increase counter for the next device unless
+	 * it has wrapped previously */
+	if (wiphy_counter >= 0)
+		wiphy_counter++;
+
+	mutex_unlock(&cfg80211_drv_mutex);
+
+	if (unlikely(drv->idx < 0)) {
 		/* ugh, wrapped! */
 		kfree(drv);
 		return NULL;
 	}
-	drv->idx = wiphy_counter;
 
 	/* give it a proper name */
 	snprintf(drv->wiphy.dev.bus_id, BUS_ID_SIZE,
 		 PHY_NAME "%d", drv->idx);
 
-	/* now increase counter for the next time */
-	wiphy_counter++;
-	mutex_unlock(&cfg80211_drv_mutex);
-
 	mutex_init(&drv->mtx);
 	mutex_init(&drv->devlist_mtx);
 	INIT_LIST_HEAD(&drv->netdev_list);



  reply	other threads:[~2007-04-26 17:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-23 18:33 [PATCH] update MAINTAINERS for wireless mailing list John W. Linville
     [not found] ` <20070423183334.GC5883-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2007-04-23 18:34   ` [PATCH] refactor wireless Kconfig John W. Linville
     [not found]     ` <20070423183443.GD5883-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2007-04-23 18:36       ` [PATCH] cfg80211: new wireless config infrastructure John W. Linville
     [not found]         ` <20070423183634.GE5883-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2007-04-23 18:37           ` [PATCH] remove wext over netlink John W. Linville
2007-04-24  9:22         ` [PATCH] cfg80211: update comment for locking Johannes Berg
2007-04-25 16:06         ` [PATCH] cfg80211: new wireless config infrastructure Ingo Oeser
2007-04-26 13:14           ` Johannes Berg [this message]
2007-04-23 19:35       ` [PATCH] refactor wireless Kconfig Stefano Brivio
2007-04-23 19:53         ` [PATCH] drivers/net/wireless/Kconfig: correct minor typo John W. Linville
     [not found]           ` <20070423195313.GG5883-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2007-04-23 20:29             ` David Miller

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=1177593262.6814.75.camel@johannes.berg \
    --to=johannes@sipsolutions.net \
    --cc=davem@davemloft.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=netdev@axxeo.de \
    --cc=netdev@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).