public inbox for iwd@lists.linux.dev
 help / color / mirror / Atom feed
From: James Prestwood <prestwoj@gmail.com>
To: iwd@lists.linux.dev
Cc: James Prestwood <prestwoj@gmail.com>
Subject: [PATCH v3 11/13] station: use netdev_ft_reassociate
Date: Wed,  6 Dec 2023 12:18:00 -0800	[thread overview]
Message-ID: <20231206201802.2139649-11-prestwoj@gmail.com> (raw)
In-Reply-To: <20231206201802.2139649-1-prestwoj@gmail.com>

Using this will provide netdev with a connect callback and unify the
roaming result notification between FT and reassociation. Both paths
will now end up in station_reassociate_cb.

This also adds another return case for ft_handshake_setup which was
previously ignored by ft_associate. Its likely impossible to actually
happen but should be handled nevertheless.

Fixes: 30c6a10f28 ("netdev: Separate connect_failed and disconnected paths")
---
 src/station.c | 22 ++++++++++++++++++++--
 1 file changed, 20 insertions(+), 2 deletions(-)

diff --git a/src/station.c b/src/station.c
index 48a595dc..52d87c84 100644
--- a/src/station.c
+++ b/src/station.c
@@ -2181,7 +2181,8 @@ static void station_reassociate_cb(struct netdev *netdev,
 
 	l_debug("%u, result: %d", netdev_get_ifindex(station->netdev), result);
 
-	if (station->state != STATION_STATE_ROAMING)
+	if (station->state != STATION_STATE_ROAMING &&
+			station->state != STATION_STATE_FT_ROAMING)
 		return;
 
 	if (result == NETDEV_RESULT_OK)
@@ -2314,7 +2315,8 @@ static bool station_ft_work_ready(struct wiphy_radio_work_item *item)
 	if (!bss)
 		goto try_next;
 
-	ret = ft_associate(netdev_get_ifindex(station->netdev), bss->addr);
+	ret = ft_handshake_setup(netdev_get_ifindex(station->netdev),
+					bss->addr);
 	switch (ret) {
 	case MMPDU_STATUS_CODE_INVALID_PMKID:
 		/*
@@ -2343,12 +2345,28 @@ try_next:
 		station_transition_start(station);
 		break;
 	case 0:
+		ret = netdev_ft_reassociate(station->netdev, bss,
+					station->connected_bss,
+					station_netdev_event,
+					station_reassociate_cb, station);
+		if (ret < 0)
+			goto disassociate;
+
 		station->connected_bss = bss;
 		station->preparing_roam = false;
 		station_enter_state(station, STATION_STATE_FT_ROAMING);
 
 		station_debug_event(station, "ft-roam");
 
+		break;
+	case -EINVAL:
+		/*
+		 * Likely an impossible situation, but since ft_handshake_setup
+		 * rederived the handshake keys we can't do anything but
+		 * disconnect.
+		 */
+disassociate:
+		station_disassociated(station);
 		break;
 	default:
 		if (ret > 0)
-- 
2.34.1


  parent reply	other threads:[~2023-12-06 20:18 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-06 20:17 [PATCH v3 01/13] auto-t: add explicit stop() to IWD class James Prestwood
2023-12-06 20:17 ` [PATCH v3 02/13] auto-t: add association timeout test James Prestwood
2023-12-06 20:17 ` [PATCH v3 03/13] auto-t: only call set_value for changed values in default() James Prestwood
2023-12-06 20:17 ` [PATCH v3 04/13] handshake: add setters for authenticator/supplicant_fte James Prestwood
2023-12-06 20:17 ` [PATCH v3 05/13] handshake: use authenticator_fte instead of 'fte' James Prestwood
2023-12-06 20:17 ` [PATCH v3 06/13] unit: use authenticator_fte James Prestwood
2023-12-06 20:17 ` [PATCH v3 07/13] handshake: remove handshake_state_set_fte James Prestwood
2023-12-06 20:17 ` [PATCH v3 08/13] ft: add FTE/RSNE building to ft_prepare_handshake James Prestwood
2023-12-06 20:17 ` [PATCH v3 09/13] ft: add ft_handshake_setup James Prestwood
2023-12-06 20:17 ` [PATCH v3 10/13] netdev: add netdev_ft_reassociate James Prestwood
2023-12-06 20:18 ` James Prestwood [this message]
2023-12-06 20:18 ` [PATCH v3 12/13] ft: remove ft_associate and helpers James Prestwood
2023-12-06 20:18 ` [PATCH v3 13/13] netdev: station: remove NETDEV_EVENT_FT_ROAMED James Prestwood
2023-12-13 16:14 ` [PATCH v3 01/13] auto-t: add explicit stop() to IWD class 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=20231206201802.2139649-11-prestwoj@gmail.com \
    --to=prestwoj@gmail.com \
    --cc=iwd@lists.linux.dev \
    /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