From: "Nicolas Escande" <nico.escande@gmail.com>
To: "Kalle Valo" <kvalo@kernel.org>
Cc: <ath11k@lists.infradead.org>, <linux-wireless@vger.kernel.org>,
"Steffen Moser" <lists@steffen-moser.de>
Subject: Re: Potential Broadcast Issues After GTK Key Exchange on ath11k with IPQ8072A (QCN5024/QCN5054)
Date: Fri, 17 Jan 2025 20:17:01 +0100 [thread overview]
Message-ID: <D74L8O64EGM3.2CXM7VKQA8O92@gmail.com> (raw)
In-Reply-To: <878qrkdsr7.fsf@kernel.org>
On Thu Jan 9, 2025 at 2:25 PM CET, Kalle Valo wrote:
> "Nicolas Escande" <nico.escande@gmail.com> writes:
>
> > On Sat Dec 28, 2024 at 11:13 AM CET, Steffen Moser wrote:
> >> Dear Remi,
> >>
> >> thank you very much for the pointer to the patch. Sebastian integrated
> >> it into DD-WRT. Now the DynaLink DL-WRX36 runs absolutely smoothly, the
> >> WLAN links are stable, the packet loss is gone. No weird states anymore,
> >> independent from the group key exchange interval:
> >>
> >> https://data.saps.uni-ulm.de/index.php/s/NLNpWqjc8iGsaEM
> >>
> >> So your idea was a direct hit! Thank you very, very much. Several months
> >> of debugging have come to an end...
> >
> > So this is at least the second time this commit breaks a setup.
> >
> > @ath11k why isn't this pushed to mainline ?
> > This seems to be a clear regression, so even if there is no need to rush things
> > in the long run this still needs to to reverted mainline right ?
>
> Good question, I don't have an answer to that. Could someone (also
> outside of Qualcomm) send a proper patch ASAP so that we can solve this?
> And it's good ot include the link to this discussion and describe the
> symptoms the revert is fixing.
>
> This is the patch in question:
>
> 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
Not sure if I did it the right way but it at least is here :
https://lore.kernel.org/linux-wireless/20250117191455.3395145-1-nico.escande@gmail.com/
next prev parent reply other threads:[~2025-01-17 19:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-19 15:02 Potential Broadcast Issues After GTK Key Exchange on ath11k with IPQ8072A (QCN5024/QCN5054) Steffen Moser
2024-12-19 15:35 ` Remi Pommarel
2024-12-20 16:52 ` Sebastian Gottschall
2024-12-28 10:13 ` Steffen Moser
2025-01-07 14:45 ` Nicolas Escande
2025-01-09 13:25 ` Kalle Valo
2025-01-09 16:30 ` Nicolas Escande
2025-01-17 19:17 ` Nicolas Escande [this message]
2025-01-19 0:55 ` Steffen Moser
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=D74L8O64EGM3.2CXM7VKQA8O92@gmail.com \
--to=nico.escande@gmail.com \
--cc=ath11k@lists.infradead.org \
--cc=kvalo@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox