From: Johan Hovold <johan@kernel.org>
To: Baochen Qiang <quic_bqiang@quicinc.com>
Cc: Jeff Johnson <jjohnson@kernel.org>,
linux-wireless@vger.kernel.org, ath12k@lists.infradead.org,
linux-kernel@vger.kernel.org, Gregoire <gregoire.s93@live.fr>,
Sebastian Reichel <sre@kernel.org>
Subject: Re: [PATCH ath-next 0/2] wifi: ath12k: install pairwise key first
Date: Wed, 25 Jun 2025 11:51:24 +0200 [thread overview]
Message-ID: <aFvGnJwMTqDbYsHF@hovoldconsulting.com> (raw)
In-Reply-To: <20250523-ath12k-unicast-key-first-v1-0-f53c3880e6d8@quicinc.com>
[ +CC: Gregoire ]
On Fri, May 23, 2025 at 11:49:00AM +0800, Baochen Qiang wrote:
> We got report that WCN7850 is not working with IWD [1][2]. Debug
> shows the reason is that IWD installs group key before pairwise
> key, which goes against WCN7850's firmware.
>
> Reorder key install to workaround this.
>
> [1] https://bugzilla.kernel.org/show_bug.cgi?id=218733
> [2] https://lore.kernel.org/all/AS8P190MB12051DDBD84CD88E71C40AD7873F2@AS8P190MB1205.EURP190.PROD.OUTLOOK.COM
>
> Signed-off-by: Baochen Qiang <quic_bqiang@quicinc.com>
> ---
> ---
> Baochen Qiang (2):
> wifi: ath12k: avoid bit operation on key flags
> wifi: ath12k: install pairwise key first
Thanks for fixing this, Baochen.
I noticed the patches weren't clearly marked as fixes. Do you think we
should ask the stable team to backport these once they are in mainline
(e.g. after 6.17-rc1 is out)? Or do you think they are too intrusive and
risky to backport or similar?
[ Also please try to remember to CC any (public) reporters. I only found
out today that this had been addressed in linux-next. ]
Johan
next prev parent reply other threads:[~2025-06-25 11:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-23 3:49 [PATCH ath-next 0/2] wifi: ath12k: install pairwise key first Baochen Qiang
2025-05-23 3:49 ` [PATCH ath-next 1/2] wifi: ath12k: avoid bit operation on key flags Baochen Qiang
2025-05-23 3:49 ` [PATCH ath-next 2/2] wifi: ath12k: install pairwise key first Baochen Qiang
2025-06-23 5:44 ` [PATCH ath-next 0/2] " Vasanthakumar Thiagarajan
2025-06-23 14:48 ` Jeff Johnson
2025-06-25 9:51 ` Johan Hovold [this message]
2025-06-25 10:15 ` Baochen Qiang
2025-06-25 14:48 ` Jeff Johnson
2025-06-25 14:57 ` Johan Hovold
2025-06-25 22:49 ` Jeff Johnson
2025-06-26 7:29 ` Greg KH
2025-08-12 15:58 ` Stable Request: " Jeff Johnson
2025-08-12 16:27 ` Greg KH
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=aFvGnJwMTqDbYsHF@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=ath12k@lists.infradead.org \
--cc=gregoire.s93@live.fr \
--cc=jjohnson@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_bqiang@quicinc.com \
--cc=sre@kernel.org \
/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