[PATCH v3 41/46] PR: Flush PMKSA cache after TK is configured for ranging

[Kavita Kavita]

In the ranging use case, PASN is performed solely to derive and
install the encryption keys (TK) into the driver. Once set_keys()
has been called, the PMK and any cached PMKSA entry serve no further
purpose. Flush the PMKSA cache after get_ranging_params() is invoked
on both the initiator and responder to ensure the PMKID is not
included in M1 on any subsequent PASN attempt.

Signed-off-by: Kavita Kavita <kavita.kavita at oss.qualcomm.com>
---
 src/common/proximity_ranging.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/src/common/proximity_ranging.c b/src/common/proximity_ranging.c
index 5b5f3bf8a..d728e0030 100644
--- a/src/common/proximity_ranging.c
+++ b/src/common/proximity_ranging.c
@@ -2048,6 +2048,7 @@ int pr_pasn_auth_tx_status(struct pr_data *pr, const u8 *data, size_t data_len,
 					    dev->final_op_channel,
 					    self_format_bw,
 					    peer_format_bw);
+		pr_flush(pr);
 	}
 
 out:
@@ -2516,6 +2517,7 @@ static int pr_pasn_handle_auth_3(struct pr_data *pr, struct pr_device *dev,
 					    dev->final_op_channel,
 					    self_format_bw,
 					    peer_format_bw);
+	pr_flush(pr);
 	return 0;
 
 fail:
-- 
2.34.1