All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Nicolas Escande" <nico.escande@gmail.com>
To: "Jeff Johnson" <jeff.johnson@oss.qualcomm.com>,
	<ath11k@lists.infradead.org>
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: Tue, 12 Aug 2025 14:44:19 +0200	[thread overview]
Message-ID: <DC0GIRF0TYEL.DUG78V7F6HID@gmail.com> (raw)
In-Reply-To: <5b769b75-df2a-4dba-a41b-198851b61b9c@oss.qualcomm.com>

On Tue Aug 12, 2025 at 1:34 AM CEST, Jeff Johnson wrote:
> On 1/17/2025 11:14 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.
>> 
>> [0] https://lore.kernel.org/linux-wireless/Z2Q9POuV-6MIdzRf@pilgrim/
>> [1] https://git.codelinaro.org/clo/qsdk/oss/system/feeds/wlan-open/-/blob/win.wlan_host_opensource.3.0.r24/patches/ath11k/350-ath11k-Revert-clear-the-keys-properly-when-DISABLE_K.patch
>> 
>> Fixes: 436a4e886598 ("ath11k: clear the keys properly via DISABLE_KEY")
>> Reported-by: Steffen Moser <lists@steffen-moser.de>
>> Closes: https://lore.kernel.org/linux-wireless/c6366409-9928-4dd7-bf7b-ba7fcf20eabf@steffen-moser.de
>> Signed-off-by: Nicolas Escande <nico.escande@gmail.com>
>> ---
>
> Can you please check if this alternative addresses the issue:
> [PATCH ath-current v4] wifi: ath11k: fix group data packet drops during rekey
> https://msgid.link/20250810170018.1124014-1-rameshkumar.sundaram@oss.qualcomm.com
>
> Any Tested-on/Tested-by tags would be appreciated!
>
> /jeff
Yes that was on my todo.
It seems to work fine with this patch.
Thanks for taking the time to fix this one


      reply	other threads:[~2025-08-12 16:23 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
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 [this message]

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=DC0GIRF0TYEL.DUG78V7F6HID@gmail.com \
    --to=nico.escande@gmail.com \
    --cc=ath11k@lists.infradead.org \
    --cc=jeff.johnson@oss.qualcomm.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lists@steffen-moser.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.