From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: Bogdan Nicolae <bogdan.nicolae@gmail.com>
Cc: linux-wireless@vger.kernel.org, brcm80211@lists.linux.dev,
brcm80211-dev-list.pdl@broadcom.com,
linux-kernel@vger.kernel.org,
Bogdan Nicolae <bogdan.nicolae@acm.org>
Subject: Re: [PATCH] wifi: brcmfmac: cyw: clean up PMKID and cookie code
Date: Mon, 13 Jul 2026 00:30:42 +0200 [thread overview]
Message-ID: <99c2c345-c594-46e1-b48a-de7f6e52e1c6@broadcom.com> (raw)
In-Reply-To: <20260709122315.11400-1-bogdan.nicolae@gmail.com>
On 09/07/2026 14:23, Bogdan Nicolae wrote:
> Avoid setting packet_id to cookie, which is always 0. Instead, use an
> increasing atomic counter. Avoids mismatches of completion events later
> in brcmf_notify_mgmt_tx_status, where packet_id != vif->mgmt_tx_id is
> checked.
>
> Also, zero out auth_status on initialization. Otherwise, garbage will
> leak from the stack to the firmware (when bssid is less than 32 bytes
> and/or when params->pmkid is set). Then, pass the params->pmkid to the
> firmware (without it, the firmware caches a garbage PMKID on successful
> authentication and denies a subsequent association request that includes
> the PMKID).
>
> Signed-off-by: Bogdan Nicolae <bogdan.nicolae@acm.org>
I always get a bit confused when people use different email addresses to
send and sign-off patches.
> ---
> .../net/wireless/broadcom/brcm80211/brcmfmac/cyw/core.c | 8 ++++++--
> 1 file changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/cyw/core.c b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/cyw/core.c
> index ce09d44fa..cca53ff19 100644
> --- a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/cyw/core.c
> +++ b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/cyw/core.c
> @@ -23,6 +23,8 @@
> #define MGMT_AUTH_FRAME_DWELL_TIME 4000
> #define MGMT_AUTH_FRAME_WAIT_TIME (MGMT_AUTH_FRAME_DWELL_TIME + 100)
>
> +static atomic_t brcmf_cyw_mgmt_tx_id = ATOMIC_INIT(0);
> +
> static int brcmf_cyw_set_sae_pwd(struct brcmf_if *ifp,
> struct cfg80211_crypto_settings *crypto)
> {
> @@ -155,7 +157,7 @@ int brcmf_cyw_mgmt_tx(struct wiphy *wiphy, struct wireless_dev *wdev,
>
> memcpy(&mf_params->da[0], &mgmt->da[0], ETH_ALEN);
> memcpy(&mf_params->bssid[0], &mgmt->bssid[0], ETH_ALEN);
> - mf_params->packet_id = cpu_to_le32(*cookie);
> + mf_params->packet_id = cpu_to_le32(atomic_inc_return(&brcmf_cyw_mgmt_tx_id));
As I understand things the cookie value here is an output parameter. The
driver should assign it:
+ *cookie = atomic_inc_return(&brcmf_cyw_mgmt_tx_id);
mf_params->packet_id = cpu_to_le32(*cookie);
> memcpy(mf_params->data, &buf[DOT11_MGMT_HDR_LEN],
> le16_to_cpu(mf_params->len));
>
Regards,
Arend
next prev parent reply other threads:[~2026-07-12 22:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-09 12:23 Bogdan Nicolae
2026-07-12 22:30 ` Arend van Spriel [this message]
2026-07-14 6:56 ` Bogdan Nicolae
2026-07-14 13:03 ` Gokul Sivakumar
2026-07-14 15:13 ` Bogdan Nicolae
-- strict thread matches above, loose matches on Subject: below --
2026-07-14 15:04 bogdan.nicolae
2026-07-20 19:48 ` Arend van Spriel
2026-07-20 21:30 ` Bogdan Nicolae
2026-07-21 10:33 ` Arend van Spriel
2026-07-09 12:16 Bogdan Nicolae
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=99c2c345-c594-46e1-b48a-de7f6e52e1c6@broadcom.com \
--to=arend.vanspriel@broadcom.com \
--cc=bogdan.nicolae@acm.org \
--cc=bogdan.nicolae@gmail.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=brcm80211@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®