From: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
To: Johan Hovold <johan@kernel.org>
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>
Subject: Re: [PATCH ath-next 0/2] wifi: ath12k: install pairwise key first
Date: Wed, 25 Jun 2025 15:49:31 -0700 [thread overview]
Message-ID: <35619c11-71e8-4372-b38f-7f1754c777aa@oss.qualcomm.com> (raw)
In-Reply-To: <aFwOVGGHOHbko9So@hovoldconsulting.com>
On 6/25/2025 7:57 AM, Johan Hovold wrote:
> On Wed, Jun 25, 2025 at 07:48:54AM -0700, Jeff Johnson wrote:
>> This is a 0-day issue so ideally this should be backported from 6.6+
>
> By "0-day" you mean it has been there since the driver was added, right
> (and not that it's exploitable or similar)?
correct
next prev parent reply other threads:[~2025-06-25 22:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-23 3:49 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
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 [this message]
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=35619c11-71e8-4372-b38f-7f1754c777aa@oss.qualcomm.com \
--to=jeff.johnson@oss.qualcomm.com \
--cc=ath12k@lists.infradead.org \
--cc=gregoire.s93@live.fr \
--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
all inboxes | Powered by JetHome®