From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sipsolutions.net (s3.sipsolutions.net [168.119.38.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 6AA483D1717; Wed, 20 May 2026 09:53:44 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=168.119.38.16 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1779270826; cv=none; b=qJ2kJQnaT9hSxcfi4AUwoWRatknQoW5FDlzFHSh809why0bW1YA2UarYDHKGcrRjAwOugSDkQIzITj+CLmEcsPzMDuzrkNx3ZeWD0RaAONil0ya4zKtIHqzGq8tiTDQ/pEVP7IQU3W6HJL8s8ajiQT7/7K0PbUJpCOhTUYqkF2E= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1779270826; c=relaxed/simple; bh=sZXNpFdt+miCOLrn5k4RQMB+WiN2cICO9fZ10VRa/y4=; h=Message-ID:Subject:From:To:Cc:Date:In-Reply-To:References: Content-Type:MIME-Version; b=GbXuuwPj3qpFcpBiexGFeekBLqyXZv/5WH0OBsx4FLPfNSFiLAoJslu6tTN0RV+fAdTSPhcznlK+Gdk+WD0PDpxPymu7ePOt/SgYmT2j6sFfCTBvnR1nNeNxrwqu6J0VB9gNh9zVjFpdKWR091VwHqLC11xEeFxehksLMHYBHG0= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=permerror header.from=sipsolutions.net; spf=none smtp.mailfrom=sipsolutions.net; dkim=pass (2048-bit key) header.d=sipsolutions.net header.i=@sipsolutions.net header.b=be7gcUPw; arc=none smtp.client-ip=168.119.38.16 Authentication-Results: smtp.subspace.kernel.org; dmarc=permerror header.from=sipsolutions.net Authentication-Results: smtp.subspace.kernel.org; spf=none smtp.mailfrom=sipsolutions.net Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=sipsolutions.net header.i=@sipsolutions.net header.b="be7gcUPw" DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sipsolutions.net; s=mail; h=MIME-Version:Content-Transfer-Encoding: Content-Type:References:In-Reply-To:Date:Cc:To:From:Subject:Message-ID:Sender :Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From:Resent-To: Resent-Cc:Resent-Message-ID; bh=sZXNpFdt+miCOLrn5k4RQMB+WiN2cICO9fZ10VRa/y4=; t=1779270824; x=1780480424; b=be7gcUPwvbElmV6ckvGLZCdNmeFK52TmFwQknwJmdNOv3AN 8fW8FWb3s3WQ3p00C4uunvyySUMFm4ZNfzz8W2OKnxjcLiA0Raky3LUVZVjYZYDGNQiMifFyJ6nUz dQ0uBDzepUCMOTM1KTW+0T1YSmwmWw6jPspVQe3gYLrvMm402L7NXe9to62D3in3w24jIrLbYCm+a lPtmJvnPddfc7qOtjrtljDhTuieLQA1WKOW+wMrnwt4xClPIFItSuRVXFqVVB89kfEeUxb7bQr1eQ RrKjzcEaBbGtowfTVBNnyEPC6tFVybBeDurX4Lb+p7kbagR7inUaDYAti+cdVxSw==; Received: by sipsolutions.net with esmtpsa (TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (Exim 4.98.2) (envelope-from ) id 1wPdcS-0000000AA3U-2Zqc; Wed, 20 May 2026 11:53:41 +0200 Message-ID: Subject: Re: [PATCH v4] wifi: mac80211: fix monitor mode frame capture for real chanctx drivers From: Johannes Berg To: =?ISO-8859-1?Q?=D3scar?= Alfonso =?ISO-8859-1?Q?D=EDaz?= Cc: Devin Wittmayer , linux-wireless@vger.kernel.org, Felix Fietkau , Lorenzo Bianconi , linux-kernel@vger.kernel.org, stable@vger.kernel.org, fjhhz1997@gmail.com, Brite Date: Wed, 20 May 2026 11:53:39 +0200 In-Reply-To: (sfid-20260520_115117_436034_41AED6CB) References: <20260518170147.13885-1-lucid_duck@justthetip.ca> <20260519235713.49109-1-lucid_duck@justthetip.ca> <20260519235713.49109-2-lucid_duck@justthetip.ca> <739ba20fa3c88e92bf034d80383015b8bc78ebfe.camel@sipsolutions.net> (sfid-20260520_115117_436034_41AED6CB) Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.58.3 (3.58.3-1.fc43) Precedence: bulk X-Mailing-List: linux-wireless@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-malware-bazaar: not-scanned On Wed, 2026-05-20 at 11:51 +0200, =C3=93scar Alfonso D=C3=ADaz wrote: > Ok, let me do one final test using Johannes=E2=80=99 v2 patch. The expect= ed > behavior is as follows: >=20 > 6.18 or lower: no need to test, it will not work. It=E2=80=99s clear now = that > this does not matter, since the goal is only to fix newer kernel > versions. >=20 > 6.19: some versions of the 6.19 will crash and others will not. The > crash was fixed at some point between 6.18.12 and 6.19.12. No need to > test. >=20 > 7.0, or 7.1: the expected result is that there will be no crash, and > VIF + deauth will work only on 2.4 GHz. It will not work on 5 GHz > (I'll test both, normal DoS and VIF+DoS). There should be no crash, > but it will not work. >=20 > So I'll focus my testing on 7.0 and 7.1 and I'll get back to you with > the results. I'll be testing this patch (v2): > https://patchwork.kernel.org/project/linux-wireless/patch/20251216111909.= 25076-2-johannes@sipsolutions.net/ >=20 Thanks. For testing that one you'd have to revert the other first, I think, you could also just test this one: https://patchwork.kernel.org/project/linux-wireless/patch/20260519235713.49= 109-2-lucid_duck@justthetip.ca/ But I think they're basically all equivalent. Since we eventually need a patch to apply w/o reverting, Devin's is probably better than my old one. johannes