Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit b8607152 authored by Arend van Spriel's avatar Arend van Spriel Committed by Johannes Berg
Browse files

cfg80211: stop critical protocol session upon disconnect event 



When user-space has started a critical protocol session and a disconnect
event occurs, the rdev::crit_prot_nlportid remains set. This caused a
subsequent NL80211_CMD_CRIT_PROTO_START to fail (-EBUSY). Fix this by
clearing the rdev attribute and call .crit_proto_stop() callback upon
disconnect event.

Reviewed-by: default avatarHante Meuleman <meuleman@broadcom.com>
Reviewed-by: default avatarPieter-Paul Giesberts <pieterpg@broadcom.com>
Signed-off-by: default avatarArend van Spriel <arend@broadcom.com>
Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
parent 5e950a78

net/wireless/sme.c

+6 −0
Original line number Diff line number Diff line
@@ -917,6 +917,12 @@ void __cfg80211_disconnected(struct net_device *dev, const u8 *ie, 


	nl80211_send_disconnected(rdev, dev, reason, ie, ie_len, from_ap);



	/* stop critical protocol if supported */

	if (rdev->ops->crit_proto_stop && rdev->crit_proto_nlportid) {

		rdev->crit_proto_nlportid = 0;

		rdev_crit_proto_stop(rdev, wdev);

	}



	/*

	 * Delete all the keys ... pairwise keys can't really

	 * exist any more anyway, but default keys might.