From: "John W. Linville" <linville@tuxdriver.com>
To: Sven Neumann <s.neumann@raumfeld.com>
Cc: libertas-dev@lists.infradead.org, linux-wireless@vger.kernel.org,
Johannes Berg <johannes@sipsolutions.net>,
Daniel Mack <daniel@zonque.org>,
mcgrof@gmail.com
Subject: Re: [PATCH] cfg80211: really ignore the regulatory request
Date: Fri, 15 Jul 2011 13:33:06 -0400 [thread overview]
Message-ID: <20110715173306.GE2566@tuxdriver.com> (raw)
In-Reply-To: <1310478727-12099-2-git-send-email-s.neumann@raumfeld.com>
Luis, ping?
On Tue, Jul 12, 2011 at 03:52:07PM +0200, Sven Neumann wrote:
> At the beginning of wiphy_update_regulatory() a check is performed
> whether the request is to be ignored. Then the request is sent to
> the driver nevertheless. This happens even if last_request points
> to NULL, leading to a crash in the driver:
>
> [<bf01d864>] (lbs_set_11d_domain_info+0x28/0x1e4 [libertas]) from [<c03b714c>] (wiphy_update_regulatory+0x4d0/0x4f4)
> [<c03b714c>] (wiphy_update_regulatory+0x4d0/0x4f4) from [<c03b4008>] (wiphy_register+0x354/0x420)
> [<c03b4008>] (wiphy_register+0x354/0x420) from [<bf01b17c>] (lbs_cfg_register+0x80/0x164 [libertas])
> [<bf01b17c>] (lbs_cfg_register+0x80/0x164 [libertas]) from [<bf020e64>] (lbs_start_card+0x20/0x88 [libertas])
> [<bf020e64>] (lbs_start_card+0x20/0x88 [libertas]) from [<bf02cbd8>] (if_sdio_probe+0x898/0x9c0 [libertas_sdio])
>
> Fix this by returning early. Also remove the out: label as it is
> not any longer needed.
>
> Signed-off-by: Sven Neumann <s.neumann@raumfeld.com>
> Cc: linux-wireless@vger.kernel.org
> Cc: Johannes Berg <johannes@sipsolutions.net>
> Cc: Daniel Mack <daniel@zonque.org>
> ---
> net/wireless/reg.c | 5 +++--
> 1 files changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/net/wireless/reg.c b/net/wireless/reg.c
> index 1ad0f39..4453eb7 100644
> --- a/net/wireless/reg.c
> +++ b/net/wireless/reg.c
> @@ -1125,12 +1125,13 @@ void wiphy_update_regulatory(struct wiphy *wiphy,
> enum ieee80211_band band;
>
> if (ignore_reg_update(wiphy, initiator))
> - goto out;
> + return;
> +
> for (band = 0; band < IEEE80211_NUM_BANDS; band++) {
> if (wiphy->bands[band])
> handle_band(wiphy, band, initiator);
> }
> -out:
> +
> reg_process_beacons(wiphy);
> reg_process_ht_flags(wiphy);
> if (wiphy->reg_notifier)
> --
> 1.7.1
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
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:[~2011-07-15 17:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-11 15:59 kernel NULL pointer dereference in lbs_set_11d_domain_info (3.0-rc6) Sven Neumann
2011-07-11 21:04 ` Pavel Roskin
2011-07-12 7:22 ` Sven Neumann
2011-07-12 15:20 ` Pavel Roskin
2011-07-12 16:54 ` Sven Neumann
2011-07-12 19:36 ` Pavel Roskin
2011-07-12 13:52 ` [PATCH] cfg80211: really ignore the regulatory request Sven Neumann
2011-07-15 17:33 ` John W. Linville [this message]
2011-07-22 20:40 ` Sven Neumann
2011-07-25 20:27 ` 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=20110715173306.GE2566@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=daniel@zonque.org \
--cc=johannes@sipsolutions.net \
--cc=libertas-dev@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.com \
--cc=s.neumann@raumfeld.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.