From: Baochen Qiang <baochen.qiang@oss.qualcomm.com>
To: Miaoqing Pan <miaoqing.pan@oss.qualcomm.com>, jjohnson@kernel.org
Cc: ath11k@lists.infradead.org, linux-wireless@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH ath-next 0/2] wifi: ath11k: dp rx sanity checks for invalid length in error paths
Date: Mon, 1 Jun 2026 11:47:59 +0800 [thread overview]
Message-ID: <83065a6c-21ee-4e69-bbda-b499caa0b6ea@oss.qualcomm.com> (raw)
In-Reply-To: <20260512022351.2033155-1-miaoqing.pan@oss.qualcomm.com>
On 5/12/2026 10:23 AM, Miaoqing Pan wrote:
> This patch series adds two defensive sanity checks in ath11k DP RX
> handling to prevent invalid memory access when hardware/descriptor
> contents are unexpected, especially in WBM error scenarios.
>
> Signed-off-by: Miaoqing Pan <miaoqing.pan@oss.qualcomm.com>
> ---
> Miaoqing Pan (2):
> wifi: ath11k: fix invalid data access in ath11k_dp_rx_h_undecap_nwifi
> wifi: ath11k: add MSDU length validation for TKIP MIC error
>
> drivers/net/wireless/ath/ath11k/dp_rx.c | 59 +++++++++++++++++++++++--
> 1 file changed, 56 insertions(+), 3 deletions(-)
>
>
> base-commit: 7b25796f571fc09a7aa6fe7efb23edccd326917d
only nit in patch 1/2, so
Reviewed-by: Baochen Qiang <baochen.qiang@oss.qualcomm.com>
next prev parent reply other threads:[~2026-06-01 3:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-12 2:23 [PATCH ath-next 0/2] wifi: ath11k: dp rx sanity checks for invalid length in error paths Miaoqing Pan
2026-05-12 2:23 ` [PATCH ath-next 1/2] wifi: ath11k: fix invalid data access in ath11k_dp_rx_h_undecap_nwifi Miaoqing Pan
2026-06-01 3:47 ` Baochen Qiang
2026-06-01 16:09 ` Jeff Johnson
2026-05-12 2:23 ` [PATCH ath-next 2/2] wifi: ath11k: add MSDU length validation for TKIP MIC error Miaoqing Pan
2026-06-01 3:47 ` Baochen Qiang [this message]
2026-06-01 13:16 ` [PATCH ath-next 0/2] wifi: ath11k: dp rx sanity checks for invalid length in error paths Rameshkumar Sundaram
2026-06-01 17:00 ` Jeff Johnson
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=83065a6c-21ee-4e69-bbda-b499caa0b6ea@oss.qualcomm.com \
--to=baochen.qiang@oss.qualcomm.com \
--cc=ath11k@lists.infradead.org \
--cc=jjohnson@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=miaoqing.pan@oss.qualcomm.com \
/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