linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Nicolas Escande" <nico.escande@gmail.com>
To: "Vasanthakumar Thiagarajan" <quic_vthiagar@quicinc.com>,
	<ath11k@lists.infradead.org>,
	"Sven Eckelmann" <se@simonwunderlich.de>
Cc: <linux-wireless@vger.kernel.org>,
	"Steffen Moser" <lists@steffen-moser.de>
Subject: Re: [PATCH] Revert "ath11k: clear the keys properly via DISABLE_KEY"
Date: Sun, 04 May 2025 14:36:48 +0200	[thread overview]
Message-ID: <D9NDQJB4VMWA.V4IPOZOIR46W@gmail.com> (raw)
In-Reply-To: <20e0a239-3d23-473b-5bc8-41bc25a64088@quicinc.com>

On Sat Jan 18, 2025 at 11:29 AM CET, Vasanthakumar Thiagarajan wrote:
> Hi Nicolas,
>
> On 1/18/2025 12:44 AM, Nicolas Escande wrote:
>> This reverts commit 436a4e88659842a7cf634d7cc088c8f2cc94ebf5.
>> 
>> This as been reported by multiple people [0] that with this commit,
>> broadcast packets were not being delivered after GTK exchange.
>> Qualcomm seems to have a similar patch [1] confirming the issue.
>> 
>
> This will re-open https://www.spinics.net/lists/hostap/msg08921.html
> reported by Sven. The recommended ath firmware ABI during GTK re-keying
> is SET_KEY instead of current DEL_KEY followed by SET_KEY. We are looking
> at other options like some marking by mac80211 for the driver to be able
> to identify if the received DEL_KEY is for re-keying. Also I'm curious
> if roaming between secure and non-secure mode is a critical use case.
> If not, we can probably go ahead with this revert as temporary WAR,
> @Sven?
>
> Vasanth

Hello,

Any news on this ?
I would hate for this to sink into oblivion once again given how hard this
affects end users when it does hit.

Thanks,

  parent reply	other threads:[~2025-05-04 12:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-17 19:14 [PATCH] Revert "ath11k: clear the keys properly via DISABLE_KEY" Nicolas Escande
2025-01-18 10:29 ` Vasanthakumar Thiagarajan
2025-01-20 15:30   ` Nicolas Escande
2025-05-04 12:36   ` Nicolas Escande [this message]
2025-05-06  9:19     ` Vasanthakumar Thiagarajan
2025-06-27  7:31       ` Nicolas Escande
2025-06-30  4:12         ` Vasanthakumar Thiagarajan
2025-08-11 23:34 ` Jeff Johnson
2025-08-12 12:44   ` Nicolas Escande

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=D9NDQJB4VMWA.V4IPOZOIR46W@gmail.com \
    --to=nico.escande@gmail.com \
    --cc=ath11k@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lists@steffen-moser.de \
    --cc=quic_vthiagar@quicinc.com \
    --cc=se@simonwunderlich.de \
    /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;
as well as URLs for NNTP newsgroup(s).