From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Luis Rodriguez <Luis.Rodriguez@Atheros.com>,
"linville@tuxdriver.com" <linville@tuxdriver.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v2 2/3] cfg80211: mark regdomains with > NL80211_MAX_SUPP_REG_RULES invalid
Date: Fri, 7 Nov 2008 13:12:00 -0800 [thread overview]
Message-ID: <20081107211200.GB5912@tesla> (raw)
In-Reply-To: <1226091963.11203.12.camel@johannes.berg>
On Fri, Nov 07, 2008 at 01:06:02PM -0800, Johannes Berg wrote:
> On Thu, 2008-11-06 at 12:45 -0800, Luis R. Rodriguez wrote:
> > Lets remain consistent and mark rds with > NL80211_MAX_SUPP_REG_RULES
> > number of reg rules as invalid in is_valid_rd().
> >
> > Signed-off-by: Luis R. Rodriguez <lrodriguez@atheros.com>
>
> Seems fine, if that's not userspace triggerable, but it isn't, right?
Nope, nl80211 has a check of its own, hence the addition of the
WARN_ON().
> Acked-by: Johannes Berg <johannes@sipsolutions.net>
Thanks,
Luis
next prev parent reply other threads:[~2008-11-07 21:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-06 20:45 [PATCH v2 0/3] cfg80211/mac80211: Add 802.11d support Luis R. Rodriguez
2008-11-06 20:45 ` [PATCH v2 1/3] cfg80211: call_crda() won't tell us if CRDA was present Luis R. Rodriguez
2008-11-06 20:45 ` [PATCH v2 2/3] cfg80211: mark regdomains with > NL80211_MAX_SUPP_REG_RULES invalid Luis R. Rodriguez
2008-11-06 20:45 ` [PATCH 3/3] cfg80211/mac80211: Add 802.11d support Luis R. Rodriguez
2008-11-06 20:56 ` Luis R. Rodriguez
2008-11-07 21:06 ` [PATCH v2 2/3] cfg80211: mark regdomains with > NL80211_MAX_SUPP_REG_RULES invalid Johannes Berg
2008-11-07 21:12 ` Luis R. Rodriguez [this message]
2008-11-07 21:05 ` [PATCH v2 1/3] cfg80211: call_crda() won't tell us if CRDA was present Johannes Berg
2008-11-07 21:02 ` [PATCH v2 0/3] cfg80211/mac80211: Add 802.11d support Johannes Berg
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=20081107211200.GB5912@tesla \
--to=lrodriguez@atheros.com \
--cc=Luis.Rodriguez@Atheros.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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 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).