From: Kalle Valo <kvalo@codeaurora.org>
To: Arend van Spriel <arend.vanspriel@broadcom.com>
Cc: linux-wireless@vger.kernel.org,
Arend van Spriel <arend.vanspriel@broadcom.com>
Subject: Re: [PATCH 1/6] brcmfmac: assure SSID length from firmware is limited
Date: Tue, 19 Feb 2019 15:05:53 +0000 (UTC) [thread overview]
Message-ID: <20190219150553.D97256071A@smtp.codeaurora.org> (raw)
In-Reply-To: <1550148232-4309-2-git-send-email-arend.vanspriel@broadcom.com>
Arend van Spriel <arend.vanspriel@broadcom.com> wrote:
> The SSID length as received from firmware should not exceed
> IEEE80211_MAX_SSID_LEN as that would result in heap overflow.
>
> Reviewed-by: Hante Meuleman <hante.meuleman@broadcom.com>
> Reviewed-by: Pieter-Paul Giesberts <pieter-paul.giesberts@broadcom.com>
> Reviewed-by: Franky Lin <franky.lin@broadcom.com>
> Signed-off-by: Arend van Spriel <arend.vanspriel@broadcom.com>
6 patches applied to wireless-drivers-next.git, thanks.
1b5e2423164b brcmfmac: assure SSID length from firmware is limited
a4176ec356c7 brcmfmac: add subtype check for event handling in data path
aaf6a5e86e36 brcmfmac: create debugfs files for bus-specific layer
92d3b88b1029 brcmfmac: disable MBSS feature for bcm4330 device
4ab2cf03da91 brcmfmac: check and dump trap info during sdio probe
a250c91c1762 brcmfmac: use chipname in brcmf_fw_alloc_request() for error path as well
--
https://patchwork.kernel.org/patch/10812617/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2019-02-19 15:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-14 12:43 [PATCH 0/6] brcmfmac: smallish series Arend van Spriel
2019-02-14 12:43 ` [PATCH 1/6] brcmfmac: assure SSID length from firmware is limited Arend van Spriel
2019-02-19 15:05 ` Kalle Valo [this message]
2019-02-14 12:43 ` [PATCH 2/6] brcmfmac: add subtype check for event handling in data path Arend van Spriel
2019-02-14 12:43 ` [PATCH 3/6] brcmfmac: create debugfs files for bus-specific layer Arend van Spriel
2019-02-14 12:43 ` [PATCH 4/6] brcmfmac: disable MBSS feature for bcm4330 device Arend van Spriel
2019-02-14 12:43 ` [PATCH 5/6] brcmfmac: check and dump trap info during sdio probe Arend van Spriel
2019-02-14 12:43 ` [PATCH 6/6] brcmfmac: use chipname in brcmf_fw_alloc_request() for error path as well Arend van Spriel
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=20190219150553.D97256071A@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=arend.vanspriel@broadcom.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).