From: James Prestwood <prestwoj@gmail.com>
To: iwd@lists.linux.dev
Cc: KeithG <ys3al35l@gmail.com>
Subject: Re: [PATCH] netdev: destroy auth-proto after external auth
Date: Thu, 19 Dec 2024 10:18:43 -0800 [thread overview]
Message-ID: <ee05cb0c-d317-4bd8-8736-6ffaba6d7b62@gmail.com> (raw)
In-Reply-To: <20241219181701.164349-1-prestwoj@gmail.com>
Hi Keith,
On 12/19/24 10:17 AM, James Prestwood wrote:
> With external auth there is no associate event meaning the auth proto
> never gets freed, which prevents eapol from starting inside the
> OCI callback. Check for this specific case and free the auth proto
> after signaling that external auth has completed.
> ---
> src/netdev.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/src/netdev.c b/src/netdev.c
> index 02496c92..2a6d94fc 100644
> --- a/src/netdev.c
> +++ b/src/netdev.c
> @@ -3483,6 +3483,13 @@ static void netdev_external_auth_sae_tx_associate(void *user_data)
>
> netdev_send_external_auth(netdev, MMPDU_STATUS_CODE_SUCCESS);
> netdev_ensure_eapol_registered(netdev);
> +
> + /*
> + * Free the auth proto now. With external auth there is no associate
> + * event which is where this normally gets cleaned up.
> + */
> + auth_proto_free(netdev->ap);
> + netdev->ap = NULL;
> }
>
> struct rtnl_data {
Could you give this version of the patch a try to verify it still works
on brcmfmac? This is just a bit simpler and more straight forward.
Thanks,
James
next prev parent reply other threads:[~2024-12-19 18:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-19 18:17 [PATCH] netdev: destroy auth-proto after external auth James Prestwood
2024-12-19 18:18 ` James Prestwood [this message]
2024-12-20 3:57 ` KeithG
2024-12-20 4:58 ` KeithG
2024-12-20 5:57 ` Denis Kenzior
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=ee05cb0c-d317-4bd8-8736-6ffaba6d7b62@gmail.com \
--to=prestwoj@gmail.com \
--cc=iwd@lists.linux.dev \
--cc=ys3al35l@gmail.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