The Linux Kernel Mailing List
 help / color / mirror / Atom feed
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
Subject: Re: [PATCH] wifi: brcmfmac: configure SAE PWE method for external SAE AP
Date: Wed, 29 Jul 2026 11:48:22 +0200	[thread overview]
Message-ID: <5cf57b2d-2bcc-481c-87bf-3a034d5f99be@broadcom.com> (raw)
In-Reply-To: <20260729053408.13715-1-bogdan.nicolae@gmail.com>

On 29/07/2026 07:34, Bogdan Nicolae wrote:
> When bringing up a WPA3-SAE SoftAP with external (user space) SAE, the
> driver never told the firmware which SAE Password Element (PWE) method to
> accept. The firmware was observed to corrupt its heap over time due to
> this omission, leading to firmware trap (data abort in heap allocator).
> 
> Parse the beacon IEs on start_ap() and set the extsae_pwe iovar
> accordingly: 2 when the RSNX IE advertises H2E, 1 when an H2E-only
> membership selector is present, 0 otherwise. This matches the behaviour
> of the upstream/vendor driver and only applies to SAE-capable APs when
> external SAE is supported.

This makes sense, but may I ask what device do you have? Suspect it is a 
Cypress/Infineon chip. I could not find the iovar in our (Broadcom bca) 
code base so I suspect it is vendor specific.

Regards,
Arend

  reply	other threads:[~2026-07-29  9:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-29  5:34 [PATCH] wifi: brcmfmac: configure SAE PWE method for external SAE AP Bogdan Nicolae
2026-07-29  9:48 ` Arend van Spriel [this message]
2026-07-29 12:07   ` Gokul Sivakumar
     [not found]   ` <CA+ORkNQntwC4k2arcngGdYB3mwsbJCkCRNTJRJ2GoRxjdGXLzA@mail.gmail.com>
2026-07-29 12:28     ` Arend van Spriel
     [not found]       ` <CA+ORkNSsb8Z5eUVH1GRvWtO_he6A+_b67ov2Cm6VJuWciJeKZQ@mail.gmail.com>
2026-07-30  4:29         ` Bogdan Nicolae
2026-07-31 13:50           ` Gokul Sivakumar
2026-07-31 18:02             ` Bogdan Nicolae
2026-08-02  8:39 ` Arend van Spriel
2026-08-07 23:56   ` Bogdan Nicolae
2026-08-08  5:20     ` Arend van Spriel
2026-08-09  4:18       ` Bogdan Nicolae
2026-08-10  5:26         ` Gokul Sivakumar

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=5cf57b2d-2bcc-481c-87bf-3a034d5f99be@broadcom.com \
    --to=arend.vanspriel@broadcom.com \
    --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