From: "Pedersen, Thomas" <c_tpeder@qca.qualcomm.com>
To: Kalle Valo <kvalo@qca.qualcomm.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
<ath6kl-devel@qualcomm.com>, <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] ath6kl: protect firmware from excessive WoW pattern length
Date: Mon, 20 Aug 2012 11:18:38 -0700 [thread overview]
Message-ID: <20120820181837.GA4695@pista> (raw)
In-Reply-To: <5031E74F.4010104@qca.qualcomm.com>
On Mon, Aug 20, 2012 at 10:29:19AM +0300, Kalle Valo wrote:
> On 08/20/2012 10:13 AM, Johannes Berg wrote:
> > On Wed, 2012-08-15 at 17:15 -0700, Thomas Pedersen wrote:
> >> Don't accept WoW patterns longer than supported by firmware.
> >>
> >> Reported-by: Haijun Jin <nhjin@qca.qualcomm.com>
> >> Signed-off-by: Thomas Pedersen <c_tpeder@qca.qualcomm.com>
> >> ---
> >> drivers/net/wireless/ath/ath6kl/cfg80211.c | 3 +++
> >> 1 files changed, 3 insertions(+), 0 deletions(-)
> >>
> >> diff --git a/drivers/net/wireless/ath/ath6kl/cfg80211.c b/drivers/net/wireless/ath/ath6kl/cfg80211.c
> >> index bd003fe..ffa18f3 100644
> >> --- a/drivers/net/wireless/ath/ath6kl/cfg80211.c
> >> +++ b/drivers/net/wireless/ath/ath6kl/cfg80211.c
> >> @@ -1876,6 +1876,9 @@ static int ath6kl_wow_usr(struct ath6kl *ar, struct ath6kl_vif *vif,
> >> /* Configure the patterns that we received from the user. */
> >> for (i = 0; i < wow->n_patterns; i++) {
> >>
> >> + if (wow->patterns[i].pattern_len > WOW_MASK_SIZE)
> >> + return -EINVAL;
> >> +
> >
> > No objection, but doesn't nl80211 already validate that (assuming you
> > give the right pattern_max_len, of course)?
Thanks for pointing that out. That check would be completely redundant
then.
Kalle,
Can you revert this patch? Otherwise the followup will just do the same.
> And ath6kl even uses different define pattern_max_len:
>
> wiphy->wowlan.pattern_max_len = WOW_PATTERN_SIZE;
>
> But the value is still same:
>
> #define WOW_PATTERN_SIZE 64
> #define WOW_MASK_SIZE 64
>
> Thomas, can you please check this? Do we really need two different
> defines? And which one is the correct one here?
No AFAICT there is no reason to have two different defines. I can submit
a small patch consolidating these, but it would remove the above hunk
anyway so I need to know whether you'll revert or not.
Thanks,
Thomas
next prev parent reply other threads:[~2012-08-20 18:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-16 0:15 [PATCH] ath6kl: protect firmware from excessive WoW pattern length Thomas Pedersen
2012-08-20 7:09 ` Kalle Valo
2012-08-20 7:13 ` Johannes Berg
2012-08-20 7:29 ` Kalle Valo
2012-08-20 18:18 ` Pedersen, Thomas [this message]
2012-08-20 19:08 ` Kalle Valo
2012-08-20 20:33 ` Pedersen, Thomas
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=20120820181837.GA4695@pista \
--to=c_tpeder@qca.qualcomm.com \
--cc=ath6kl-devel@qualcomm.com \
--cc=johannes@sipsolutions.net \
--cc=kvalo@qca.qualcomm.com \
--cc=linux-wireless@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).