From: Greg KH <gregkh@linuxfoundation.org>
To: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
Cc: stable@vger.kernel.org, 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>,
Baochen Qiang <quic_bqiang@quicinc.com>,
Johan Hovold <johan@kernel.org>
Subject: Re: [PATCH ath-next 0/2] wifi: ath12k: install pairwise key first
Date: Thu, 26 Jun 2025 08:29:58 +0100 [thread overview]
Message-ID: <2025062637-facsimile-chatter-f87a@gregkh> (raw)
In-Reply-To: <e23d7674-31cd-4499-9711-6e5695b149c6@oss.qualcomm.com>
On Wed, Jun 25, 2025 at 07:48:54AM -0700, Jeff Johnson wrote:
> On 6/25/2025 3:15 AM, Baochen Qiang wrote:
> >
> >
> > On 6/25/2025 5:51 PM, Johan Hovold wrote:
> >> [ +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?
> >
> > Yeah, I think they should be backported.
> >
> >>
> >> [ Also please try to remember to CC any (public) reporters. I only found
> >> out today that this had been addressed in linux-next. ]
> >
> > Thanks, will keep in mind.
>
> +Stable team,
> Per the above discussion please backport the series:
> https://msgid.link/20250523-ath12k-unicast-key-first-v1-0-f53c3880e6d8@quicinc.com
<formletter>
This is not the correct way to submit patches for inclusion in the
stable kernel tree. Please read:
https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
for how to do this properly.
</formletter>
next prev parent reply other threads:[~2025-06-26 7:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250523-ath12k-unicast-key-first-v1-0-f53c3880e6d8@quicinc.com>
[not found] ` <aFvGnJwMTqDbYsHF@hovoldconsulting.com>
[not found] ` <2d688040-e547-4e18-905e-ea31ea9d627b@quicinc.com>
2025-06-25 14:48 ` [PATCH ath-next 0/2] wifi: ath12k: install pairwise key first Jeff Johnson
2025-06-25 14:57 ` Johan Hovold
2025-06-25 22:49 ` Jeff Johnson
2025-06-26 7:29 ` Greg KH [this message]
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=2025062637-facsimile-chatter-f87a@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=ath12k@lists.infradead.org \
--cc=gregoire.s93@live.fr \
--cc=jeff.johnson@oss.qualcomm.com \
--cc=jjohnson@kernel.org \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_bqiang@quicinc.com \
--cc=sre@kernel.org \
--cc=stable@vger.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