linux-kernel - Re: [PATCH wireless-next 1/2] wifi: mac80211: validate SCAN_FLAG

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <d211e634532031322a77053ff912394714b5ff35.camel@sipsolutions.net>
Date: Tue, 13 May 2025 12:48:18 +0200
From: Johannes Berg <johannes@...solutions.net>
To: Aditya Kumar Singh <aditya.kumar.singh@....qualcomm.com>
Cc: linux-wireless@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH wireless-next 1/2] wifi: mac80211: validate SCAN_FLAG_AP
 in scan request during MLO

On Tue, 2025-05-13 at 16:02 +0530, Aditya Kumar Singh wrote:
> 
> Okay sure let me first send a clean up. So, 
> ieee80211_num_beaconing_links() should return 1 for non-MLO as well?
> 

That would seem logical to me? For this and many other things non-MLO is
mostly equivalent to just having a single link (apart from the address
translation.)

> And callers should test for == 1 instead of <= 1.

Not even sure that matters enough to need to change?

johannes