2019-06-01 10:08:46 +02:00
|
|
|
|
2007-05-05 11:45:53 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-02-15 12:53:10 +02:00
|
|
|
|
2015-06-01 22:54:13 +02:00
|
|
|
|
mac80211: reject/clear user rate mask if not usable
If the user rate mask results in no (basic) rates being usable,
clear it. Also, if we're already operating when it's set, reject
it instead.
Technically, selecting basic rates as the criterion is a bit too
restrictive, but calculating the usable rates over all stations
(e.g. in AP mode) is harder, and all stations must support the
basic rates. Similarly, in client mode, the basic rates will be
used anyway for control frames.
This fixes the "no supported rates (...) in rate_mask ..." warning
that occurs on TX when you've selected a rate mask that's not
compatible with the connection (e.g. an AP that enables only the
rates 36, 48, 54 and you've selected only 6, 9, 12.)
Reported-by: Kirtika Ruchandani <kirtika@google.com>
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2017-03-08 11:12:10 +01:00
|
|
|
|
2026-01-30 16:21:07 +01:00
|
|
|
|
2007-05-05 11:45:53 -07:00
|
|
|
|
|
|
|
|
|
2007-12-19 02:03:30 +01:00
|
|
|
|
2007-05-05 11:45:53 -07:00
|
|
|
|
|
|
|
|
|
include cleanup: Update gfp.h and slab.h includes to prepare for breaking implicit slab.h inclusion from percpu.h
percpu.h is included by sched.h and module.h and thus ends up being
included when building most .c files. percpu.h includes slab.h which
in turn includes gfp.h making everything defined by the two files
universally available and complicating inclusion dependencies.
percpu.h -> slab.h dependency is about to be removed. Prepare for
this change by updating users of gfp and slab facilities include those
headers directly instead of assuming availability. As this conversion
needs to touch large number of source files, the following script is
used as the basis of conversion.
http://userweb.kernel.org/~tj/misc/slabh-sweep.py
The script does the followings.
* Scan files for gfp and slab usages and update includes such that
only the necessary includes are there. ie. if only gfp is used,
gfp.h, if slab is used, slab.h.
* When the script inserts a new include, it looks at the include
blocks and try to put the new include such that its order conforms
to its surrounding. It's put in the include block which contains
core kernel includes, in the same order that the rest are ordered -
alphabetical, Christmas tree, rev-Xmas-tree or at the end if there
doesn't seem to be any matching order.
* If the script can't find a place to put a new include (mostly
because the file doesn't have fitting include block), it prints out
an error message indicating which .h file needs to be added to the
file.
The conversion was done in the following steps.
1. The initial automatic conversion of all .c files updated slightly
over 4000 files, deleting around 700 includes and adding ~480 gfp.h
and ~3000 slab.h inclusions. The script emitted errors for ~400
files.
2. Each error was manually checked. Some didn't need the inclusion,
some needed manual addition while adding it to implementation .h or
embedding .c file was more appropriate for others. This step added
inclusions to around 150 files.
3. The script was run again and the output was compared to the edits
from #2 to make sure no file was left behind.
4. Several build tests were done and a couple of problems were fixed.
e.g. lib/decompress_*.c used malloc/free() wrappers around slab
APIs requiring slab.h to be added manually.
5. The script was run on all .h files but without automatically
editing them as sprinkling gfp.h and slab.h inclusions around .h
files could easily lead to inclusion dependency hell. Most gfp.h
inclusion directives were ignored as stuff from gfp.h was usually
wildly available and often used in preprocessor macros. Each
slab.h inclusion directive was examined and added manually as
necessary.
6. percpu.h was updated not to include slab.h.
7. Build test were done on the following configurations and failures
were fixed. CONFIG_GCOV_KERNEL was turned off for all tests (as my
distributed build env didn't work with gcov compiles) and a few
more options had to be turned off depending on archs to make things
build (like ipr on powerpc/64 which failed due to missing writeq).
* x86 and x86_64 UP and SMP allmodconfig and a custom test config.
* powerpc and powerpc64 SMP allmodconfig
* sparc and sparc64 SMP allmodconfig
* ia64 SMP allmodconfig
* s390 SMP allmodconfig
* alpha SMP allmodconfig
* um on x86_64 SMP allmodconfig
8. percpu.h modifications were reverted so that it could be applied as
a separate patch and serve as bisection point.
Given the fact that I had only a couple of failures from tests on step
6, I'm fairly confident about the coverage of this conversion patch.
If there is a breakage, it's likely to be something in one of the arch
headers which should be easily discoverable easily on most builds of
the specific arch.
Signed-off-by: Tejun Heo <tj@kernel.org>
Guess-its-ok-by: Christoph Lameter <cl@linux-foundation.org>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
2010-03-24 17:04:11 +09:00
|
|
|
|
2007-09-17 11:56:21 -07:00
|
|
|
|
2007-12-19 02:03:33 +01:00
|
|
|
|
2019-06-12 18:19:54 +02:00
|
|
|
|
2011-09-28 14:12:52 +03:00
|
|
|
|
2007-05-05 11:45:53 -07:00
|
|
|
|
|
|
|
|
|
2009-04-23 18:52:52 +02:00
|
|
|
|
2008-04-08 15:14:40 -04:00
|
|
|
|
2008-02-23 15:17:17 +01:00
|
|
|
|
2014-10-07 10:38:50 +03:00
|
|
|
|
2008-02-23 15:17:17 +01:00
|
|
|
|
2022-08-02 15:22:42 +03:00
|
|
|
|
2022-08-17 11:17:01 +02:00
|
|
|
|
|
|
|
|
|
2022-08-02 15:22:42 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-08-17 11:17:01 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-08 16:36:08 +03:00
|
|
|
|
2022-08-02 15:22:42 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-04-12 12:36:31 +02:00
|
|
|
|
|
|
|
|
|
2017-04-12 10:46:13 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-04-12 12:36:31 +02:00
|
|
|
|
2017-04-12 10:46:13 +02:00
|
|
|
|
2017-04-12 12:36:31 +02:00
|
|
|
|
2017-04-12 10:46:13 +02:00
|
|
|
|
|
|
|
|
|
2025-11-10 14:18:20 +02:00
|
|
|
|
2017-04-12 10:46:13 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-11-10 14:18:20 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-04-12 10:46:13 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-04-12 12:36:31 +02:00
|
|
|
|
2017-04-12 10:46:13 +02:00
|
|
|
|
2025-11-10 14:18:20 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-04-12 10:46:13 +02:00
|
|
|
|
|
|
|
|
|
wifi: mac80211: move some future per-link data to bss_conf
To add MLD, reuse the bss_conf structure later for per-link
information, so move some things into it that are per link.
Most transformations were done with the following spatch:
@@
expression sdata;
identifier var = { chanctx_conf, mu_mimo_owner, csa_active, color_change_active, color_change_color };
@@
-sdata->vif.var
+sdata->vif.bss_conf.var
@@
struct ieee80211_vif *vif;
identifier var = { chanctx_conf, mu_mimo_owner, csa_active, color_change_active, color_change_color };
@@
-vif->var
+vif->bss_conf.var
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2022-05-10 13:26:44 +02:00
|
|
|
|
2025-11-10 14:18:20 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-04-12 12:36:31 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-11-10 14:18:20 +02:00
|
|
|
|
2017-04-12 12:36:31 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-02-04 12:13:52 +01:00
|
|
|
|
2017-04-12 12:36:31 +02:00
|
|
|
|
|
|
|
|
|
2025-02-04 12:13:52 +01:00
|
|
|
|
|
|
|
|
|
2017-04-12 12:36:31 +02:00
|
|
|
|
|
|
|
|
|
2025-02-04 12:13:52 +01:00
|
|
|
|
2017-04-12 12:36:31 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-11-10 14:18:20 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-04-12 12:36:31 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-11-10 14:18:20 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-04-12 12:36:31 +02:00
|
|
|
|
|
|
|
|
|
2025-11-10 14:18:20 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-04-12 12:36:31 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-04-12 10:46:13 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-09-15 19:54:35 -07:00
|
|
|
|
2024-11-08 09:22:27 +01:00
|
|
|
|
2022-06-01 12:55:14 +03:00
|
|
|
|
2021-09-15 19:54:35 -07:00
|
|
|
|
|
|
|
|
|
2025-04-08 11:45:00 -07:00
|
|
|
|
2021-09-15 19:54:35 -07:00
|
|
|
|
2022-06-01 12:55:14 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-12-21 10:56:16 -08:00
|
|
|
|
2021-09-15 19:54:35 -07:00
|
|
|
|
2024-11-08 09:22:27 +01:00
|
|
|
|
2021-09-15 19:54:35 -07:00
|
|
|
|
|
|
|
|
|
2025-04-08 11:45:00 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-11-08 09:22:27 +01:00
|
|
|
|
2021-09-15 19:54:35 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-04-08 11:45:00 -07:00
|
|
|
|
2021-09-15 19:54:35 -07:00
|
|
|
|
2025-04-08 11:45:00 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-06-01 12:55:14 +03:00
|
|
|
|
2024-11-08 09:22:27 +01:00
|
|
|
|
2025-05-30 09:39:40 +05:30
|
|
|
|
2021-09-15 19:54:35 -07:00
|
|
|
|
2024-11-08 09:22:27 +01:00
|
|
|
|
2022-06-01 12:55:14 +03:00
|
|
|
|
2021-09-15 19:54:35 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-09-19 09:26:06 +02:00
|
|
|
|
|
|
|
|
|
2015-03-18 11:13:39 +01:00
|
|
|
|
2012-06-16 00:00:26 +02:00
|
|
|
|
|
|
|
|
|
2007-05-05 11:45:53 -07:00
|
|
|
|
|
|
|
|
|
2012-06-16 00:00:26 +02:00
|
|
|
|
2008-01-31 19:48:23 +01:00
|
|
|
|
|
|
|
|
|
2007-05-05 11:45:53 -07:00
|
|
|
|
2015-03-18 11:13:39 +01:00
|
|
|
|
2010-12-03 09:20:42 +01:00
|
|
|
|
|
|
|
|
|
2008-01-31 19:48:23 +01:00
|
|
|
|
2017-04-12 10:46:13 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-04-12 12:36:31 +02:00
|
|
|
|
2017-04-12 10:46:13 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-12-03 09:20:42 +01:00
|
|
|
|
|
|
|
|
|
2024-10-07 15:00:45 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-06-16 00:00:26 +02:00
|
|
|
|
2007-05-05 11:45:53 -07:00
|
|
|
|
|
|
|
|
|
2012-06-16 00:00:26 +02:00
|
|
|
|
2007-05-05 11:45:53 -07:00
|
|
|
|
2012-06-16 00:00:26 +02:00
|
|
|
|
2007-05-05 11:45:53 -07:00
|
|
|
|
2008-07-09 14:40:35 +02:00
|
|
|
|
2007-05-05 11:45:53 -07:00
|
|
|
|
|
|
|
|
|
2009-06-09 21:04:43 +02:00
|
|
|
|
|
|
|
|
|
2017-04-12 11:23:28 +02:00
|
|
|
|
2008-02-23 15:17:06 +01:00
|
|
|
|
2007-09-28 21:52:27 +02:00
|
|
|
|
2009-12-23 13:15:31 +01:00
|
|
|
|
2021-07-02 07:01:11 +02:00
|
|
|
|
|
|
|
|
|
2008-07-09 14:40:36 +02:00
|
|
|
|
2007-09-28 21:52:27 +02:00
|
|
|
|
2023-08-28 14:00:01 +02:00
|
|
|
|
|
|
|
|
|
2008-09-11 00:01:58 +02:00
|
|
|
|
2008-07-09 14:40:36 +02:00
|
|
|
|
|
|
|
|
|
2007-09-28 21:52:27 +02:00
|
|
|
|
2018-08-31 11:31:05 +03:00
|
|
|
|
2011-08-01 16:19:00 +00:00
|
|
|
|
2016-03-31 20:02:10 +03:00
|
|
|
|
2018-08-31 11:31:05 +03:00
|
|
|
|
2021-07-02 07:01:11 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-11-19 11:55:19 +01:00
|
|
|
|
2021-07-02 07:01:11 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-05-16 15:00:15 +02:00
|
|
|
|
2021-07-02 07:01:11 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-03-31 20:02:10 +03:00
|
|
|
|
2009-11-19 11:55:19 +01:00
|
|
|
|
2016-08-29 23:25:16 +03:00
|
|
|
|
2017-04-12 12:36:31 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-10-02 13:17:07 +02:00
|
|
|
|
2010-04-27 00:26:34 +02:00
|
|
|
|
2007-09-28 21:52:27 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-06-18 20:07:15 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-02-27 11:07:21 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-08-28 14:00:03 +02:00
|
|
|
|
|
|
|
|
|
2024-07-09 10:38:35 +02:00
|
|
|
|
2014-02-27 11:07:21 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-06-18 20:07:15 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-09-08 14:13:07 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-03-02 09:11:46 +02:00
|
|
|
|
|
|
|
|
|
2025-09-08 14:13:07 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-09-20 17:31:14 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-08-28 14:00:03 +02:00
|
|
|
|
|
|
|
|
|
2025-09-08 14:13:04 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-07-09 10:38:35 +02:00
|
|
|
|
2016-09-20 17:31:14 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-09-08 14:13:04 +03:00
|
|
|
|
2016-09-20 17:31:14 +03:00
|
|
|
|
2025-09-08 14:13:04 +03:00
|
|
|
|
|
|
|
|
|
2016-09-20 17:31:14 +03:00
|
|
|
|
2025-09-08 14:13:04 +03:00
|
|
|
|
|
|
|
|
|
2016-09-20 17:31:20 +03:00
|
|
|
|
2025-09-08 14:13:07 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-09-08 14:13:04 +03:00
|
|
|
|
|
|
|
|
|
2016-09-20 17:31:14 +03:00
|
|
|
|
|
|
|
|
|
2016-09-20 17:31:19 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-09-08 14:13:07 +03:00
|
|
|
|
2016-09-20 17:31:19 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-09-08 14:13:07 +03:00
|
|
|
|
|
|
|
|
|
2016-09-20 17:31:19 +03:00
|
|
|
|
2025-09-08 14:13:07 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-09-20 17:31:19 +03:00
|
|
|
|
2025-09-08 14:13:07 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-09-20 17:31:19 +03:00
|
|
|
|
|
|
|
|
|
2025-09-08 14:13:07 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-09-20 17:31:19 +03:00
|
|
|
|
2025-09-08 14:13:07 +03:00
|
|
|
|
2016-09-20 17:31:19 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-09-20 17:31:20 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-03-26 12:14:34 +02:00
|
|
|
|
|
|
|
|
|
2016-09-20 17:31:20 +03:00
|
|
|
|
2026-03-26 12:14:34 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-09-20 17:31:20 +03:00
|
|
|
|
|
|
|
|
|
2026-03-26 12:14:34 +02:00
|
|
|
|
2016-09-20 17:31:20 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-03-26 12:14:34 +02:00
|
|
|
|
|
|
|
|
|
2016-09-20 17:31:20 +03:00
|
|
|
|
2026-03-26 12:14:34 +02:00
|
|
|
|
2016-09-20 17:31:20 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-03-26 12:14:34 +02:00
|
|
|
|
2016-09-20 17:31:20 +03:00
|
|
|
|
2026-03-26 12:14:34 +02:00
|
|
|
|
2016-09-20 17:31:20 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-03-26 12:14:34 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-09-20 17:31:20 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-03-26 12:14:34 +02:00
|
|
|
|
2016-09-20 17:31:20 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-11-18 14:20:44 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-03-21 15:25:43 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-11-18 14:20:44 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-03-19 21:34:08 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-08-28 14:00:02 +02:00
|
|
|
|
2019-03-19 21:34:08 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-01-07 15:20:02 +02:00
|
|
|
|
2022-07-30 10:56:43 +05:30
|
|
|
|
|
|
|
|
|
2007-12-19 02:03:30 +01:00
|
|
|
|
2026-01-07 15:20:02 +02:00
|
|
|
|
2022-08-17 11:17:01 +02:00
|
|
|
|
|
|
|
|
|
2013-03-24 14:23:27 +02:00
|
|
|
|
2007-12-19 02:03:30 +01:00
|
|
|
|
2008-02-25 16:27:45 +01:00
|
|
|
|
2008-04-08 17:56:52 +02:00
|
|
|
|
2023-08-28 14:00:01 +02:00
|
|
|
|
|
|
|
|
|
2007-12-19 02:03:30 +01:00
|
|
|
|
2010-08-27 12:35:55 +02:00
|
|
|
|
2010-06-01 10:19:19 +02:00
|
|
|
|
|
|
|
|
|
2022-08-17 11:17:01 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-01-02 16:20:05 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-03-19 21:34:08 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-08-10 09:46:38 +02:00
|
|
|
|
2007-12-19 02:03:30 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-08-10 09:46:38 +02:00
|
|
|
|
2022-08-17 11:17:01 +02:00
|
|
|
|
|
|
|
|
|
2019-06-12 18:19:54 +02:00
|
|
|
|
2010-08-10 09:46:38 +02:00
|
|
|
|
2020-11-20 12:36:45 -06:00
|
|
|
|
2007-12-19 02:03:30 +01:00
|
|
|
|
2010-08-10 09:46:38 +02:00
|
|
|
|
2007-12-19 02:03:30 +01:00
|
|
|
|
|
|
|
|
|
2010-08-10 09:46:38 +02:00
|
|
|
|
2022-02-09 13:14:26 +01:00
|
|
|
|
2010-08-01 17:37:03 +01:00
|
|
|
|
|
|
|
|
|
2008-02-25 16:27:45 +01:00
|
|
|
|
2025-01-02 16:20:05 +02:00
|
|
|
|
2010-10-05 19:39:30 +02:00
|
|
|
|
2025-01-02 16:20:05 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-10-05 19:39:30 +02:00
|
|
|
|
2019-03-19 21:34:08 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-12-19 02:03:30 +01:00
|
|
|
|
2016-10-04 15:32:16 +02:00
|
|
|
|
2013-01-11 14:34:25 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-10-29 22:55:58 -07:00
|
|
|
|
2013-01-11 14:34:25 +01:00
|
|
|
|
2026-01-14 16:48:56 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-01-11 14:34:25 +01:00
|
|
|
|
2026-01-14 16:48:56 +05:30
|
|
|
|
2013-01-11 14:34:25 +01:00
|
|
|
|
2026-01-14 16:48:56 +05:30
|
|
|
|
|
|
|
|
|
2013-03-06 22:53:52 +01:00
|
|
|
|
2023-08-28 14:00:01 +02:00
|
|
|
|
2008-02-25 16:27:45 +01:00
|
|
|
|
2007-12-19 02:03:30 +01:00
|
|
|
|
|
|
|
|
|
2012-09-04 17:08:23 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-03-26 12:14:45 +02:00
|
|
|
|
|
|
|
|
|
2012-09-04 17:08:23 +02:00
|
|
|
|
2018-09-29 16:01:58 +02:00
|
|
|
|
2012-09-04 17:08:23 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-04-20 14:38:46 +05:30
|
|
|
|
2012-09-04 17:08:23 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-11-03 10:33:18 +01:00
|
|
|
|
2012-09-04 17:08:23 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-08-17 11:17:01 +02:00
|
|
|
|
2023-09-19 08:34:15 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-02-25 16:27:45 +01:00
|
|
|
|
2008-04-08 17:56:52 +02:00
|
|
|
|
2007-12-19 02:03:30 +01:00
|
|
|
|
|
|
|
|
|
2022-05-19 23:27:22 +02:00
|
|
|
|
2022-08-17 11:17:01 +02:00
|
|
|
|
2022-05-19 23:27:22 +02:00
|
|
|
|
|
|
|
|
|
2022-11-11 16:36:22 +01:00
|
|
|
|
2022-08-17 11:17:01 +02:00
|
|
|
|
2022-05-16 15:00:15 +02:00
|
|
|
|
2022-08-17 11:17:01 +02:00
|
|
|
|
|
|
|
|
|
2023-08-29 12:18:56 +02:00
|
|
|
|
2022-08-17 11:17:01 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-05-19 23:27:22 +02:00
|
|
|
|
|
|
|
|
|
2022-08-17 11:17:01 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-05-19 23:27:22 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-08-17 11:17:01 +02:00
|
|
|
|
|
|
|
|
|
2023-08-28 14:00:01 +02:00
|
|
|
|
2022-08-17 11:17:01 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-05-19 23:27:22 +02:00
|
|
|
|
2023-08-28 14:00:02 +02:00
|
|
|
|
|
|
|
|
|
2022-05-19 23:27:22 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-08-28 14:00:02 +02:00
|
|
|
|
|
|
|
|
|
2022-05-19 23:27:22 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-05-16 15:00:15 +02:00
|
|
|
|
2023-08-28 14:00:02 +02:00
|
|
|
|
2022-05-19 23:27:22 +02:00
|
|
|
|
2023-08-28 14:00:02 +02:00
|
|
|
|
2022-05-16 15:00:15 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-06-23 22:21:28 +02:00
|
|
|
|
|
|
|
|
|
2023-08-28 14:00:02 +02:00
|
|
|
|
2022-06-23 22:21:28 +02:00
|
|
|
|
2022-05-19 23:27:22 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-01-07 15:20:02 +02:00
|
|
|
|
2022-07-30 10:56:43 +05:30
|
|
|
|
|
|
|
|
|
2007-12-19 02:03:30 +01:00
|
|
|
|
2026-01-07 15:20:02 +02:00
|
|
|
|
2011-05-12 14:31:49 +02:00
|
|
|
|
2022-05-19 23:27:22 +02:00
|
|
|
|
2007-12-19 02:03:30 +01:00
|
|
|
|
2023-08-28 14:00:01 +02:00
|
|
|
|
|
|
|
|
|
2022-08-17 11:17:01 +02:00
|
|
|
|
2023-08-28 14:00:02 +02:00
|
|
|
|
|
|
|
|
|
2007-12-19 02:03:30 +01:00
|
|
|
|
mac80211: restrict delayed tailroom needed decrement
As explained in ieee80211_delayed_tailroom_dec(), during roam,
keys of the old AP will be destroyed and new keys will be
installed. Deletion of the old key causes
crypto_tx_tailroom_needed_cnt to go from 1 to 0 and the new key
installation causes a transition from 0 to 1.
Whenever crypto_tx_tailroom_needed_cnt transitions from 0 to 1,
we invoke synchronize_net(); the reason for doing this is to avoid
a race in the TX path as explained in increment_tailroom_need_count().
This synchronize_net() operation can be slow and can affect the station
roam time. To avoid this, decrementing the crypto_tx_tailroom_needed_cnt
is delayed for a while so that upon installation of new key the
transition would be from 1 to 2 instead of 0 to 1 and thereby
improving the roam time.
This is all correct for a STA iftype, but deferring the tailroom_needed
decrement for other iftypes may be unnecessary.
For example, let's consider the case of a 4-addr client connecting to
an AP for which AP_VLAN interface is also created, let the initial
value for tailroom_needed on the AP be 1.
* 4-addr client connects to the AP (AP: tailroom_needed = 1)
* AP will clear old keys, delay decrement of tailroom_needed count
* AP_VLAN is created, it takes the tailroom count from master
(AP_VLAN: tailroom_needed = 1, AP: tailroom_needed = 1)
* Install new key for the station, assume key is plumbed in the HW,
there won't be any change in tailroom_needed count on AP iface
* Delayed decrement of tailroom_needed count on AP
(AP: tailroom_needed = 0, AP_VLAN: tailroom_needed = 1)
Because of the delayed decrement on AP iface, tailroom_needed count goes
out of sync between AP(master iface) and AP_VLAN(slave iface) and
there would be unnecessary tailroom created for the packets going
through AP_VLAN iface.
Also, WARN_ONs were observed while trying to bring down the AP_VLAN
interface:
(warn_slowpath_common) (warn_slowpath_null+0x18/0x20)
(warn_slowpath_null) (ieee80211_free_keys+0x114/0x1e4)
(ieee80211_free_keys) (ieee80211_del_virtual_monitor+0x51c/0x850)
(ieee80211_del_virtual_monitor) (ieee80211_stop+0x30/0x3c)
(ieee80211_stop) (__dev_close_many+0x94/0xb8)
(__dev_close_many) (dev_close_many+0x5c/0xc8)
Restricting delayed decrement to station interface alone fixes the problem
and it makes sense to do so because delayed decrement is done to improve
roam time which is applicable only for client devices.
Signed-off-by: Manikanta Pubbisetty <mpubbise@codeaurora.org>
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2018-07-10 16:48:27 +05:30
|
|
|
|
2007-12-19 02:03:30 +01:00
|
|
|
|
2023-08-28 14:00:02 +02:00
|
|
|
|
2007-12-19 02:03:30 +01:00
|
|
|
|
|
|
|
|
|
2026-01-07 15:20:02 +02:00
|
|
|
|
2022-07-30 10:56:43 +05:30
|
|
|
|
|
|
|
|
|
2007-12-19 02:03:31 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-07-29 13:22:52 +02:00
|
|
|
|
2007-12-19 02:03:31 +01:00
|
|
|
|
|
|
|
|
|
2022-05-19 23:27:22 +02:00
|
|
|
|
2011-07-06 21:59:39 +02:00
|
|
|
|
2007-12-19 02:03:31 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-04-20 18:12:41 +02:00
|
|
|
|
2007-12-19 02:03:31 +01:00
|
|
|
|
2026-01-07 15:20:02 +02:00
|
|
|
|
2008-07-29 13:22:52 +02:00
|
|
|
|
2008-04-08 17:56:52 +02:00
|
|
|
|
|
|
|
|
|
2022-08-17 11:17:01 +02:00
|
|
|
|
2007-12-19 02:03:31 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-08-10 09:46:38 +02:00
|
|
|
|
2007-12-19 02:03:31 +01:00
|
|
|
|
2010-08-10 09:46:38 +02:00
|
|
|
|
|
|
|
|
|
2016-02-14 13:56:35 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-12-19 02:03:31 +01:00
|
|
|
|
2015-04-20 18:12:41 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-12-19 02:03:31 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-08-10 09:46:38 +02:00
|
|
|
|
2015-01-24 19:52:07 +02:00
|
|
|
|
2015-06-01 15:36:51 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-07-07 15:45:48 -05:00
|
|
|
|
2015-06-01 15:36:51 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-07-07 15:45:48 -05:00
|
|
|
|
2015-06-01 15:36:51 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-04-20 18:12:41 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-06-01 15:36:51 +02:00
|
|
|
|
2015-04-20 18:12:41 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-01-24 19:52:06 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-04-20 18:21:58 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-12-19 02:03:31 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-04-08 17:56:52 +02:00
|
|
|
|
2007-12-19 02:03:31 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-12-19 02:03:30 +01:00
|
|
|
|
|
|
|
|
|
2022-07-30 10:56:43 +05:30
|
|
|
|
2010-12-09 19:58:59 +01:00
|
|
|
|
2007-12-19 02:03:30 +01:00
|
|
|
|
2010-06-01 10:19:19 +02:00
|
|
|
|
2022-08-17 11:17:01 +02:00
|
|
|
|
|
|
|
|
|
2007-12-19 02:03:30 +01:00
|
|
|
|
2022-08-17 11:17:01 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-12-19 02:03:30 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-01-08 13:32:02 +02:00
|
|
|
|
2026-01-07 15:20:02 +02:00
|
|
|
|
2022-07-30 10:56:43 +05:30
|
|
|
|
2009-01-08 13:32:02 +02:00
|
|
|
|
2026-01-07 15:20:02 +02:00
|
|
|
|
2022-08-17 11:17:01 +02:00
|
|
|
|
|
|
|
|
|
2009-01-08 13:32:02 +02:00
|
|
|
|
2022-08-17 11:17:01 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-01-08 13:32:02 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-02-22 15:25:44 +02:00
|
|
|
|
2026-01-07 15:20:02 +02:00
|
|
|
|
2022-07-30 10:56:43 +05:30
|
|
|
|
2020-02-22 15:25:44 +02:00
|
|
|
|
2026-01-07 15:20:02 +02:00
|
|
|
|
2022-08-17 11:17:01 +02:00
|
|
|
|
|
|
|
|
|
2020-02-22 15:25:44 +02:00
|
|
|
|
2022-08-17 11:17:01 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-02-22 15:25:44 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-03-05 15:31:48 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-11-09 18:38:32 +01:00
|
|
|
|
2012-03-05 15:31:48 -08:00
|
|
|
|
2012-11-09 18:38:32 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-07-08 16:55:53 +02:00
|
|
|
|
2017-04-27 12:45:38 +05:30
|
|
|
|
2020-10-05 09:45:21 -07:00
|
|
|
|
2023-08-29 12:17:44 +02:00
|
|
|
|
|
|
|
|
|
2012-11-09 18:38:32 +01:00
|
|
|
|
2012-03-05 15:31:48 -08:00
|
|
|
|
2015-01-15 16:14:02 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-03-05 15:31:48 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-02-19 11:47:13 +02:00
|
|
|
|
2014-05-19 17:19:31 +02:00
|
|
|
|
2008-02-23 15:17:17 +01:00
|
|
|
|
2026-02-19 11:47:13 +02:00
|
|
|
|
2012-06-21 10:56:46 +03:00
|
|
|
|
2008-02-23 15:17:17 +01:00
|
|
|
|
2008-02-25 16:27:46 +01:00
|
|
|
|
|
|
|
|
|
2023-08-28 14:00:01 +02:00
|
|
|
|
2008-02-23 15:17:17 +01:00
|
|
|
|
2009-11-16 12:00:37 +01:00
|
|
|
|
2008-02-25 16:27:46 +01:00
|
|
|
|
|
|
|
|
|
2008-09-11 00:02:02 +02:00
|
|
|
|
2018-05-18 11:40:44 +02:00
|
|
|
|
2025-05-28 11:14:16 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-02-25 16:27:46 +01:00
|
|
|
|
2008-02-23 15:17:17 +01:00
|
|
|
|
2008-02-25 16:27:46 +01:00
|
|
|
|
2008-02-23 15:17:17 +01:00
|
|
|
|
|
|
|
|
|
2010-04-19 10:23:57 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-02-19 11:47:13 +02:00
|
|
|
|
|
|
|
|
|
2014-05-19 17:19:31 +02:00
|
|
|
|
2007-12-19 02:03:37 +01:00
|
|
|
|
2026-02-19 11:47:13 +02:00
|
|
|
|
2012-06-21 10:56:46 +03:00
|
|
|
|
2007-12-19 02:03:37 +01:00
|
|
|
|
2008-02-25 16:27:46 +01:00
|
|
|
|
2007-12-19 02:03:37 +01:00
|
|
|
|
2023-08-28 14:00:01 +02:00
|
|
|
|
2007-12-19 02:03:37 +01:00
|
|
|
|
2010-01-08 18:10:58 +01:00
|
|
|
|
2008-02-25 16:27:46 +01:00
|
|
|
|
|
|
|
|
|
2018-05-18 11:40:44 +02:00
|
|
|
|
2025-05-28 11:14:16 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-02-25 16:27:46 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-12-19 02:03:37 +01:00
|
|
|
|
|
|
|
|
|
2012-06-06 08:18:22 +02:00
|
|
|
|
2024-10-09 10:25:47 +02:00
|
|
|
|
2012-11-08 21:25:48 +01:00
|
|
|
|
2012-06-06 08:18:22 +02:00
|
|
|
|
2012-07-26 17:24:39 +02:00
|
|
|
|
|
|
|
|
|
wifi: mac80211: introduce 'channel request'
For channel contexts, mac80211 currently uses the cfg80211
chandef struct (control channel, center freq(s), width) to
define towards drivers and internally how these behave. In
fact, there are _two_ such structs used, where the min_def
can reduce bandwidth according to the stations connected.
Unfortunately, with EHT this is longer be sufficient, at
least not for all hardware. EHT requires that non-AP STAs
that are connected to an AP with a lower bandwidth than it
(the AP) advertises (e.g. 160 MHz STA connected to 320 MHz
AP) still be able to receive downlink OFDMA and respond to
trigger frames for uplink OFDMA that specify the position
and bandwidth for the non-AP STA relative to the channel
the AP is using. Therefore, they need to be aware of this,
and at least for some hardware (e.g. Intel) this awareness
is in the hardware. As a result, use of the "same" channel
may need to be split over two channel contexts where they
differ by the AP being used.
As a first step, introduce a concept of a channel request
('chanreq') for each interface, to control the context it
requests. This step does nothing but reorganise the code,
so that later the AP's chandef can be added to the request
in order to handle the EHT case described above.
Link: https://msgid.link/20240129194108.2e88e48bd2e9.I4256183debe975c5ed71621611206fdbb69ba330@changeid
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2024-01-29 19:34:40 +01:00
|
|
|
|
2024-01-29 19:34:38 +01:00
|
|
|
|
2012-07-26 17:24:39 +02:00
|
|
|
|
2023-08-28 14:00:05 +02:00
|
|
|
|
|
|
|
|
|
2024-10-09 10:25:48 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-03-18 09:54:46 +01:00
|
|
|
|
2024-10-09 10:25:48 +02:00
|
|
|
|
2012-07-26 17:24:39 +02:00
|
|
|
|
2024-10-09 10:25:48 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-07-26 17:24:39 +02:00
|
|
|
|
2024-10-09 10:25:48 +02:00
|
|
|
|
2025-03-18 09:54:46 +01:00
|
|
|
|
wifi: mac80211: introduce 'channel request'
For channel contexts, mac80211 currently uses the cfg80211
chandef struct (control channel, center freq(s), width) to
define towards drivers and internally how these behave. In
fact, there are _two_ such structs used, where the min_def
can reduce bandwidth according to the stations connected.
Unfortunately, with EHT this is longer be sufficient, at
least not for all hardware. EHT requires that non-AP STAs
that are connected to an AP with a lower bandwidth than it
(the AP) advertises (e.g. 160 MHz STA connected to 320 MHz
AP) still be able to receive downlink OFDMA and respond to
trigger frames for uplink OFDMA that specify the position
and bandwidth for the non-AP STA relative to the channel
the AP is using. Therefore, they need to be aware of this,
and at least for some hardware (e.g. Intel) this awareness
is in the hardware. As a result, use of the "same" channel
may need to be split over two channel contexts where they
differ by the AP being used.
As a first step, introduce a concept of a channel request
('chanreq') for each interface, to control the context it
requests. This step does nothing but reorganise the code,
so that later the AP's chandef can be added to the request
in order to handle the EHT case described above.
Link: https://msgid.link/20240129194108.2e88e48bd2e9.I4256183debe975c5ed71621611206fdbb69ba330@changeid
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2024-01-29 19:34:40 +01:00
|
|
|
|
2024-01-29 19:34:38 +01:00
|
|
|
|
2012-07-26 17:24:39 +02:00
|
|
|
|
2024-01-29 19:34:38 +01:00
|
|
|
|
wifi: mac80211: introduce 'channel request'
For channel contexts, mac80211 currently uses the cfg80211
chandef struct (control channel, center freq(s), width) to
define towards drivers and internally how these behave. In
fact, there are _two_ such structs used, where the min_def
can reduce bandwidth according to the stations connected.
Unfortunately, with EHT this is longer be sufficient, at
least not for all hardware. EHT requires that non-AP STAs
that are connected to an AP with a lower bandwidth than it
(the AP) advertises (e.g. 160 MHz STA connected to 320 MHz
AP) still be able to receive downlink OFDMA and respond to
trigger frames for uplink OFDMA that specify the position
and bandwidth for the non-AP STA relative to the channel
the AP is using. Therefore, they need to be aware of this,
and at least for some hardware (e.g. Intel) this awareness
is in the hardware. As a result, use of the "same" channel
may need to be split over two channel contexts where they
differ by the AP being used.
As a first step, introduce a concept of a channel request
('chanreq') for each interface, to control the context it
requests. This step does nothing but reorganise the code,
so that later the AP's chandef can be added to the request
in order to handle the EHT case described above.
Link: https://msgid.link/20240129194108.2e88e48bd2e9.I4256183debe975c5ed71621611206fdbb69ba330@changeid
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2024-01-29 19:34:40 +01:00
|
|
|
|
2024-10-09 10:25:48 +02:00
|
|
|
|
2024-01-29 19:34:38 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
wifi: mac80211: introduce 'channel request'
For channel contexts, mac80211 currently uses the cfg80211
chandef struct (control channel, center freq(s), width) to
define towards drivers and internally how these behave. In
fact, there are _two_ such structs used, where the min_def
can reduce bandwidth according to the stations connected.
Unfortunately, with EHT this is longer be sufficient, at
least not for all hardware. EHT requires that non-AP STAs
that are connected to an AP with a lower bandwidth than it
(the AP) advertises (e.g. 160 MHz STA connected to 320 MHz
AP) still be able to receive downlink OFDMA and respond to
trigger frames for uplink OFDMA that specify the position
and bandwidth for the non-AP STA relative to the channel
the AP is using. Therefore, they need to be aware of this,
and at least for some hardware (e.g. Intel) this awareness
is in the hardware. As a result, use of the "same" channel
may need to be split over two channel contexts where they
differ by the AP being used.
As a first step, introduce a concept of a channel request
('chanreq') for each interface, to control the context it
requests. This step does nothing but reorganise the code,
so that later the AP's chandef can be added to the request
in order to handle the EHT case described above.
Link: https://msgid.link/20240129194108.2e88e48bd2e9.I4256183debe975c5ed71621611206fdbb69ba330@changeid
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2024-01-29 19:34:40 +01:00
|
|
|
|
2024-01-29 19:34:38 +01:00
|
|
|
|
2012-06-06 08:18:22 +02:00
|
|
|
|
|
|
|
|
|
2021-07-02 19:44:08 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-06-01 12:55:14 +03:00
|
|
|
|
|
|
|
|
|
2011-11-10 11:28:57 +02:00
|
|
|
|
2012-08-06 14:26:16 +03:00
|
|
|
|
2011-11-10 11:28:57 +02:00
|
|
|
|
|
|
|
|
|
2012-08-22 14:21:07 +05:30
|
|
|
|
2011-11-10 11:28:57 +02:00
|
|
|
|
2022-06-01 12:55:14 +03:00
|
|
|
|
2011-11-10 11:28:57 +02:00
|
|
|
|
2012-08-06 14:26:16 +03:00
|
|
|
|
2011-11-10 11:28:57 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-08-06 14:26:16 +03:00
|
|
|
|
|
|
|
|
|
2011-11-10 11:28:57 +02:00
|
|
|
|
2014-06-05 14:21:36 +02:00
|
|
|
|
2020-08-11 10:01:04 +02:00
|
|
|
|
2014-06-05 14:21:36 +02:00
|
|
|
|
2020-08-11 10:01:04 +02:00
|
|
|
|
2021-07-02 19:44:08 +02:00
|
|
|
|
|
|
|
|
|
2014-06-05 14:21:36 +02:00
|
|
|
|
2022-06-01 12:55:14 +03:00
|
|
|
|
2012-08-06 14:26:16 +03:00
|
|
|
|
|
|
|
|
|
2011-11-10 11:28:57 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-09-11 00:05:31 +00:00
|
|
|
|
2022-06-01 12:55:14 +03:00
|
|
|
|
|
|
|
|
|
2024-01-29 19:57:39 +01:00
|
|
|
|
|
|
|
|
|
2020-09-11 00:05:31 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-07-27 10:40:57 -07:00
|
|
|
|
|
|
|
|
|
2020-09-11 00:05:31 +00:00
|
|
|
|
2022-06-01 12:55:14 +03:00
|
|
|
|
2020-09-11 00:05:31 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-06-01 12:55:14 +03:00
|
|
|
|
2020-09-11 00:05:31 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-07-27 10:40:57 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-01-29 19:57:39 +01:00
|
|
|
|
|
|
|
|
|
2020-09-11 00:05:31 +00:00
|
|
|
|
|
|
|
|
|
2020-09-11 00:33:01 +00:00
|
|
|
|
|
|
|
|
|
2022-06-01 12:55:14 +03:00
|
|
|
|
|
|
|
|
|
2024-01-29 19:57:30 +01:00
|
|
|
|
|
|
|
|
|
2020-09-11 00:33:01 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-07-27 10:40:57 -07:00
|
|
|
|
|
|
|
|
|
2020-09-11 00:33:01 +00:00
|
|
|
|
2022-06-01 12:55:14 +03:00
|
|
|
|
2020-09-11 00:33:01 +00:00
|
|
|
|
2023-07-27 10:40:57 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-01-29 19:57:30 +01:00
|
|
|
|
|
|
|
|
|
2020-09-11 00:33:01 +00:00
|
|
|
|
|
|
|
|
|
2025-07-17 17:42:03 +10:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-10-03 20:19:20 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-06-01 12:55:14 +03:00
|
|
|
|
|
|
|
|
|
2018-10-03 20:19:20 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-12-15 11:03:24 +02:00
|
|
|
|
|
|
|
|
|
2018-10-03 20:19:20 -07:00
|
|
|
|
2022-06-01 12:55:14 +03:00
|
|
|
|
2018-10-03 20:19:20 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-06-01 12:55:14 +03:00
|
|
|
|
2018-10-03 20:19:20 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-02-24 12:54:58 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-11-24 01:25:00 +08:00
|
|
|
|
2022-02-24 12:54:58 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-03-23 04:38:01 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-07-21 11:25:22 -07:00
|
|
|
|
2023-03-23 04:38:01 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-04-15 14:42:18 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-05-29 10:25:08 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-04-15 14:42:18 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-05-29 10:25:08 +02:00
|
|
|
|
|
|
|
|
|
2026-04-15 14:42:18 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-04 12:11:26 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-12-19 02:03:33 +01:00
|
|
|
|
2022-02-24 12:54:58 +01:00
|
|
|
|
2023-03-23 04:38:01 -07:00
|
|
|
|
2007-12-19 02:03:33 +01:00
|
|
|
|
|
|
|
|
|
2012-02-13 15:17:18 +01:00
|
|
|
|
2023-06-04 12:11:26 +03:00
|
|
|
|
2022-06-17 22:36:37 +02:00
|
|
|
|
2007-12-19 02:03:33 +01:00
|
|
|
|
2022-06-01 12:55:14 +03:00
|
|
|
|
2007-12-19 02:03:33 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-02-13 15:17:18 +01:00
|
|
|
|
2007-12-19 02:03:33 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-02-24 12:54:58 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-03-23 04:38:01 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-02-24 12:54:58 +01:00
|
|
|
|
|
|
|
|
|
2007-12-19 02:03:33 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-03-23 04:38:01 -07:00
|
|
|
|
2007-12-19 02:03:33 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-02-24 12:54:58 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-03-23 04:38:01 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-02-24 12:55:00 +01:00
|
|
|
|
2025-05-30 09:39:40 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-02-24 12:54:58 +01:00
|
|
|
|
2007-12-19 02:03:33 +01:00
|
|
|
|
2014-06-05 14:21:36 +02:00
|
|
|
|
2020-08-11 10:01:04 +02:00
|
|
|
|
|
|
|
|
|
2014-06-05 14:21:36 +02:00
|
|
|
|
2020-08-11 10:01:04 +02:00
|
|
|
|
2021-07-02 19:44:08 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-06-05 14:21:36 +02:00
|
|
|
|
|
|
|
|
|
2007-12-19 02:03:33 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-02-13 15:17:18 +01:00
|
|
|
|
2022-06-01 12:55:14 +03:00
|
|
|
|
2019-07-03 00:29:47 +02:00
|
|
|
|
|
|
|
|
|
2012-02-13 15:17:18 +01:00
|
|
|
|
2019-07-03 00:29:47 +02:00
|
|
|
|
2012-02-13 15:17:18 +01:00
|
|
|
|
2023-06-04 12:11:26 +03:00
|
|
|
|
2010-02-05 11:45:06 +01:00
|
|
|
|
2018-10-03 20:19:20 -07:00
|
|
|
|
2022-06-01 12:55:14 +03:00
|
|
|
|
2018-10-03 20:19:20 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-06-01 12:55:14 +03:00
|
|
|
|
|
|
|
|
|
2018-10-03 20:19:20 -07:00
|
|
|
|
2019-07-03 00:29:47 +02:00
|
|
|
|
|
|
|
|
|
2018-10-03 20:19:20 -07:00
|
|
|
|
2019-07-03 00:29:47 +02:00
|
|
|
|
2018-10-03 20:19:20 -07:00
|
|
|
|
2023-06-04 12:11:26 +03:00
|
|
|
|
2018-10-03 20:19:20 -07:00
|
|
|
|
|
|
|
|
|
2022-06-01 12:55:14 +03:00
|
|
|
|
2022-05-16 15:00:15 +02:00
|
|
|
|
2007-12-19 02:03:33 +01:00
|
|
|
|
2012-02-13 15:17:18 +01:00
|
|
|
|
|
|
|
|
|
2007-12-19 02:03:33 +01:00
|
|
|
|
2026-04-15 14:42:18 +02:00
|
|
|
|
|
|
|
|
|
2023-06-04 12:11:26 +03:00
|
|
|
|
|
|
|
|
|
2007-12-19 02:03:33 +01:00
|
|
|
|
|
|
|
|
|
2024-02-27 09:52:51 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-05-15 23:31:21 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-02-27 09:52:51 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-02-13 15:17:18 +01:00
|
|
|
|
|
|
|
|
|
2007-12-19 02:03:33 +01:00
|
|
|
|
2012-02-13 15:17:18 +01:00
|
|
|
|
mac80211: fix iflist_mtx/mtx locking in radar detection
The scan code creates an iflist_mtx -> mtx locking dependency,
and a few other places, notably radar detection, were creating
the opposite dependency, causing lockdep to complain. As scan
and radar detection are mutually exclusive, the deadlock can't
really happen in practice, but it's still bad form.
A similar issue exists in the monitor mode code, but this is
only used by channel-context drivers right now and those have
to have hardware scan, so that also can't happen.
Still, fix these issues by making some of the channel context
code require the mtx to be held rather than acquiring it, thus
allowing the monitor/radar callers to keep the iflist_mtx->mtx
lock ordering.
While at it, also fix access to the local->scanning variable
in the radar code, and document that radar_detect_enabled is
now properly protected by the mtx.
All this would now introduce an ABBA deadlock between the DFS
work cancelling and local->mtx, so change the locking there a
bit to not need to use cancel_delayed_work_sync() but be able
to just use cancel_delayed_work(). The work is also safely
stopped/removed when the interface is stopped, so no extra
changes are needed.
Reported-by: Kalle Valo <kvalo@qca.qualcomm.com>
Tested-by: Simon Wunderlich <sw@simonwunderlich.de>
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2013-12-18 09:43:33 +01:00
|
|
|
|
2007-12-19 02:03:33 +01:00
|
|
|
|
2011-11-04 11:18:11 +01:00
|
|
|
|
2023-01-30 16:12:27 -08:00
|
|
|
|
2012-02-13 15:17:18 +01:00
|
|
|
|
|
|
|
|
|
2014-11-13 11:23:53 +01:00
|
|
|
|
2019-05-28 13:49:48 +02:00
|
|
|
|
2020-07-09 08:16:21 +05:30
|
|
|
|
2020-04-25 18:57:12 +03:00
|
|
|
|
mac80211: Restore vif beacon interval if start ap fails
The starting of AP interface can fail due to invalid
beacon interval, which does not match the minimum gcd
requirement set by the wifi driver. In such case, the
beacon interval of that interface gets updated with
that invalid beacon interval.
The next time that interface is brought up in AP mode,
an interface combination check is performed and the
beacon interval is taken from the previously set value.
In a case where an invalid beacon interval, i.e. a beacon
interval value which does not satisfy the minimum gcd criteria
set by the driver, is set, all the subsequent trials to
bring that interface in AP mode will fail, even if the
subsequent trials have a valid beacon interval.
To avoid this, in case of a failure in bringing up an
interface in AP mode due to interface combination error,
the interface beacon interval which is stored in bss
conf, needs to be restored with the last working value
of beacon interval.
Tested on ath10k using WCN3990.
Cc: stable@vger.kernel.org
Fixes: 0c317a02ca98 ("cfg80211: support virtual interfaces with different beacon intervals")
Signed-off-by: Rakesh Pillai <pillair@codeaurora.org>
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2019-02-15 14:16:02 +05:30
|
|
|
|
2022-06-01 12:55:14 +03:00
|
|
|
|
2022-06-17 22:36:37 +02:00
|
|
|
|
|
|
|
|
|
2026-04-28 11:25:37 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-07-17 17:42:04 +10:00
|
|
|
|
2022-06-17 22:36:37 +02:00
|
|
|
|
2023-08-28 14:00:05 +02:00
|
|
|
|
|
|
|
|
|
2022-06-17 22:36:37 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-07-29 13:22:52 +02:00
|
|
|
|
2022-06-01 12:55:14 +03:00
|
|
|
|
2007-12-19 02:03:33 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-06-01 12:55:14 +03:00
|
|
|
|
2017-06-10 13:52:45 +03:00
|
|
|
|
2022-06-01 12:55:14 +03:00
|
|
|
|
2012-09-11 14:34:12 +02:00
|
|
|
|
2022-06-01 12:55:14 +03:00
|
|
|
|
|
|
|
|
|
2016-10-21 14:25:14 +02:00
|
|
|
|
2023-02-18 01:49:25 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-10-05 14:54:45 -07:00
|
|
|
|
2023-02-18 01:49:25 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-10-05 14:54:45 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-04-15 14:42:13 +02:00
|
|
|
|
2022-06-01 12:55:14 +03:00
|
|
|
|
|
|
|
|
|
2026-04-15 14:42:13 +02:00
|
|
|
|
2020-01-31 13:12:55 +02:00
|
|
|
|
2022-06-01 12:55:14 +03:00
|
|
|
|
2026-04-15 14:42:13 +02:00
|
|
|
|
2020-01-31 13:12:55 +02:00
|
|
|
|
2020-07-09 08:16:21 +05:30
|
|
|
|
|
|
|
|
|
2022-04-13 21:58:14 +05:30
|
|
|
|
2020-07-09 08:16:21 +05:30
|
|
|
|
2020-01-31 13:12:55 +02:00
|
|
|
|
2018-08-31 11:31:15 +03:00
|
|
|
|
2022-10-05 14:54:46 -07:00
|
|
|
|
2023-02-18 01:49:25 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-10-05 14:54:46 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-01-30 16:12:27 -08:00
|
|
|
|
2023-04-10 13:03:32 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-02-18 01:48:59 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-05-15 11:13:18 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-05-05 20:58:36 +05:30
|
|
|
|
2026-04-15 14:42:13 +02:00
|
|
|
|
2025-05-05 20:58:36 +05:30
|
|
|
|
2023-02-18 01:48:59 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-01-30 16:12:27 -08:00
|
|
|
|
|
|
|
|
|
2026-04-15 14:42:13 +02:00
|
|
|
|
2026-04-28 11:25:39 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-01-30 16:21:07 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-04-28 11:25:39 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-01-30 16:21:07 +01:00
|
|
|
|
|
|
|
|
|
2021-09-15 19:54:35 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-11-08 09:22:27 +01:00
|
|
|
|
2022-06-01 12:55:14 +03:00
|
|
|
|
2021-09-15 19:54:35 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
wifi: mac80211: introduce 'channel request'
For channel contexts, mac80211 currently uses the cfg80211
chandef struct (control channel, center freq(s), width) to
define towards drivers and internally how these behave. In
fact, there are _two_ such structs used, where the min_def
can reduce bandwidth according to the stations connected.
Unfortunately, with EHT this is longer be sufficient, at
least not for all hardware. EHT requires that non-AP STAs
that are connected to an AP with a lower bandwidth than it
(the AP) advertises (e.g. 160 MHz STA connected to 320 MHz
AP) still be able to receive downlink OFDMA and respond to
trigger frames for uplink OFDMA that specify the position
and bandwidth for the non-AP STA relative to the channel
the AP is using. Therefore, they need to be aware of this,
and at least for some hardware (e.g. Intel) this awareness
is in the hardware. As a result, use of the "same" channel
may need to be split over two channel contexts where they
differ by the AP being used.
As a first step, introduce a concept of a channel request
('chanreq') for each interface, to control the context it
requests. This step does nothing but reorganise the code,
so that later the AP's chandef can be added to the request
in order to handle the EHT case described above.
Link: https://msgid.link/20240129194108.2e88e48bd2e9.I4256183debe975c5ed71621611206fdbb69ba330@changeid
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2024-01-29 19:34:40 +01:00
|
|
|
|
2022-05-30 18:35:23 +02:00
|
|
|
|
2014-03-05 13:14:08 +01:00
|
|
|
|
2022-06-01 12:55:14 +03:00
|
|
|
|
mac80211: Restore vif beacon interval if start ap fails
The starting of AP interface can fail due to invalid
beacon interval, which does not match the minimum gcd
requirement set by the wifi driver. In such case, the
beacon interval of that interface gets updated with
that invalid beacon interval.
The next time that interface is brought up in AP mode,
an interface combination check is performed and the
beacon interval is taken from the previously set value.
In a case where an invalid beacon interval, i.e. a beacon
interval value which does not satisfy the minimum gcd criteria
set by the driver, is set, all the subsequent trials to
bring that interface in AP mode will fail, even if the
subsequent trials have a valid beacon interval.
To avoid this, in case of a failure in bringing up an
interface in AP mode due to interface combination error,
the interface beacon interval which is stored in bss
conf, needs to be restored with the last working value
of beacon interval.
Tested on ath10k using WCN3990.
Cc: stable@vger.kernel.org
Fixes: 0c317a02ca98 ("cfg80211: support virtual interfaces with different beacon intervals")
Signed-off-by: Rakesh Pillai <pillair@codeaurora.org>
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2019-02-15 14:16:02 +05:30
|
|
|
|
2022-06-01 12:55:14 +03:00
|
|
|
|
2012-05-16 23:50:18 +02:00
|
|
|
|
mac80211: Restore vif beacon interval if start ap fails
The starting of AP interface can fail due to invalid
beacon interval, which does not match the minimum gcd
requirement set by the wifi driver. In such case, the
beacon interval of that interface gets updated with
that invalid beacon interval.
The next time that interface is brought up in AP mode,
an interface combination check is performed and the
beacon interval is taken from the previously set value.
In a case where an invalid beacon interval, i.e. a beacon
interval value which does not satisfy the minimum gcd criteria
set by the driver, is set, all the subsequent trials to
bring that interface in AP mode will fail, even if the
subsequent trials have a valid beacon interval.
To avoid this, in case of a failure in bringing up an
interface in AP mode due to interface combination error,
the interface beacon interval which is stored in bss
conf, needs to be restored with the last working value
of beacon interval.
Tested on ath10k using WCN3990.
Cc: stable@vger.kernel.org
Fixes: 0c317a02ca98 ("cfg80211: support virtual interfaces with different beacon intervals")
Signed-off-by: Rakesh Pillai <pillair@codeaurora.org>
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2019-02-15 14:16:02 +05:30
|
|
|
|
2012-05-16 23:50:18 +02:00
|
|
|
|
2011-11-04 11:18:11 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-03-26 12:52:51 -05:00
|
|
|
|
|
|
|
|
|
2020-03-12 10:10:54 +01:00
|
|
|
|
|
|
|
|
|
2013-03-24 14:23:27 +02:00
|
|
|
|
2011-11-04 11:18:11 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-03-26 12:52:51 -05:00
|
|
|
|
|
|
|
|
|
2020-03-12 10:10:54 +01:00
|
|
|
|
|
|
|
|
|
2011-11-04 11:18:11 +01:00
|
|
|
|
|
|
|
|
|
2022-06-01 12:55:14 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-07-17 17:42:03 +10:00
|
|
|
|
|
|
|
|
|
2012-02-13 15:17:18 +01:00
|
|
|
|
wifi: mac80211: move interface config to new struct
We'll use bss_conf for per-link configuration later, so
move out all the non-link-specific data out into a new
struct ieee80211_vif_cfg used in the vif.
Some adjustments were done with the following spatch:
@@
expression sdata;
struct ieee80211_vif *vifp;
identifier var = { assoc, ibss_joined, aid, arp_addr_list, arp_addr_cnt, ssid, ssid_len, s1g, ibss_creator };
@@
(
-sdata->vif.bss_conf.var
+sdata->vif.cfg.var
|
-vifp->bss_conf.var
+vifp->cfg.var
)
@bss_conf@
struct ieee80211_bss_conf *bss_conf;
identifier var = { assoc, ibss_joined, aid, arp_addr_list, arp_addr_cnt, ssid, ssid_len, s1g, ibss_creator };
@@
-bss_conf->var
+vif_cfg->var
(though more manual fixups were needed, e.g. replacing
"vif_cfg->" by "vif->cfg." in many files.)
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2022-05-10 17:05:04 +02:00
|
|
|
|
2012-02-13 15:17:18 +01:00
|
|
|
|
wifi: mac80211: move interface config to new struct
We'll use bss_conf for per-link configuration later, so
move out all the non-link-specific data out into a new
struct ieee80211_vif_cfg used in the vif.
Some adjustments were done with the following spatch:
@@
expression sdata;
struct ieee80211_vif *vifp;
identifier var = { assoc, ibss_joined, aid, arp_addr_list, arp_addr_cnt, ssid, ssid_len, s1g, ibss_creator };
@@
(
-sdata->vif.bss_conf.var
+sdata->vif.cfg.var
|
-vifp->bss_conf.var
+vifp->cfg.var
)
@bss_conf@
struct ieee80211_bss_conf *bss_conf;
identifier var = { assoc, ibss_joined, aid, arp_addr_list, arp_addr_cnt, ssid, ssid_len, s1g, ibss_creator };
@@
-bss_conf->var
+vif_cfg->var
(though more manual fixups were needed, e.g. replacing
"vif_cfg->" by "vif->cfg." in many files.)
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2022-05-10 17:05:04 +02:00
|
|
|
|
2012-02-13 15:17:18 +01:00
|
|
|
|
2022-06-01 12:55:14 +03:00
|
|
|
|
2012-02-13 15:17:18 +01:00
|
|
|
|
|
|
|
|
|
2022-06-01 12:55:14 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-03-21 15:47:56 +01:00
|
|
|
|
|
|
|
|
|
2022-06-01 12:55:14 +03:00
|
|
|
|
2013-03-21 15:47:56 +01:00
|
|
|
|
2012-11-14 15:21:17 +01:00
|
|
|
|
2020-04-25 18:57:12 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-10-03 15:04:18 -07:00
|
|
|
|
2022-06-01 12:55:14 +03:00
|
|
|
|
2020-10-03 15:04:18 -07:00
|
|
|
|
2023-06-04 12:11:26 +03:00
|
|
|
|
|
|
|
|
|
2020-09-11 00:05:31 +00:00
|
|
|
|
|
|
|
|
|
2012-02-13 15:17:18 +01:00
|
|
|
|
2023-07-27 10:40:57 -07:00
|
|
|
|
2024-01-29 19:57:39 +01:00
|
|
|
|
2023-07-27 10:40:57 -07:00
|
|
|
|
|
|
|
|
|
2020-09-11 00:05:31 +00:00
|
|
|
|
2023-07-27 10:40:57 -07:00
|
|
|
|
|
|
|
|
|
2024-01-29 19:57:30 +01:00
|
|
|
|
2023-07-27 10:40:57 -07:00
|
|
|
|
|
|
|
|
|
2020-09-11 00:33:01 +00:00
|
|
|
|
2025-07-17 17:42:03 +10:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-06-29 12:22:24 +03:00
|
|
|
|
2012-10-19 15:44:42 +02:00
|
|
|
|
2022-06-01 12:55:14 +03:00
|
|
|
|
2013-11-21 18:19:50 +01:00
|
|
|
|
2012-10-19 15:44:42 +02:00
|
|
|
|
|
|
|
|
|
2022-06-01 12:55:14 +03:00
|
|
|
|
2024-04-09 15:10:17 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-09-11 00:05:31 +00:00
|
|
|
|
2012-10-19 15:44:42 +02:00
|
|
|
|
|
|
|
|
|
2025-07-17 17:42:04 +10:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-06-01 12:55:14 +03:00
|
|
|
|
2022-06-17 22:36:37 +02:00
|
|
|
|
2012-02-13 15:17:18 +01:00
|
|
|
|
2024-02-27 09:52:51 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-04-03 10:24:00 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-11-04 11:18:11 +01:00
|
|
|
|
2020-09-11 00:05:31 +00:00
|
|
|
|
|
|
|
|
|
2022-06-01 12:55:14 +03:00
|
|
|
|
2021-12-20 10:22:40 +01:00
|
|
|
|
2020-09-11 00:05:31 +00:00
|
|
|
|
2007-12-19 02:03:33 +01:00
|
|
|
|
|
|
|
|
|
2012-02-13 15:17:18 +01:00
|
|
|
|
2023-09-25 08:56:38 +02:00
|
|
|
|
2023-07-27 10:40:58 -07:00
|
|
|
|
2007-12-19 02:03:33 +01:00
|
|
|
|
2022-06-01 12:55:14 +03:00
|
|
|
|
2022-06-17 22:36:37 +02:00
|
|
|
|
2023-07-27 10:40:58 -07:00
|
|
|
|
2007-12-19 02:03:33 +01:00
|
|
|
|
2012-02-13 15:17:18 +01:00
|
|
|
|
2022-06-17 22:36:37 +02:00
|
|
|
|
2023-06-04 12:11:26 +03:00
|
|
|
|
2007-12-19 02:03:33 +01:00
|
|
|
|
2023-08-29 12:18:56 +02:00
|
|
|
|
2008-07-29 13:22:52 +02:00
|
|
|
|
2023-07-27 10:40:58 -07:00
|
|
|
|
2022-06-17 22:36:37 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-07-02 19:44:08 +02:00
|
|
|
|
2013-07-11 16:09:06 +02:00
|
|
|
|
|
|
|
|
|
2022-06-01 12:55:14 +03:00
|
|
|
|
2013-07-11 16:09:06 +02:00
|
|
|
|
|
|
|
|
|
2022-06-17 22:36:37 +02:00
|
|
|
|
2007-12-19 02:03:33 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-07-27 10:40:58 -07:00
|
|
|
|
2023-06-04 12:11:26 +03:00
|
|
|
|
2012-02-13 15:17:18 +01:00
|
|
|
|
|
|
|
|
|
2022-04-13 21:58:15 +05:30
|
|
|
|
2023-07-27 10:41:00 -07:00
|
|
|
|
2024-01-29 19:57:39 +01:00
|
|
|
|
2023-07-27 10:41:00 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-01-29 19:57:30 +01:00
|
|
|
|
2023-07-27 10:41:00 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-07-17 17:42:03 +10:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-07-27 10:40:58 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-04 12:11:26 +03:00
|
|
|
|
2022-04-13 21:58:15 +05:30
|
|
|
|
|
|
|
|
|
2023-06-04 12:11:26 +03:00
|
|
|
|
2012-02-13 15:17:18 +01:00
|
|
|
|
2007-12-19 02:03:33 +01:00
|
|
|
|
|
|
|
|
|
2022-06-01 12:55:14 +03:00
|
|
|
|
2022-05-16 12:57:32 +02:00
|
|
|
|
2022-06-01 12:55:14 +03:00
|
|
|
|
2022-05-16 12:57:32 +02:00
|
|
|
|
|
|
|
|
|
2022-06-01 12:55:14 +03:00
|
|
|
|
2023-03-23 04:38:01 -07:00
|
|
|
|
2022-06-01 12:55:14 +03:00
|
|
|
|
|
|
|
|
|
2022-05-16 12:57:32 +02:00
|
|
|
|
|
|
|
|
|
2022-04-14 16:50:57 +02:00
|
|
|
|
|
|
|
|
|
2007-12-19 02:03:33 +01:00
|
|
|
|
2012-10-25 19:02:42 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-09-11 00:05:31 +00:00
|
|
|
|
2020-09-11 00:33:01 +00:00
|
|
|
|
2025-07-17 17:42:03 +10:00
|
|
|
|
2013-11-06 13:55:51 +01:00
|
|
|
|
2022-06-17 22:36:37 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-05-05 15:12:16 +02:00
|
|
|
|
2024-02-27 09:52:50 +05:30
|
|
|
|
2007-12-19 02:03:33 +01:00
|
|
|
|
2023-08-28 14:00:05 +02:00
|
|
|
|
2014-01-29 07:56:21 +01:00
|
|
|
|
2022-06-01 12:55:14 +03:00
|
|
|
|
2012-10-25 19:02:42 +02:00
|
|
|
|
2007-12-19 02:03:33 +01:00
|
|
|
|
2022-06-01 12:55:14 +03:00
|
|
|
|
2022-05-16 15:00:15 +02:00
|
|
|
|
2022-06-01 12:55:14 +03:00
|
|
|
|
2020-09-11 00:05:31 +00:00
|
|
|
|
2020-09-11 00:33:01 +00:00
|
|
|
|
2022-06-01 12:55:14 +03:00
|
|
|
|
2020-09-11 00:33:01 +00:00
|
|
|
|
2025-07-17 17:42:03 +10:00
|
|
|
|
|
|
|
|
|
2007-12-19 02:03:33 +01:00
|
|
|
|
2023-05-04 16:04:41 +08:00
|
|
|
|
2022-06-01 12:55:14 +03:00
|
|
|
|
2023-05-04 16:04:41 +08:00
|
|
|
|
2024-06-12 14:28:35 +02:00
|
|
|
|
2014-06-13 16:30:07 +03:00
|
|
|
|
2022-06-01 12:55:14 +03:00
|
|
|
|
2013-11-21 18:19:53 +01:00
|
|
|
|
2012-10-25 19:02:42 +02:00
|
|
|
|
2012-04-03 10:24:00 +02:00
|
|
|
|
|
|
|
|
|
2024-02-27 09:52:51 +05:30
|
|
|
|
2024-04-09 15:10:17 +05:30
|
|
|
|
2024-02-27 09:52:51 +05:30
|
|
|
|
2024-04-09 15:10:17 +05:30
|
|
|
|
|
|
|
|
|
2012-04-03 10:24:00 +02:00
|
|
|
|
2012-10-25 19:02:42 +02:00
|
|
|
|
2022-06-01 12:55:14 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-07-17 17:42:03 +10:00
|
|
|
|
2012-10-25 19:02:42 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-09-11 00:05:31 +00:00
|
|
|
|
|
|
|
|
|
2020-09-11 00:33:01 +00:00
|
|
|
|
|
|
|
|
|
2025-07-17 17:42:03 +10:00
|
|
|
|
|
|
|
|
|
2012-02-13 15:17:18 +01:00
|
|
|
|
2026-05-05 15:12:16 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-06-01 12:55:14 +03:00
|
|
|
|
|
|
|
|
|
2018-10-03 20:19:20 -07:00
|
|
|
|
2022-12-21 10:56:16 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-09-24 18:30:14 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-12-21 10:56:16 -08:00
|
|
|
|
2024-12-24 19:27:29 +02:00
|
|
|
|
2024-02-27 09:52:50 +05:30
|
|
|
|
2025-04-08 11:45:00 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-06-01 12:55:14 +03:00
|
|
|
|
2020-04-25 18:57:12 +03:00
|
|
|
|
wifi: mac80211: move interface config to new struct
We'll use bss_conf for per-link configuration later, so
move out all the non-link-specific data out into a new
struct ieee80211_vif_cfg used in the vif.
Some adjustments were done with the following spatch:
@@
expression sdata;
struct ieee80211_vif *vifp;
identifier var = { assoc, ibss_joined, aid, arp_addr_list, arp_addr_cnt, ssid, ssid_len, s1g, ibss_creator };
@@
(
-sdata->vif.bss_conf.var
+sdata->vif.cfg.var
|
-vifp->bss_conf.var
+vifp->cfg.var
)
@bss_conf@
struct ieee80211_bss_conf *bss_conf;
identifier var = { assoc, ibss_joined, aid, arp_addr_list, arp_addr_cnt, ssid, ssid_len, s1g, ibss_creator };
@@
-bss_conf->var
+vif_cfg->var
(though more manual fixups were needed, e.g. replacing
"vif_cfg->" by "vif->cfg." in many files.)
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2022-05-10 17:05:04 +02:00
|
|
|
|
2025-07-17 17:42:03 +10:00
|
|
|
|
2012-12-14 14:06:28 +01:00
|
|
|
|
2026-05-05 15:12:16 +02:00
|
|
|
|
2012-02-13 15:17:18 +01:00
|
|
|
|
2026-03-03 15:03:39 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-09-06 12:14:25 +05:30
|
|
|
|
wifi: mac80211: introduce 'channel request'
For channel contexts, mac80211 currently uses the cfg80211
chandef struct (control channel, center freq(s), width) to
define towards drivers and internally how these behave. In
fact, there are _two_ such structs used, where the min_def
can reduce bandwidth according to the stations connected.
Unfortunately, with EHT this is longer be sufficient, at
least not for all hardware. EHT requires that non-AP STAs
that are connected to an AP with a lower bandwidth than it
(the AP) advertises (e.g. 160 MHz STA connected to 320 MHz
AP) still be able to receive downlink OFDMA and respond to
trigger frames for uplink OFDMA that specify the position
and bandwidth for the non-AP STA relative to the channel
the AP is using. Therefore, they need to be aware of this,
and at least for some hardware (e.g. Intel) this awareness
is in the hardware. As a result, use of the "same" channel
may need to be split over two channel contexts where they
differ by the AP being used.
As a first step, introduce a concept of a channel request
('chanreq') for each interface, to control the context it
requests. This step does nothing but reorganise the code,
so that later the AP's chandef can be added to the request
in order to handle the EHT case described above.
Link: https://msgid.link/20240129194108.2e88e48bd2e9.I4256183debe975c5ed71621611206fdbb69ba330@changeid
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2024-01-29 19:34:40 +01:00
|
|
|
|
2026-01-30 09:25:11 +05:30
|
|
|
|
2013-11-06 13:55:51 +01:00
|
|
|
|
|
|
|
|
|
2024-09-06 12:14:25 +05:30
|
|
|
|
2013-06-11 10:44:39 +02:00
|
|
|
|
|
|
|
|
|
2022-06-29 12:22:24 +03:00
|
|
|
|
2012-10-19 15:44:42 +02:00
|
|
|
|
2012-10-25 19:02:42 +02:00
|
|
|
|
|
|
|
|
|
2016-08-02 11:13:41 +02:00
|
|
|
|
2012-10-25 19:02:42 +02:00
|
|
|
|
2022-06-01 12:55:14 +03:00
|
|
|
|
|
|
|
|
|
2012-07-26 17:24:39 +02:00
|
|
|
|
2009-04-23 16:13:26 +02:00
|
|
|
|
2007-12-19 02:03:33 +01:00
|
|
|
|
|
|
|
|
|
nl80211/mac80211: support full station state in AP mode
Today, stations are added already associated. That is
inefficient if, for example, the driver has no room
for stations any more because then the station will
go through the entire auth/assoc handshake, only to
be kicked out afterwards.
To address this a bit better, at least with drivers
using the new station state callback, allow hostapd
to add stations in unauthenticated mode, just after
receiving the AUTH frame, before even replying. Thus
if there's no more space at that point, it can send
a negative auth frame back. It still needs to handle
later state transition errors though, of course.
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2012-10-26 17:53:44 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-03-08 18:04:22 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-09-23 10:41:27 +02:00
|
|
|
|
wifi: mac80211: allow rate_control_rate_init() for links
Andrei previously fixed an issue in the client where the NSS
for links other than the primary/assoc/deflink isn't set. The
same issue appears to exist on the AP side, because there's
only a call to rate_control_rate_init() for the deflink, and
not any other links.
Rework the code a bit to do rate_control_rate_init() for links,
even if it really doesn't work with software rate control yet,
it does other things as well.
Also add rate_control_rate_init_all_links() to actually do it
properly when moving to ASSOC state in cfg80211.
Change the explicit call to ieee80211_sta_init_nss() to instead
be rate_control_rate_init() now in the client code, but also
add a call to rate_control_rate_init() when a link is added in
AP mode and the STA is already associated.
This should fix the NSS initialization issue, and perhaps pave
the way for actual software rate scaling a bit, in case anyone
cares in the future, but that of course needs a lot more than
just the init call.
We still need to fix the rate control _update_ as well, and the
sta_rc_update() driver method especially, but that will be in a
different patch.
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: Miri Korenblit <miriam.rachel.korenblit@intel.com>
Link: https://patch.msgid.link/20241007144851.c693274a908f.I0376da02e9f5a30eaa1b5d0d01371ff09506d453@changeid
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2024-10-07 15:00:53 +03:00
|
|
|
|
2015-03-08 18:04:22 +02:00
|
|
|
|
nl80211/mac80211: support full station state in AP mode
Today, stations are added already associated. That is
inefficient if, for example, the driver has no room
for stations any more because then the station will
go through the entire auth/assoc handshake, only to
be kicked out afterwards.
To address this a bit better, at least with drivers
using the new station state callback, allow hostapd
to add stations in unauthenticated mode, just after
receiving the AUTH frame, before even replying. Thus
if there's no more space at that point, it can send
a negative auth frame back. It still needs to handle
later state transition errors though, of course.
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2012-10-26 17:53:44 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-06-17 10:34:54 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-04 12:11:26 +03:00
|
|
|
|
2015-06-17 10:34:54 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-07-01 10:19:34 +09:00
|
|
|
|
2015-06-17 10:34:54 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-01-15 15:31:56 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-06-17 10:34:54 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
wifi: mac80211: fix erroneous errors for STA changes
When e.g. wpa_supplicant sets only the MLD "sta" authorized
state, the code actually applies that change, but then returns
an error to userspace anyway because there were no changes to
the link station, and no link ID was given. However, it's not
incorrect to not have a link ID when wanting to change only
the MLD peer ("sta") state, so the code shouldn't require it.
To fix this, separate the "new_link" argument out into a new
three-state enum, because if modify is called on a link STA
only, it should return an error if no link is given or if it
doesn't exist. For modify on the MLD "sta", not having a link
ID is OK, but if there is one it should be validated.
This seems to not have mattered much as wpa_supplicant just
prints a message and continues, and the authorized state was
already set before this error return. However, in the later
code powersave recalculation etc. will be skipped, so that it
may result in never allowing powersave on MLO connections.
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: Miri Korenblit <miriam.rachel.korenblit@intel.com>
Link: https://msgid.link/20240605135233.48e2b8af07e3.Ib9793c383fcba118c05100e024f4a11a1c3d0e85@changeid
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2024-06-05 13:57:18 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-06-14 13:49:16 +03:00
|
|
|
|
wifi: mac80211: fix erroneous errors for STA changes
When e.g. wpa_supplicant sets only the MLD "sta" authorized
state, the code actually applies that change, but then returns
an error to userspace anyway because there were no changes to
the link station, and no link ID was given. However, it's not
incorrect to not have a link ID when wanting to change only
the MLD peer ("sta") state, so the code shouldn't require it.
To fix this, separate the "new_link" argument out into a new
three-state enum, because if modify is called on a link STA
only, it should return an error if no link is given or if it
doesn't exist. For modify on the MLD "sta", not having a link
ID is OK, but if there is one it should be validated.
This seems to not have mattered much as wpa_supplicant just
prints a message and continues, and the authorized state was
already set before this error return. However, in the later
code powersave recalculation etc. will be skipped, so that it
may result in never allowing powersave on MLO connections.
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: Miri Korenblit <miriam.rachel.korenblit@intel.com>
Link: https://msgid.link/20240605135233.48e2b8af07e3.Ib9793c383fcba118c05100e024f4a11a1c3d0e85@changeid
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2024-06-05 13:57:18 +03:00
|
|
|
|
|
|
|
|
|
2022-06-14 13:49:16 +03:00
|
|
|
|
|
|
|
|
|
2026-03-26 12:14:38 +02:00
|
|
|
|
2022-06-14 13:49:16 +03:00
|
|
|
|
|
|
|
|
|
2022-06-17 22:36:37 +02:00
|
|
|
|
|
|
|
|
|
2022-06-14 13:49:16 +03:00
|
|
|
|
|
|
|
|
|
2023-08-28 14:00:01 +02:00
|
|
|
|
2026-03-26 12:14:38 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
wifi: mac80211: fix erroneous errors for STA changes
When e.g. wpa_supplicant sets only the MLD "sta" authorized
state, the code actually applies that change, but then returns
an error to userspace anyway because there were no changes to
the link station, and no link ID was given. However, it's not
incorrect to not have a link ID when wanting to change only
the MLD peer ("sta") state, so the code shouldn't require it.
To fix this, separate the "new_link" argument out into a new
three-state enum, because if modify is called on a link STA
only, it should return an error if no link is given or if it
doesn't exist. For modify on the MLD "sta", not having a link
ID is OK, but if there is one it should be validated.
This seems to not have mattered much as wpa_supplicant just
prints a message and continues, and the authorized state was
already set before this error return. However, in the later
code powersave recalculation etc. will be skipped, so that it
may result in never allowing powersave on MLO connections.
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: Miri Korenblit <miriam.rachel.korenblit@intel.com>
Link: https://msgid.link/20240605135233.48e2b8af07e3.Ib9793c383fcba118c05100e024f4a11a1c3d0e85@changeid
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2024-06-05 13:57:18 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-01-30 16:21:07 +01:00
|
|
|
|
2025-06-17 18:06:09 +10:00
|
|
|
|
wifi: mac80211: fix erroneous errors for STA changes
When e.g. wpa_supplicant sets only the MLD "sta" authorized
state, the code actually applies that change, but then returns
an error to userspace anyway because there were no changes to
the link station, and no link ID was given. However, it's not
incorrect to not have a link ID when wanting to change only
the MLD peer ("sta") state, so the code shouldn't require it.
To fix this, separate the "new_link" argument out into a new
three-state enum, because if modify is called on a link STA
only, it should return an error if no link is given or if it
doesn't exist. For modify on the MLD "sta", not having a link
ID is OK, but if there is one it should be validated.
This seems to not have mattered much as wpa_supplicant just
prints a message and continues, and the authorized state was
already set before this error return. However, in the later
code powersave recalculation etc. will be skipped, so that it
may result in never allowing powersave on MLO connections.
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: Miri Korenblit <miriam.rachel.korenblit@intel.com>
Link: https://msgid.link/20240605135233.48e2b8af07e3.Ib9793c383fcba118c05100e024f4a11a1c3d0e85@changeid
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2024-06-05 13:57:18 +03:00
|
|
|
|
2022-06-14 13:49:16 +03:00
|
|
|
|
wifi: mac80211: fix erroneous errors for STA changes
When e.g. wpa_supplicant sets only the MLD "sta" authorized
state, the code actually applies that change, but then returns
an error to userspace anyway because there were no changes to
the link station, and no link ID was given. However, it's not
incorrect to not have a link ID when wanting to change only
the MLD peer ("sta") state, so the code shouldn't require it.
To fix this, separate the "new_link" argument out into a new
three-state enum, because if modify is called on a link STA
only, it should return an error if no link is given or if it
doesn't exist. For modify on the MLD "sta", not having a link
ID is OK, but if there is one it should be validated.
This seems to not have mattered much as wpa_supplicant just
prints a message and continues, and the authorized state was
already set before this error return. However, in the later
code powersave recalculation etc. will be skipped, so that it
may result in never allowing powersave on MLO connections.
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: Miri Korenblit <miriam.rachel.korenblit@intel.com>
Link: https://msgid.link/20240605135233.48e2b8af07e3.Ib9793c383fcba118c05100e024f4a11a1c3d0e85@changeid
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2024-06-05 13:57:18 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-07-23 22:08:49 +02:00
|
|
|
|
2022-06-17 22:36:37 +02:00
|
|
|
|
2022-06-14 13:49:16 +03:00
|
|
|
|
|
|
|
|
|
2026-03-26 12:14:38 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-06-14 13:49:16 +03:00
|
|
|
|
|
|
|
|
|
2026-03-26 12:14:38 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-06-14 13:49:16 +03:00
|
|
|
|
wifi: mac80211: fix erroneous errors for STA changes
When e.g. wpa_supplicant sets only the MLD "sta" authorized
state, the code actually applies that change, but then returns
an error to userspace anyway because there were no changes to
the link station, and no link ID was given. However, it's not
incorrect to not have a link ID when wanting to change only
the MLD peer ("sta") state, so the code shouldn't require it.
To fix this, separate the "new_link" argument out into a new
three-state enum, because if modify is called on a link STA
only, it should return an error if no link is given or if it
doesn't exist. For modify on the MLD "sta", not having a link
ID is OK, but if there is one it should be validated.
This seems to not have mattered much as wpa_supplicant just
prints a message and continues, and the authorized state was
already set before this error return. However, in the later
code powersave recalculation etc. will be skipped, so that it
may result in never allowing powersave on MLO connections.
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: Miri Korenblit <miriam.rachel.korenblit@intel.com>
Link: https://msgid.link/20240605135233.48e2b8af07e3.Ib9793c383fcba118c05100e024f4a11a1c3d0e85@changeid
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2024-06-05 13:57:18 +03:00
|
|
|
|
2022-07-18 22:23:53 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-06-14 13:49:16 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-06-05 13:57:19 +03:00
|
|
|
|
|
|
|
|
|
2022-06-14 13:49:16 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-03-26 12:14:38 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-06-14 13:49:16 +03:00
|
|
|
|
2025-03-17 13:31:37 +03:00
|
|
|
|
2026-01-08 14:32:57 +01:00
|
|
|
|
2025-03-17 13:31:37 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-06-14 13:49:16 +03:00
|
|
|
|
|
|
|
|
|
2026-03-26 12:14:38 +02:00
|
|
|
|
2022-06-14 13:49:16 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-03-26 12:14:38 +02:00
|
|
|
|
2023-09-18 14:10:55 +03:00
|
|
|
|
|
|
|
|
|
2022-06-14 13:49:16 +03:00
|
|
|
|
|
|
|
|
|
2026-03-26 12:14:38 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-06-14 13:49:16 +03:00
|
|
|
|
2023-03-01 12:09:31 +02:00
|
|
|
|
2022-06-14 13:49:16 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-01-30 16:21:07 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-06-17 18:06:09 +10:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-04-15 14:42:08 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-11-18 16:07:22 +08:00
|
|
|
|
2022-06-14 13:49:16 +03:00
|
|
|
|
2025-07-03 12:37:57 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-06-14 13:49:16 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-06-05 13:57:19 +03:00
|
|
|
|
2022-06-14 13:49:16 +03:00
|
|
|
|
|
|
|
|
|
2011-12-14 12:35:30 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-12-19 02:03:35 +01:00
|
|
|
|
2008-02-25 16:27:46 +01:00
|
|
|
|
2009-05-11 21:57:56 +03:00
|
|
|
|
2022-07-22 00:07:29 +02:00
|
|
|
|
2008-10-14 16:58:37 +02:00
|
|
|
|
2009-05-11 21:57:56 +03:00
|
|
|
|
|
|
|
|
|
2008-02-25 16:27:47 +01:00
|
|
|
|
2026-01-14 16:48:56 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
nl80211/mac80211: support full station state in AP mode
Today, stations are added already associated. That is
inefficient if, for example, the driver has no room
for stations any more because then the station will
go through the entire auth/assoc handshake, only to
be kicked out afterwards.
To address this a bit better, at least with drivers
using the new station state callback, allow hostapd
to add stations in unauthenticated mode, just after
receiving the AUTH frame, before even replying. Thus
if there's no more space at that point, it can send
a negative auth frame back. It still needs to handle
later state transition errors though, of course.
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2012-10-26 17:53:44 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-02-15 00:48:33 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-12-14 12:35:30 +01:00
|
|
|
|
|
|
|
|
|
2015-03-30 15:09:20 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-09-23 10:41:27 +02:00
|
|
|
|
2021-03-27 04:42:45 +05:30
|
|
|
|
2015-09-23 10:41:27 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-06-11 17:18:19 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-12-14 12:35:30 +01:00
|
|
|
|
2009-05-11 21:57:56 +03:00
|
|
|
|
|
|
|
|
|
2011-09-29 16:04:36 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-05-11 21:57:56 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-10-07 10:40:04 +05:30
|
|
|
|
2009-05-11 21:57:56 +03:00
|
|
|
|
2011-09-29 16:04:36 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-05-11 21:57:56 +03:00
|
|
|
|
2011-04-07 15:08:30 -07:00
|
|
|
|
2011-09-28 14:12:53 +03:00
|
|
|
|
|
|
|
|
|
2011-09-29 16:04:36 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-09-28 14:12:53 +03:00
|
|
|
|
2009-05-11 21:57:56 +03:00
|
|
|
|
2024-01-02 21:35:40 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-11-09 18:50:15 +02:00
|
|
|
|
|
|
|
|
|
2022-06-29 12:01:41 +02:00
|
|
|
|
2014-11-09 18:50:15 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-06-10 20:42:59 +03:00
|
|
|
|
2015-08-15 22:39:46 +03:00
|
|
|
|
2015-06-10 20:42:59 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-09-27 20:56:12 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-08-23 14:37:47 +03:00
|
|
|
|
2026-05-13 17:06:27 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-12-13 15:41:05 +02:00
|
|
|
|
2009-05-24 16:42:30 +02:00
|
|
|
|
|
|
|
|
|
2025-07-25 23:22:19 +10:00
|
|
|
|
|
|
|
|
|
2009-05-24 16:42:30 +02:00
|
|
|
|
2025-07-25 23:22:19 +10:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-05-24 16:42:30 +02:00
|
|
|
|
2025-07-25 23:22:19 +10:00
|
|
|
|
2009-05-24 16:42:30 +02:00
|
|
|
|
2008-02-25 16:27:47 +01:00
|
|
|
|
2012-12-27 17:32:09 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-02-25 16:27:47 +01:00
|
|
|
|
|
|
|
|
|
2007-12-19 02:03:35 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-03-27 10:43:18 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
wifi: mac80211: fix erroneous errors for STA changes
When e.g. wpa_supplicant sets only the MLD "sta" authorized
state, the code actually applies that change, but then returns
an error to userspace anyway because there were no changes to
the link station, and no link ID was given. However, it's not
incorrect to not have a link ID when wanting to change only
the MLD peer ("sta") state, so the code shouldn't require it.
To fix this, separate the "new_link" argument out into a new
three-state enum, because if modify is called on a link STA
only, it should return an error if no link is given or if it
doesn't exist. For modify on the MLD "sta", not having a link
ID is OK, but if there is one it should be validated.
This seems to not have mattered much as wpa_supplicant just
prints a message and continues, and the authorized state was
already set before this error return. However, in the later
code powersave recalculation etc. will be skipped, so that it
may result in never allowing powersave on MLO connections.
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: Miri Korenblit <miriam.rachel.korenblit@intel.com>
Link: https://msgid.link/20240605135233.48e2b8af07e3.Ib9793c383fcba118c05100e024f4a11a1c3d0e85@changeid
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2024-06-05 13:57:18 +03:00
|
|
|
|
2022-07-18 22:23:53 +02:00
|
|
|
|
2022-06-14 13:49:16 +03:00
|
|
|
|
|
|
|
|
|
2014-02-03 14:44:44 +01:00
|
|
|
|
2016-03-17 15:41:39 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-06-17 10:34:54 +02:00
|
|
|
|
|
|
|
|
|
2011-12-14 12:35:30 +01:00
|
|
|
|
2018-12-18 17:02:08 -08:00
|
|
|
|
2022-06-25 23:24:05 +02:00
|
|
|
|
2018-12-18 17:02:08 -08:00
|
|
|
|
2026-03-26 12:14:38 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-06-11 17:18:19 +03:00
|
|
|
|
2015-09-23 10:41:27 +02:00
|
|
|
|
|
|
|
|
|
2014-06-11 17:18:19 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-07-13 12:05:27 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-12-14 12:35:30 +01:00
|
|
|
|
2007-12-19 02:03:35 +01:00
|
|
|
|
|
|
|
|
|
2026-02-19 11:47:13 +02:00
|
|
|
|
2014-05-19 17:19:31 +02:00
|
|
|
|
|
|
|
|
|
2007-12-19 02:03:35 +01:00
|
|
|
|
2008-07-29 13:22:52 +02:00
|
|
|
|
2007-12-19 02:03:35 +01:00
|
|
|
|
|
|
|
|
|
2008-02-25 16:27:47 +01:00
|
|
|
|
2007-12-19 02:03:35 +01:00
|
|
|
|
2023-08-28 14:00:01 +02:00
|
|
|
|
|
|
|
|
|
2007-12-19 02:03:35 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-09-11 00:01:58 +02:00
|
|
|
|
|
|
|
|
|
2007-12-19 02:03:35 +01:00
|
|
|
|
|
|
|
|
|
2026-02-19 11:47:13 +02:00
|
|
|
|
2007-12-19 02:03:35 +01:00
|
|
|
|
mac80211: Convert compare_ether_addr to ether_addr_equal
Use the new bool function ether_addr_equal to add
some clarity and reduce the likelihood for misuse
of compare_ether_addr for sorting.
Done via cocci script:
$ cat compare_ether_addr.cocci
@@
expression a,b;
@@
- !compare_ether_addr(a, b)
+ ether_addr_equal(a, b)
@@
expression a,b;
@@
- compare_ether_addr(a, b)
+ !ether_addr_equal(a, b)
@@
expression a,b;
@@
- !ether_addr_equal(a, b) == 0
+ ether_addr_equal(a, b)
@@
expression a,b;
@@
- !ether_addr_equal(a, b) != 0
+ !ether_addr_equal(a, b)
@@
expression a,b;
@@
- ether_addr_equal(a, b) == 0
+ !ether_addr_equal(a, b)
@@
expression a,b;
@@
- ether_addr_equal(a, b) != 0
+ ether_addr_equal(a, b)
@@
expression a,b;
@@
- !!ether_addr_equal(a, b)
+ ether_addr_equal(a, b)
Signed-off-by: Joe Perches <joe@perches.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2012-05-08 18:56:52 +00:00
|
|
|
|
2008-02-27 09:56:40 +01:00
|
|
|
|
|
|
|
|
|
2019-07-24 14:46:10 +05:30
|
|
|
|
2008-02-27 09:56:40 +01:00
|
|
|
|
|
|
|
|
|
2019-08-01 09:30:33 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-07-18 09:14:30 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-07-14 23:40:47 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-07-18 09:14:30 +02:00
|
|
|
|
2022-07-14 23:40:47 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-02-25 16:27:47 +01:00
|
|
|
|
|
|
|
|
|
2007-12-19 02:03:35 +01:00
|
|
|
|
2015-09-23 10:41:27 +02:00
|
|
|
|
|
|
|
|
|
2007-12-19 02:03:35 +01:00
|
|
|
|
2022-06-14 13:49:16 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-12-14 12:35:30 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-12-19 02:03:35 +01:00
|
|
|
|
2011-11-07 23:24:39 +02:00
|
|
|
|
2015-09-23 10:41:27 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-11-07 23:24:39 +02:00
|
|
|
|
2015-09-23 10:41:27 +02:00
|
|
|
|
|
|
|
|
|
wifi: mac80211: allow rate_control_rate_init() for links
Andrei previously fixed an issue in the client where the NSS
for links other than the primary/assoc/deflink isn't set. The
same issue appears to exist on the AP side, because there's
only a call to rate_control_rate_init() for the deflink, and
not any other links.
Rework the code a bit to do rate_control_rate_init() for links,
even if it really doesn't work with software rate control yet,
it does other things as well.
Also add rate_control_rate_init_all_links() to actually do it
properly when moving to ASSOC state in cfg80211.
Change the explicit call to ieee80211_sta_init_nss() to instead
be rate_control_rate_init() now in the client code, but also
add a call to rate_control_rate_init() when a link is added in
AP mode and the STA is already associated.
This should fix the NSS initialization issue, and perhaps pave
the way for actual software rate scaling a bit, in case anyone
cares in the future, but that of course needs a lot more than
just the init call.
We still need to fix the rate control _update_ as well, and the
sta_rc_update() driver method especially, but that will be in a
different patch.
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: Miri Korenblit <miriam.rachel.korenblit@intel.com>
Link: https://patch.msgid.link/20241007144851.c693274a908f.I0376da02e9f5a30eaa1b5d0d01371ff09506d453@changeid
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2024-10-07 15:00:53 +03:00
|
|
|
|
2007-12-19 02:03:35 +01:00
|
|
|
|
2026-03-26 12:14:40 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-12-19 02:03:35 +01:00
|
|
|
|
|
|
|
|
|
2026-02-19 11:47:13 +02:00
|
|
|
|
2014-10-10 20:52:40 +03:00
|
|
|
|
2007-12-19 02:03:35 +01:00
|
|
|
|
2008-07-29 13:22:52 +02:00
|
|
|
|
2007-12-19 02:03:35 +01:00
|
|
|
|
2026-02-19 11:47:13 +02:00
|
|
|
|
2008-07-29 13:22:52 +02:00
|
|
|
|
2014-10-10 20:52:40 +03:00
|
|
|
|
|
|
|
|
|
2007-12-19 02:03:35 +01:00
|
|
|
|
2024-02-05 21:59:51 +05:30
|
|
|
|
2007-12-19 02:03:35 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-03-26 22:17:21 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-12-19 02:03:35 +01:00
|
|
|
|
2026-02-19 11:47:13 +02:00
|
|
|
|
2007-12-19 02:03:35 +01:00
|
|
|
|
|
|
|
|
|
2026-02-19 11:47:13 +02:00
|
|
|
|
2008-07-29 13:22:52 +02:00
|
|
|
|
2007-12-19 02:03:35 +01:00
|
|
|
|
|
|
|
|
|
2013-02-15 00:48:33 +01:00
|
|
|
|
2011-12-29 14:41:39 +02:00
|
|
|
|
2007-12-19 02:03:35 +01:00
|
|
|
|
2023-08-28 14:00:01 +02:00
|
|
|
|
2008-04-10 15:36:09 +02:00
|
|
|
|
2010-01-08 18:10:58 +01:00
|
|
|
|
2023-08-28 14:00:01 +02:00
|
|
|
|
|
|
|
|
|
2007-12-19 02:03:35 +01:00
|
|
|
|
2013-02-15 00:48:33 +01:00
|
|
|
|
|
|
|
|
|
2013-03-04 13:06:12 -08:00
|
|
|
|
2013-03-04 13:06:11 -08:00
|
|
|
|
2013-02-15 00:48:33 +01:00
|
|
|
|
2013-03-04 13:06:11 -08:00
|
|
|
|
2013-02-15 00:48:33 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-09-23 10:41:27 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-02-15 00:48:33 +01:00
|
|
|
|
2026-03-26 12:14:38 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-02-15 00:48:33 +01:00
|
|
|
|
2023-08-28 14:00:01 +02:00
|
|
|
|
2011-12-14 12:20:27 +01:00
|
|
|
|
|
|
|
|
|
2013-02-15 00:48:33 +01:00
|
|
|
|
|
|
|
|
|
2023-08-28 14:00:01 +02:00
|
|
|
|
2013-02-15 00:48:33 +01:00
|
|
|
|
2008-02-25 16:27:46 +01:00
|
|
|
|
2007-12-19 02:03:35 +01:00
|
|
|
|
|
|
|
|
|
2009-11-19 11:55:19 +01:00
|
|
|
|
2026-03-26 22:17:21 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-11-10 20:10:05 +01:00
|
|
|
|
2012-04-23 19:49:03 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-03-16 08:43:36 +01:00
|
|
|
|
2014-03-24 00:51:43 +05:30
|
|
|
|
2016-10-10 19:12:21 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-11-10 20:10:05 +01:00
|
|
|
|
2008-07-29 13:22:52 +02:00
|
|
|
|
2024-03-16 08:43:36 +01:00
|
|
|
|
2015-05-19 14:13:36 +02:00
|
|
|
|
2012-04-23 19:49:03 +02:00
|
|
|
|
mac80211: Do not send Layer 2 Update frame before authorization
The Layer 2 Update frame is used to update bridges when a station roams
to another AP even if that STA does not transmit any frames after the
reassociation. This behavior was described in IEEE Std 802.11F-2003 as
something that would happen based on MLME-ASSOCIATE.indication, i.e.,
before completing 4-way handshake. However, this IEEE trial-use
recommended practice document was published before RSN (IEEE Std
802.11i-2004) and as such, did not consider RSN use cases. Furthermore,
IEEE Std 802.11F-2003 was withdrawn in 2006 and as such, has not been
maintained amd should not be used anymore.
Sending out the Layer 2 Update frame immediately after association is
fine for open networks (and also when using SAE, FT protocol, or FILS
authentication when the station is actually authenticated by the time
association completes). However, it is not appropriate for cases where
RSN is used with PSK or EAP authentication since the station is actually
fully authenticated only once the 4-way handshake completes after
authentication and attackers might be able to use the unauthenticated
triggering of Layer 2 Update frame transmission to disrupt bridge
behavior.
Fix this by postponing transmission of the Layer 2 Update frame from
station entry addition to the point when the station entry is marked
authorized. Similarly, send out the VLAN binding update only if the STA
entry has already been authorized.
Signed-off-by: Jouni Malinen <jouni@codeaurora.org>
Reviewed-by: Johannes Berg <johannes@sipsolutions.net>
Signed-off-by: David S. Miller <davem@davemloft.net>
2019-09-11 16:03:05 +03:00
|
|
|
|
2016-10-10 19:12:21 +02:00
|
|
|
|
mac80211: Do not send Layer 2 Update frame before authorization
The Layer 2 Update frame is used to update bridges when a station roams
to another AP even if that STA does not transmit any frames after the
reassociation. This behavior was described in IEEE Std 802.11F-2003 as
something that would happen based on MLME-ASSOCIATE.indication, i.e.,
before completing 4-way handshake. However, this IEEE trial-use
recommended practice document was published before RSN (IEEE Std
802.11i-2004) and as such, did not consider RSN use cases. Furthermore,
IEEE Std 802.11F-2003 was withdrawn in 2006 and as such, has not been
maintained amd should not be used anymore.
Sending out the Layer 2 Update frame immediately after association is
fine for open networks (and also when using SAE, FT protocol, or FILS
authentication when the station is actually authenticated by the time
association completes). However, it is not appropriate for cases where
RSN is used with PSK or EAP authentication since the station is actually
fully authenticated only once the 4-way handshake completes after
authentication and attackers might be able to use the unauthenticated
triggering of Layer 2 Update frame transmission to disrupt bridge
behavior.
Fix this by postponing transmission of the Layer 2 Update frame from
station entry addition to the point when the station entry is marked
authorized. Similarly, send out the VLAN binding update only if the STA
entry has already been authorized.
Signed-off-by: Jouni Malinen <jouni@codeaurora.org>
Reviewed-by: Johannes Berg <johannes@sipsolutions.net>
Signed-off-by: David S. Miller <davem@davemloft.net>
2019-09-11 16:03:05 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-12-19 02:03:35 +01:00
|
|
|
|
|
|
|
|
|
2026-03-26 12:14:38 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-08-29 12:18:56 +02:00
|
|
|
|
2013-02-15 00:48:33 +01:00
|
|
|
|
2023-08-28 14:00:01 +02:00
|
|
|
|
2008-04-10 15:36:09 +02:00
|
|
|
|
2011-03-10 16:43:19 -08:00
|
|
|
|
2012-07-27 12:33:22 +03:00
|
|
|
|
2015-10-14 18:02:43 +02:00
|
|
|
|
2012-07-27 12:33:22 +03:00
|
|
|
|
|
|
|
|
|
2013-02-15 00:48:33 +01:00
|
|
|
|
2007-12-19 02:03:35 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-02-23 15:17:17 +01:00
|
|
|
|
|
|
|
|
|
2014-05-19 17:19:31 +02:00
|
|
|
|
2008-02-23 15:17:17 +01:00
|
|
|
|
2008-07-29 13:22:52 +02:00
|
|
|
|
2008-02-23 15:17:17 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-07-29 13:22:52 +02:00
|
|
|
|
|
|
|
|
|
2008-02-25 16:27:46 +01:00
|
|
|
|
2009-11-25 17:46:18 +01:00
|
|
|
|
2008-02-25 16:27:46 +01:00
|
|
|
|
|
|
|
|
|
2008-02-23 15:17:17 +01:00
|
|
|
|
2008-02-25 16:27:46 +01:00
|
|
|
|
2008-02-23 15:17:17 +01:00
|
|
|
|
2013-03-29 09:38:39 -04:00
|
|
|
|
|
|
|
|
|
2008-02-25 16:27:46 +01:00
|
|
|
|
2013-03-29 09:38:39 -04:00
|
|
|
|
2008-02-25 16:27:46 +01:00
|
|
|
|
2008-02-23 15:17:17 +01:00
|
|
|
|
|
|
|
|
|
2008-02-25 16:27:46 +01:00
|
|
|
|
2008-02-23 15:17:17 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-05-19 17:19:31 +02:00
|
|
|
|
2008-02-23 15:17:17 +01:00
|
|
|
|
2008-08-03 12:04:37 +12:00
|
|
|
|
2008-02-23 15:17:17 +01:00
|
|
|
|
2008-08-03 12:04:37 +12:00
|
|
|
|
2013-02-15 14:40:31 +01:00
|
|
|
|
2008-08-03 12:04:37 +12:00
|
|
|
|
2011-08-29 13:23:04 -07:00
|
|
|
|
2008-02-23 15:17:17 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-05-19 17:19:31 +02:00
|
|
|
|
|
|
|
|
|
2008-02-23 15:17:17 +01:00
|
|
|
|
2008-07-29 13:22:52 +02:00
|
|
|
|
2008-02-23 15:17:17 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-07-29 13:22:52 +02:00
|
|
|
|
|
|
|
|
|
2008-02-23 15:17:17 +01:00
|
|
|
|
2008-02-25 16:27:46 +01:00
|
|
|
|
2009-11-25 17:46:18 +01:00
|
|
|
|
2008-02-25 16:27:46 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-02-15 14:40:31 +01:00
|
|
|
|
2008-02-23 15:17:17 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-02-25 16:27:46 +01:00
|
|
|
|
2008-02-23 15:17:17 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-05-12 15:11:37 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-02-23 15:17:17 +01:00
|
|
|
|
2015-03-02 19:54:57 -08:00
|
|
|
|
2008-02-23 15:17:17 +01:00
|
|
|
|
2012-08-27 22:28:16 +09:00
|
|
|
|
|
|
|
|
|
2016-02-28 20:03:56 -05:00
|
|
|
|
2009-08-07 16:17:38 +02:00
|
|
|
|
2008-02-23 15:17:17 +01:00
|
|
|
|
2009-11-09 23:46:55 +00:00
|
|
|
|
2008-02-23 15:17:17 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-01-15 15:28:42 -08:00
|
|
|
|
2019-01-15 15:28:43 -08:00
|
|
|
|
|
|
|
|
|
2008-02-23 15:17:17 +01:00
|
|
|
|
|
|
|
|
|
2009-11-09 23:46:55 +00:00
|
|
|
|
2008-02-23 15:17:17 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-11-09 23:46:55 +00:00
|
|
|
|
|
|
|
|
|
2008-02-23 15:17:17 +01:00
|
|
|
|
|
|
|
|
|
2012-08-27 22:28:16 +09:00
|
|
|
|
|
|
|
|
|
2019-01-15 15:28:42 -08:00
|
|
|
|
2019-01-15 15:28:43 -08:00
|
|
|
|
2008-02-23 15:17:17 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-07-29 13:22:52 +02:00
|
|
|
|
2008-02-23 15:17:17 +01:00
|
|
|
|
|
|
|
|
|
2008-07-29 13:22:52 +02:00
|
|
|
|
|
|
|
|
|
2008-02-23 15:17:17 +01:00
|
|
|
|
2013-02-15 14:40:31 +01:00
|
|
|
|
2008-02-23 15:17:17 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-05-19 17:19:31 +02:00
|
|
|
|
|
|
|
|
|
2008-02-23 15:17:17 +01:00
|
|
|
|
2008-07-29 13:22:52 +02:00
|
|
|
|
2008-02-23 15:17:17 +01:00
|
|
|
|
|
|
|
|
|
2008-07-29 13:22:52 +02:00
|
|
|
|
|
|
|
|
|
2008-02-23 15:17:17 +01:00
|
|
|
|
2013-02-15 14:40:31 +01:00
|
|
|
|
2008-02-23 15:17:17 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-10-21 12:03:48 -07:00
|
|
|
|
2014-09-12 08:58:50 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-02-28 20:03:56 -05:00
|
|
|
|
2014-09-12 08:58:50 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-12-16 17:37:48 -08:00
|
|
|
|
2008-10-21 12:03:48 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-12-16 17:37:49 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-11-24 17:15:20 -08:00
|
|
|
|
|
|
|
|
|
2020-04-25 18:57:12 +03:00
|
|
|
|
2010-12-16 17:37:49 -08:00
|
|
|
|
2011-04-07 15:08:27 -07:00
|
|
|
|
2010-12-16 17:37:49 -08:00
|
|
|
|
|
|
|
|
|
2011-04-07 15:08:27 -07:00
|
|
|
|
|
|
|
|
|
2010-12-16 17:37:49 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-04-07 15:08:27 -07:00
|
|
|
|
|
|
|
|
|
2010-12-16 17:37:49 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-03-31 11:31:33 -07:00
|
|
|
|
2010-12-16 17:37:49 -08:00
|
|
|
|
|
|
|
|
|
2013-03-04 13:06:12 -08:00
|
|
|
|
2013-05-08 11:46:00 -07:00
|
|
|
|
2011-05-03 16:57:07 -07:00
|
|
|
|
2017-05-16 11:23:13 +02:00
|
|
|
|
2011-05-03 16:57:07 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-12-16 17:37:49 -08:00
|
|
|
|
2011-11-24 17:15:20 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-06-03 10:33:36 -07:00
|
|
|
|
2011-11-24 17:15:20 -08:00
|
|
|
|
2013-01-07 16:04:51 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-04-25 18:57:12 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-12-16 17:37:49 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-12-16 17:37:48 -08:00
|
|
|
|
2010-12-03 09:20:44 +01:00
|
|
|
|
|
|
|
|
|
2008-10-21 12:03:48 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-11-09 23:46:57 +00:00
|
|
|
|
|
|
|
|
|
2008-10-21 12:03:48 -07:00
|
|
|
|
2009-11-09 23:46:57 +00:00
|
|
|
|
2008-10-21 12:03:48 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-12-03 09:20:40 +01:00
|
|
|
|
2012-06-15 00:23:53 +08:00
|
|
|
|
2013-03-04 13:06:14 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-10-21 12:03:48 -07:00
|
|
|
|
2013-03-04 13:06:14 -08:00
|
|
|
|
2012-03-31 11:31:33 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-10-21 12:03:48 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-11-24 17:15:24 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-10-21 12:03:48 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-11-09 23:46:57 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-08-09 16:45:11 -07:00
|
|
|
|
2011-08-25 10:36:14 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-06-14 02:06:09 +08:00
|
|
|
|
|
|
|
|
|
2011-08-25 10:36:14 -07:00
|
|
|
|
|
|
|
|
|
2011-08-09 16:45:11 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-06-11 11:59:36 +08:00
|
|
|
|
2011-08-09 16:45:10 -07:00
|
|
|
|
|
|
|
|
|
2012-01-21 01:02:16 +08:00
|
|
|
|
|
|
|
|
|
2012-02-28 17:04:08 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-06-02 21:39:54 +02:00
|
|
|
|
2023-12-11 09:05:25 +02:00
|
|
|
|
2012-02-28 17:04:08 -08:00
|
|
|
|
|
|
|
|
|
2012-04-30 14:20:32 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-06-17 22:36:37 +02:00
|
|
|
|
|
|
|
|
|
2012-04-30 14:20:32 -07:00
|
|
|
|
2012-06-14 02:06:06 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-06-14 02:06:10 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-01-30 18:14:08 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-02-14 11:20:13 -08:00
|
|
|
|
2013-01-30 18:14:08 +01:00
|
|
|
|
|
|
|
|
|
2013-06-03 09:53:40 -07:00
|
|
|
|
|
|
|
|
|
2018-10-25 17:36:34 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-06-17 09:30:33 +02:00
|
|
|
|
|
|
|
|
|
2020-06-11 16:02:37 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-02-14 11:20:13 -08:00
|
|
|
|
2008-10-21 12:03:48 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-12-03 09:20:44 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
wifi: mac80211: introduce 'channel request'
For channel contexts, mac80211 currently uses the cfg80211
chandef struct (control channel, center freq(s), width) to
define towards drivers and internally how these behave. In
fact, there are _two_ such structs used, where the min_def
can reduce bandwidth according to the stations connected.
Unfortunately, with EHT this is longer be sufficient, at
least not for all hardware. EHT requires that non-AP STAs
that are connected to an AP with a lower bandwidth than it
(the AP) advertises (e.g. 160 MHz STA connected to 320 MHz
AP) still be able to receive downlink OFDMA and respond to
trigger frames for uplink OFDMA that specify the position
and bandwidth for the non-AP STA relative to the channel
the AP is using. Therefore, they need to be aware of this,
and at least for some hardware (e.g. Intel) this awareness
is in the hardware. As a result, use of the "same" channel
may need to be split over two channel contexts where they
differ by the AP being used.
As a first step, introduce a concept of a channel request
('chanreq') for each interface, to control the context it
requests. This step does nothing but reorganise the code,
so that later the AP's chandef can be added to the request
in order to handle the EHT case described above.
Link: https://msgid.link/20240129194108.2e88e48bd2e9.I4256183debe975c5ed71621611206fdbb69ba330@changeid
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2024-01-29 19:34:40 +01:00
|
|
|
|
2010-12-03 09:20:44 +01:00
|
|
|
|
2010-12-16 17:37:49 -08:00
|
|
|
|
2010-12-03 09:20:44 +01:00
|
|
|
|
2023-08-28 14:00:05 +02:00
|
|
|
|
|
|
|
|
|
2010-12-16 17:37:49 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-05-16 23:50:20 +02:00
|
|
|
|
2018-03-26 12:52:51 -05:00
|
|
|
|
|
|
|
|
|
2012-09-11 14:34:12 +02:00
|
|
|
|
2022-05-16 15:00:15 +02:00
|
|
|
|
|
|
|
|
|
2012-09-11 14:34:12 +02:00
|
|
|
|
wifi: mac80211: introduce 'channel request'
For channel contexts, mac80211 currently uses the cfg80211
chandef struct (control channel, center freq(s), width) to
define towards drivers and internally how these behave. In
fact, there are _two_ such structs used, where the min_def
can reduce bandwidth according to the stations connected.
Unfortunately, with EHT this is longer be sufficient, at
least not for all hardware. EHT requires that non-AP STAs
that are connected to an AP with a lower bandwidth than it
(the AP) advertises (e.g. 160 MHz STA connected to 320 MHz
AP) still be able to receive downlink OFDMA and respond to
trigger frames for uplink OFDMA that specify the position
and bandwidth for the non-AP STA relative to the channel
the AP is using. Therefore, they need to be aware of this,
and at least for some hardware (e.g. Intel) this awareness
is in the hardware. As a result, use of the "same" channel
may need to be split over two channel contexts where they
differ by the AP being used.
As a first step, introduce a concept of a channel request
('chanreq') for each interface, to control the context it
requests. This step does nothing but reorganise the code,
so that later the AP's chandef can be added to the request
in order to handle the EHT case described above.
Link: https://msgid.link/20240129194108.2e88e48bd2e9.I4256183debe975c5ed71621611206fdbb69ba330@changeid
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2024-01-29 19:34:40 +01:00
|
|
|
|
2022-05-30 18:35:23 +02:00
|
|
|
|
2012-05-16 23:50:20 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-02-14 11:20:13 -08:00
|
|
|
|
2010-12-03 09:20:44 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-08-28 14:00:05 +02:00
|
|
|
|
|
|
|
|
|
2010-12-03 09:20:44 +01:00
|
|
|
|
2022-06-17 22:36:37 +02:00
|
|
|
|
2020-07-04 15:50:07 +02:00
|
|
|
|
2010-12-03 09:20:44 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-02-23 15:17:17 +01:00
|
|
|
|
|
|
|
|
|
2008-08-07 20:07:01 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-07-26 17:24:39 +02:00
|
|
|
|
2022-09-06 22:42:25 +02:00
|
|
|
|
2017-04-27 12:45:38 +05:30
|
|
|
|
2023-06-04 12:11:26 +03:00
|
|
|
|
2008-08-07 20:07:01 +03:00
|
|
|
|
2022-09-06 22:42:25 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-07-26 17:24:39 +02:00
|
|
|
|
|
|
|
|
|
2022-09-06 22:42:25 +02:00
|
|
|
|
2017-04-27 12:45:38 +05:30
|
|
|
|
|
|
|
|
|
2008-08-07 20:07:01 +03:00
|
|
|
|
2023-02-24 10:52:19 +01:00
|
|
|
|
2026-01-08 14:32:57 +01:00
|
|
|
|
2023-02-24 10:52:19 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-08-07 20:07:01 +03:00
|
|
|
|
2022-09-06 22:42:25 +02:00
|
|
|
|
2008-08-07 20:07:01 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-09-06 22:42:25 +02:00
|
|
|
|
2008-08-07 20:07:01 +03:00
|
|
|
|
|
|
|
|
|
2010-01-15 03:00:48 +01:00
|
|
|
|
2022-09-06 22:42:25 +02:00
|
|
|
|
2020-05-28 21:34:46 +02:00
|
|
|
|
|
|
|
|
|
2022-09-06 22:42:25 +02:00
|
|
|
|
2010-01-15 03:00:48 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-08-07 20:07:01 +03:00
|
|
|
|
2022-09-06 22:42:25 +02:00
|
|
|
|
2008-08-07 20:07:01 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-04-27 01:23:36 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-03-31 20:02:10 +03:00
|
|
|
|
2010-04-27 01:23:36 +02:00
|
|
|
|
|
|
|
|
|
2010-11-19 12:40:26 +01:00
|
|
|
|
2022-09-06 22:42:25 +02:00
|
|
|
|
2010-11-19 12:40:26 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-11-14 15:21:17 +01:00
|
|
|
|
2022-09-06 22:42:25 +02:00
|
|
|
|
2013-03-21 15:47:56 +01:00
|
|
|
|
2022-09-06 22:42:25 +02:00
|
|
|
|
2013-03-21 15:47:56 +01:00
|
|
|
|
2012-11-14 15:21:17 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-03-21 15:47:56 +01:00
|
|
|
|
2022-09-06 22:42:25 +02:00
|
|
|
|
2013-03-21 15:47:56 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-09-06 22:42:25 +02:00
|
|
|
|
2013-03-21 15:47:56 +01:00
|
|
|
|
2012-11-14 15:21:17 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-09-06 22:42:25 +02:00
|
|
|
|
2008-08-07 20:07:01 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-10-30 16:59:24 +02:00
|
|
|
|
2011-09-25 20:06:53 +03:00
|
|
|
|
2008-10-30 16:59:24 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-09-25 20:06:54 +03:00
|
|
|
|
2022-08-02 15:22:42 +03:00
|
|
|
|
2022-08-17 11:17:01 +02:00
|
|
|
|
2008-10-30 16:59:24 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-03-28 11:04:25 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-08-02 15:22:42 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-10-30 16:59:24 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-01-12 10:42:31 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-03-28 13:24:10 +03:00
|
|
|
|
|
|
|
|
|
2022-06-24 15:40:11 +02:00
|
|
|
|
|
|
|
|
|
2010-08-20 16:25:38 -07:00
|
|
|
|
2012-03-28 11:04:24 +02:00
|
|
|
|
|
|
|
|
|
2008-10-30 16:59:24 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-06-24 15:40:11 +02:00
|
|
|
|
2022-06-17 22:36:37 +02:00
|
|
|
|
2012-07-06 17:37:43 +02:00
|
|
|
|
2008-10-30 16:59:24 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-01-19 11:20:53 -05:00
|
|
|
|
2011-05-04 15:37:28 +02:00
|
|
|
|
|
|
|
|
|
2009-01-19 11:20:53 -05:00
|
|
|
|
2011-05-04 15:37:29 +02:00
|
|
|
|
2009-01-19 11:20:53 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-06-18 19:17:03 +02:00
|
|
|
|
2025-08-12 12:53:30 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-06-18 19:17:03 +02:00
|
|
|
|
|
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
2010-09-16 14:58:23 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-06-18 20:07:15 +02:00
|
|
|
|
2010-09-16 14:58:23 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-02-01 15:35:36 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-07-07 15:45:48 -05:00
|
|
|
|
2010-09-16 14:58:23 +02:00
|
|
|
|
2012-10-16 08:39:22 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-12-22 10:29:57 +01:00
|
|
|
|
2012-10-16 08:39:22 +02:00
|
|
|
|
|
|
|
|
|
2025-08-12 12:53:30 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-09-16 14:58:23 +02:00
|
|
|
|
2016-09-20 17:31:13 +03:00
|
|
|
|
2026-04-20 14:38:46 +05:30
|
|
|
|
2010-09-16 14:58:23 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-10-30 19:14:50 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-05-11 17:09:36 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-04-21 13:05:02 +01:00
|
|
|
|
|
|
|
|
|
2011-05-11 17:09:36 +03:00
|
|
|
|
2015-10-25 10:59:33 +02:00
|
|
|
|
2011-05-11 17:09:36 +03:00
|
|
|
|
2015-10-25 10:59:33 +02:00
|
|
|
|
2011-05-11 17:09:36 +03:00
|
|
|
|
|
|
|
|
|
2015-10-25 10:59:33 +02:00
|
|
|
|
2011-05-11 17:09:36 +03:00
|
|
|
|
|
|
|
|
|
2009-03-19 13:39:22 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-07-07 03:45:17 +02:00
|
|
|
|
2009-03-19 13:39:22 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-07-07 03:45:17 +02:00
|
|
|
|
2009-03-19 13:39:22 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-02-24 13:50:51 +01:00
|
|
|
|
2009-03-19 13:39:22 +02:00
|
|
|
|
2012-02-24 13:50:51 +01:00
|
|
|
|
2009-03-19 13:39:22 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-02-24 13:50:51 +01:00
|
|
|
|
2009-03-19 13:39:22 +02:00
|
|
|
|
2012-02-24 13:50:51 +01:00
|
|
|
|
2009-03-19 13:39:22 +02:00
|
|
|
|
|
|
|
|
|
2009-04-19 21:25:43 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-07-26 17:24:39 +02:00
|
|
|
|
2009-04-19 21:25:43 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-07-26 17:24:39 +02:00
|
|
|
|
2009-04-19 21:25:43 +02:00
|
|
|
|
|
|
|
|
|
2014-11-03 10:33:19 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-11-02 13:27:49 +01:00
|
|
|
|
2016-04-12 15:56:15 +02:00
|
|
|
|
2012-11-02 13:27:49 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-02-06 17:23:45 +01:00
|
|
|
|
2016-04-12 15:56:15 +02:00
|
|
|
|
2012-11-02 13:27:49 +01:00
|
|
|
|
2024-05-15 13:34:10 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-03-22 12:18:03 -07:00
|
|
|
|
2012-11-02 13:27:49 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-06-15 13:53:09 +05:30
|
|
|
|
|
|
|
|
|
2009-04-20 18:39:05 +02:00
|
|
|
|
|
|
|
|
|
2009-04-23 18:52:52 +02:00
|
|
|
|
2009-04-20 18:39:05 +02:00
|
|
|
|
2010-11-08 11:51:06 +02:00
|
|
|
|
2015-03-21 15:25:43 +01:00
|
|
|
|
|
|
|
|
|
2025-06-15 13:53:09 +05:30
|
|
|
|
|
|
|
|
|
2010-11-08 11:51:06 +02:00
|
|
|
|
2015-03-21 15:25:43 +01:00
|
|
|
|
|
|
|
|
|
2010-11-08 11:51:06 +02:00
|
|
|
|
2015-03-21 15:25:43 +01:00
|
|
|
|
2010-11-08 11:51:06 +02:00
|
|
|
|
|
|
|
|
|
2014-09-04 23:57:41 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-06-15 13:53:09 +05:30
|
|
|
|
|
|
|
|
|
2009-12-21 22:50:48 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-04-20 18:39:05 +02:00
|
|
|
|
2025-06-15 13:53:12 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-04-20 18:39:05 +02:00
|
|
|
|
2009-04-23 18:52:52 +02:00
|
|
|
|
|
|
|
|
|
2009-04-20 18:39:05 +02:00
|
|
|
|
|
|
|
|
|
2012-11-09 18:38:32 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-04-20 18:39:05 +02:00
|
|
|
|
2012-11-09 18:38:32 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-04-20 18:39:05 +02:00
|
|
|
|
2012-11-09 18:38:32 +01:00
|
|
|
|
2009-04-20 18:39:05 +02:00
|
|
|
|
|
|
|
|
|
2025-06-15 13:53:09 +05:30
|
|
|
|
|
|
|
|
|
2009-04-20 18:39:05 +02:00
|
|
|
|
2018-05-08 13:03:50 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-06-15 13:53:09 +05:30
|
|
|
|
2018-05-08 13:03:50 +02:00
|
|
|
|
2009-04-20 18:39:05 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-06-02 13:01:39 +02:00
|
|
|
|
2025-06-15 13:53:09 +05:30
|
|
|
|
2010-06-23 12:12:37 +03:00
|
|
|
|
2009-06-02 13:01:39 +02:00
|
|
|
|
|
|
|
|
|
2012-10-24 10:59:25 +02:00
|
|
|
|
2015-01-14 12:55:08 +01:00
|
|
|
|
|
|
|
|
|
2017-12-13 18:29:46 +01:00
|
|
|
|
2024-10-07 15:00:52 +03:00
|
|
|
|
2024-09-23 18:13:25 -07:00
|
|
|
|
2009-06-02 13:01:39 +02:00
|
|
|
|
2023-08-28 14:00:06 +02:00
|
|
|
|
|
|
|
|
|
2024-10-07 15:00:52 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-10-24 10:59:25 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-10-09 10:25:48 +02:00
|
|
|
|
|
|
|
|
|
2024-07-25 18:48:36 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-11-12 13:51:44 +01:00
|
|
|
|
|
|
|
|
|
2017-12-13 18:29:46 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-10-07 15:00:52 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-10-24 10:59:25 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-07-26 17:24:39 +02:00
|
|
|
|
2024-10-07 15:00:52 +03:00
|
|
|
|
2009-06-02 13:01:39 +02:00
|
|
|
|
2015-01-14 12:55:08 +01:00
|
|
|
|
2024-10-09 10:25:48 +02:00
|
|
|
|
|
|
|
|
|
2017-12-13 18:29:46 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-10-07 15:00:52 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-01-14 12:55:08 +01:00
|
|
|
|
2017-12-13 18:29:46 +01:00
|
|
|
|
2024-10-09 10:25:48 +02:00
|
|
|
|
|
|
|
|
|
2017-12-13 18:29:46 +01:00
|
|
|
|
2024-10-07 15:00:52 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-12-13 18:29:46 +01:00
|
|
|
|
2009-06-02 13:01:39 +02:00
|
|
|
|
2017-12-13 18:29:46 +01:00
|
|
|
|
2021-11-12 13:51:44 +01:00
|
|
|
|
|
|
|
|
|
2024-07-25 18:48:36 +02:00
|
|
|
|
2022-05-16 15:00:15 +02:00
|
|
|
|
2017-12-13 18:29:46 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-10-07 15:00:50 +03:00
|
|
|
|
|
|
|
|
|
2017-12-13 18:29:46 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-09-23 18:13:25 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-06-02 13:01:39 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-10-24 10:17:18 +02:00
|
|
|
|
|
|
|
|
|
2025-06-15 13:53:09 +05:30
|
|
|
|
2024-11-25 14:02:16 +05:30
|
|
|
|
2012-10-24 10:17:18 +02:00
|
|
|
|
2009-06-02 13:01:39 +02:00
|
|
|
|
|
|
|
|
|
2012-10-24 10:59:25 +02:00
|
|
|
|
2024-11-25 14:02:17 +05:30
|
|
|
|
2009-06-02 13:01:39 +02:00
|
|
|
|
2024-10-02 11:56:30 +02:00
|
|
|
|
|
|
|
|
|
2024-11-25 14:02:17 +05:30
|
|
|
|
2014-10-26 00:32:53 +02:00
|
|
|
|
2024-11-25 14:02:17 +05:30
|
|
|
|
2012-10-24 10:59:25 +02:00
|
|
|
|
2024-11-25 14:02:17 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-06-02 13:01:39 +02:00
|
|
|
|
2023-02-03 10:36:36 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-06-02 13:01:39 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-06-02 13:01:41 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-07-01 21:26:51 +02:00
|
|
|
|
2013-07-31 18:04:15 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-07-01 21:26:51 +02:00
|
|
|
|
|
|
|
|
|
2013-07-31 18:06:22 +03:00
|
|
|
|
2009-07-01 21:26:51 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-07-31 18:06:22 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-07-01 21:26:51 +02:00
|
|
|
|
2011-05-20 09:05:54 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-07-01 21:26:51 +02:00
|
|
|
|
|
|
|
|
|
2013-10-01 16:45:43 +03:00
|
|
|
|
2022-06-17 22:36:37 +02:00
|
|
|
|
2013-10-01 16:45:43 +03:00
|
|
|
|
2009-12-01 13:37:02 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-06-14 16:53:46 +03:00
|
|
|
|
|
|
|
|
|
2009-12-01 13:37:02 +01:00
|
|
|
|
2023-08-29 12:18:56 +02:00
|
|
|
|
2011-04-19 20:44:04 +02:00
|
|
|
|
2013-10-01 16:45:43 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-02-28 09:48:11 +01:00
|
|
|
|
2023-08-28 15:09:25 +02:00
|
|
|
|
|
|
|
|
|
2022-06-17 22:36:37 +02:00
|
|
|
|
|
|
|
|
|
2009-12-01 13:37:02 +01:00
|
|
|
|
2023-09-28 17:35:27 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-12-01 13:37:02 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-09-11 14:34:12 +02:00
|
|
|
|
|
|
|
|
|
2009-12-01 13:37:02 +01:00
|
|
|
|
|
|
|
|
|
wifi: mac80211: introduce 'channel request'
For channel contexts, mac80211 currently uses the cfg80211
chandef struct (control channel, center freq(s), width) to
define towards drivers and internally how these behave. In
fact, there are _two_ such structs used, where the min_def
can reduce bandwidth according to the stations connected.
Unfortunately, with EHT this is longer be sufficient, at
least not for all hardware. EHT requires that non-AP STAs
that are connected to an AP with a lower bandwidth than it
(the AP) advertises (e.g. 160 MHz STA connected to 320 MHz
AP) still be able to receive downlink OFDMA and respond to
trigger frames for uplink OFDMA that specify the position
and bandwidth for the non-AP STA relative to the channel
the AP is using. Therefore, they need to be aware of this,
and at least for some hardware (e.g. Intel) this awareness
is in the hardware. As a result, use of the "same" channel
may need to be split over two channel contexts where they
differ by the AP being used.
As a first step, introduce a concept of a channel request
('chanreq') for each interface, to control the context it
requests. This step does nothing but reorganise the code,
so that later the AP's chandef can be added to the request
in order to handle the EHT case described above.
Link: https://msgid.link/20240129194108.2e88e48bd2e9.I4256183debe975c5ed71621611206fdbb69ba330@changeid
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2024-01-29 19:34:40 +01:00
|
|
|
|
2009-12-01 13:37:02 +01:00
|
|
|
|
|
|
|
|
|
2023-08-28 15:09:25 +02:00
|
|
|
|
2009-12-01 13:37:02 +01:00
|
|
|
|
2015-06-14 16:53:46 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-12-01 13:37:02 +01:00
|
|
|
|
2015-06-14 16:53:46 +03:00
|
|
|
|
2009-12-01 13:37:02 +01:00
|
|
|
|
2015-06-14 16:53:46 +03:00
|
|
|
|
|
|
|
|
|
2009-12-01 13:37:02 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-08-28 15:09:25 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-12-01 13:37:02 +01:00
|
|
|
|
2022-06-17 22:36:37 +02:00
|
|
|
|
2015-06-14 16:53:46 +03:00
|
|
|
|
2024-02-28 09:55:47 +01:00
|
|
|
|
2009-12-01 13:37:02 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-07-01 21:26:57 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-05-30 23:45:04 +02:00
|
|
|
|
2009-07-01 21:26:57 +02:00
|
|
|
|
2013-10-29 18:11:59 -04:00
|
|
|
|
2010-01-15 12:21:37 +01:00
|
|
|
|
|
|
|
|
|
2015-06-02 21:39:54 +02:00
|
|
|
|
2009-07-01 21:26:57 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-06-09 09:51:52 +03:00
|
|
|
|
2009-07-01 21:26:57 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-06-09 09:51:52 +03:00
|
|
|
|
2009-07-01 21:26:57 +02:00
|
|
|
|
2009-12-01 13:37:02 +01:00
|
|
|
|
2022-05-30 23:45:04 +02:00
|
|
|
|
2022-06-17 22:36:37 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-05-30 23:45:04 +02:00
|
|
|
|
2022-06-17 22:36:37 +02:00
|
|
|
|
|
|
|
|
|
2022-05-30 23:45:04 +02:00
|
|
|
|
2009-12-01 13:37:02 +01:00
|
|
|
|
2015-06-02 21:39:54 +02:00
|
|
|
|
2025-06-15 13:53:09 +05:30
|
|
|
|
2009-07-01 21:26:57 +02:00
|
|
|
|
2015-10-14 18:02:43 +02:00
|
|
|
|
2012-07-27 12:33:22 +03:00
|
|
|
|
2018-02-23 10:06:05 +01:00
|
|
|
|
2009-07-01 21:26:57 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-02-28 09:47:54 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-03-23 09:02:34 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-02-28 09:47:54 +01:00
|
|
|
|
2010-03-23 09:02:34 +02:00
|
|
|
|
2024-02-28 09:47:54 +01:00
|
|
|
|
|
|
|
|
|
2015-08-28 10:44:20 +02:00
|
|
|
|
|
|
|
|
|
2024-02-28 09:47:54 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-02-10 04:50:22 +01:00
|
|
|
|
2024-02-28 09:47:54 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-02-10 04:50:22 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-02-28 09:47:54 +01:00
|
|
|
|
2017-02-10 04:50:22 +01:00
|
|
|
|
2024-02-28 09:47:54 +01:00
|
|
|
|
2017-02-10 04:50:22 +01:00
|
|
|
|
|
|
|
|
|
2024-02-28 09:47:54 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-03-23 09:02:34 +02:00
|
|
|
|
2024-02-28 09:47:54 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-03-23 09:02:34 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-07-01 21:26:59 +02:00
|
|
|
|
|
|
|
|
|
2022-04-14 16:50:57 +02:00
|
|
|
|
2009-07-01 21:26:59 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-04-27 16:56:51 +05:30
|
|
|
|
2009-12-04 09:26:38 +01:00
|
|
|
|
2012-06-12 12:41:15 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
mac80211: reject/clear user rate mask if not usable
If the user rate mask results in no (basic) rates being usable,
clear it. Also, if we're already operating when it's set, reject
it instead.
Technically, selecting basic rates as the criterion is a bit too
restrictive, but calculating the usable rates over all stations
(e.g. in AP mode) is harder, and all stations must support the
basic rates. Similarly, in client mode, the basic rates will be
used anyway for control frames.
This fixes the "no supported rates (...) in rate_mask ..." warning
that occurs on TX when you've selected a rate mask that's not
compatible with the connection (e.g. an AP that enables only the
rates 36, 48, 54 and you've selected only 6, 9, 12.)
Reported-by: Kirtika Ruchandani <kirtika@google.com>
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2017-03-08 11:12:10 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
wifi: mac80211: move some future per-link data to bss_conf
To add MLD, reuse the bss_conf structure later for per-link
information, so move some things into it that are per link.
Most transformations were done with the following spatch:
@@
expression sdata;
identifier var = { chanctx_conf, mu_mimo_owner, csa_active, color_change_active, color_change_color };
@@
-sdata->vif.var
+sdata->vif.bss_conf.var
@@
struct ieee80211_vif *vif;
identifier var = { chanctx_conf, mu_mimo_owner, csa_active, color_change_active, color_change_color };
@@
-vif->var
+vif->bss_conf.var
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2022-05-10 13:26:44 +02:00
|
|
|
|
wifi: mac80211: introduce 'channel request'
For channel contexts, mac80211 currently uses the cfg80211
chandef struct (control channel, center freq(s), width) to
define towards drivers and internally how these behave. In
fact, there are _two_ such structs used, where the min_def
can reduce bandwidth according to the stations connected.
Unfortunately, with EHT this is longer be sufficient, at
least not for all hardware. EHT requires that non-AP STAs
that are connected to an AP with a lower bandwidth than it
(the AP) advertises (e.g. 160 MHz STA connected to 320 MHz
AP) still be able to receive downlink OFDMA and respond to
trigger frames for uplink OFDMA that specify the position
and bandwidth for the non-AP STA relative to the channel
the AP is using. Therefore, they need to be aware of this,
and at least for some hardware (e.g. Intel) this awareness
is in the hardware. As a result, use of the "same" channel
may need to be split over two channel contexts where they
differ by the AP being used.
As a first step, introduce a concept of a channel request
('chanreq') for each interface, to control the context it
requests. This step does nothing but reorganise the code,
so that later the AP's chandef can be added to the request
in order to handle the EHT case described above.
Link: https://msgid.link/20240129194108.2e88e48bd2e9.I4256183debe975c5ed71621611206fdbb69ba330@changeid
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2024-01-29 19:34:40 +01:00
|
|
|
|
mac80211: reject/clear user rate mask if not usable
If the user rate mask results in no (basic) rates being usable,
clear it. Also, if we're already operating when it's set, reject
it instead.
Technically, selecting basic rates as the criterion is a bit too
restrictive, but calculating the usable rates over all stations
(e.g. in AP mode) is harder, and all stations must support the
basic rates. Similarly, in client mode, the basic rates will be
used anyway for control frames.
This fixes the "no supported rates (...) in rate_mask ..." warning
that occurs on TX when you've selected a rate mask that's not
compatible with the connection (e.g. an AP that enables only the
rates 36, 48, 54 and you've selected only 6, 9, 12.)
Reported-by: Kirtika Ruchandani <kirtika@google.com>
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2017-03-08 11:12:10 +01:00
|
|
|
|
wifi: mac80211: introduce 'channel request'
For channel contexts, mac80211 currently uses the cfg80211
chandef struct (control channel, center freq(s), width) to
define towards drivers and internally how these behave. In
fact, there are _two_ such structs used, where the min_def
can reduce bandwidth according to the stations connected.
Unfortunately, with EHT this is longer be sufficient, at
least not for all hardware. EHT requires that non-AP STAs
that are connected to an AP with a lower bandwidth than it
(the AP) advertises (e.g. 160 MHz STA connected to 320 MHz
AP) still be able to receive downlink OFDMA and respond to
trigger frames for uplink OFDMA that specify the position
and bandwidth for the non-AP STA relative to the channel
the AP is using. Therefore, they need to be aware of this,
and at least for some hardware (e.g. Intel) this awareness
is in the hardware. As a result, use of the "same" channel
may need to be split over two channel contexts where they
differ by the AP being used.
As a first step, introduce a concept of a channel request
('chanreq') for each interface, to control the context it
requests. This step does nothing but reorganise the code,
so that later the AP's chandef can be added to the request
in order to handle the EHT case described above.
Link: https://msgid.link/20240129194108.2e88e48bd2e9.I4256183debe975c5ed71621611206fdbb69ba330@changeid
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2024-01-29 19:34:40 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
mac80211: reject/clear user rate mask if not usable
If the user rate mask results in no (basic) rates being usable,
clear it. Also, if we're already operating when it's set, reject
it instead.
Technically, selecting basic rates as the criterion is a bit too
restrictive, but calculating the usable rates over all stations
(e.g. in AP mode) is harder, and all stations must support the
basic rates. Similarly, in client mode, the basic rates will be
used anyway for control frames.
This fixes the "no supported rates (...) in rate_mask ..." warning
that occurs on TX when you've selected a rate mask that's not
compatible with the connection (e.g. an AP that enables only the
rates 36, 48, 54 and you've selected only 6, 9, 12.)
Reported-by: Kirtika Ruchandani <kirtika@google.com>
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2017-03-08 11:12:10 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-10-18 09:36:51 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-04-12 15:56:15 +02:00
|
|
|
|
2013-04-16 13:38:42 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-01-06 13:09:08 +02:00
|
|
|
|
2013-12-05 10:02:15 +01:00
|
|
|
|
|
|
|
|
|
2015-08-06 23:47:33 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-04-16 13:38:42 +02:00
|
|
|
|
|
|
|
|
|
2015-08-06 23:47:33 +02:00
|
|
|
|
2013-04-16 13:38:42 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-08-06 23:47:33 +02:00
|
|
|
|
2021-02-12 11:22:14 +01:00
|
|
|
|
2013-04-16 13:38:42 +02:00
|
|
|
|
|
|
|
|
|
2015-08-21 14:07:13 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-02-12 11:22:14 +01:00
|
|
|
|
2015-08-21 14:07:13 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-08-06 23:47:33 +02:00
|
|
|
|
2012-01-28 17:25:33 +01:00
|
|
|
|
2009-07-01 21:26:59 +02:00
|
|
|
|
2010-01-06 13:09:08 +02:00
|
|
|
|
2009-07-01 21:26:59 +02:00
|
|
|
|
|
|
|
|
|
2025-05-27 14:11:44 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-02-08 18:16:20 +01:00
|
|
|
|
|
|
|
|
|
2014-02-21 19:46:13 +01:00
|
|
|
|
2024-09-06 12:14:23 +05:30
|
|
|
|
2013-02-08 18:16:20 +01:00
|
|
|
|
|
|
|
|
|
wifi: mac80211: introduce 'channel request'
For channel contexts, mac80211 currently uses the cfg80211
chandef struct (control channel, center freq(s), width) to
define towards drivers and internally how these behave. In
fact, there are _two_ such structs used, where the min_def
can reduce bandwidth according to the stations connected.
Unfortunately, with EHT this is longer be sufficient, at
least not for all hardware. EHT requires that non-AP STAs
that are connected to an AP with a lower bandwidth than it
(the AP) advertises (e.g. 160 MHz STA connected to 320 MHz
AP) still be able to receive downlink OFDMA and respond to
trigger frames for uplink OFDMA that specify the position
and bandwidth for the non-AP STA relative to the channel
the AP is using. Therefore, they need to be aware of this,
and at least for some hardware (e.g. Intel) this awareness
is in the hardware. As a result, use of the "same" channel
may need to be split over two channel contexts where they
differ by the AP being used.
As a first step, introduce a concept of a channel request
('chanreq') for each interface, to control the context it
requests. This step does nothing but reorganise the code,
so that later the AP's chandef can be added to the request
in order to handle the EHT case described above.
Link: https://msgid.link/20240129194108.2e88e48bd2e9.I4256183debe975c5ed71621611206fdbb69ba330@changeid
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2024-01-29 19:34:40 +01:00
|
|
|
|
2013-02-08 18:16:20 +01:00
|
|
|
|
2024-09-06 12:14:24 +05:30
|
|
|
|
2013-02-08 18:16:20 +01:00
|
|
|
|
|
|
|
|
|
2023-08-28 14:00:05 +02:00
|
|
|
|
|
|
|
|
|
2025-05-27 14:11:44 +05:30
|
|
|
|
2024-09-06 12:14:20 +05:30
|
|
|
|
2013-02-08 18:16:20 +01:00
|
|
|
|
2024-09-06 12:14:24 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-02-08 18:16:20 +01:00
|
|
|
|
2024-09-06 12:14:24 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-05-30 18:35:23 +02:00
|
|
|
|
2013-02-08 18:16:20 +01:00
|
|
|
|
2024-09-06 12:14:20 +05:30
|
|
|
|
2013-02-08 18:16:20 +01:00
|
|
|
|
2026-01-30 09:25:11 +05:30
|
|
|
|
|
|
|
|
|
2013-02-08 18:16:20 +01:00
|
|
|
|
2024-09-06 12:14:20 +05:30
|
|
|
|
2013-02-08 18:16:20 +01:00
|
|
|
|
|
|
|
|
|
2019-12-22 14:55:31 +00:00
|
|
|
|
2024-09-06 12:14:23 +05:30
|
|
|
|
2019-12-22 14:55:31 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-09-06 12:14:24 +05:30
|
|
|
|
2019-12-22 14:55:31 +00:00
|
|
|
|
2023-08-28 14:00:05 +02:00
|
|
|
|
|
|
|
|
|
2019-12-22 14:55:31 +00:00
|
|
|
|
2024-09-06 12:14:24 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-12-22 14:55:31 +00:00
|
|
|
|
2026-01-30 09:25:11 +05:30
|
|
|
|
2024-09-06 12:14:24 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-12-22 14:55:31 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-07-11 16:09:06 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-12-05 16:50:37 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-03-23 04:38:01 -07:00
|
|
|
|
2022-12-05 16:50:37 -08:00
|
|
|
|
2013-07-11 16:09:06 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-02-24 12:54:58 +01:00
|
|
|
|
|
|
|
|
|
treewide: Replace kmalloc with kmalloc_obj for non-scalar types
This is the result of running the Coccinelle script from
scripts/coccinelle/api/kmalloc_objs.cocci. The script is designed to
avoid scalar types (which need careful case-by-case checking), and
instead replace kmalloc-family calls that allocate struct or union
object instances:
Single allocations: kmalloc(sizeof(TYPE), ...)
are replaced with: kmalloc_obj(TYPE, ...)
Array allocations: kmalloc_array(COUNT, sizeof(TYPE), ...)
are replaced with: kmalloc_objs(TYPE, COUNT, ...)
Flex array allocations: kmalloc(struct_size(PTR, FAM, COUNT), ...)
are replaced with: kmalloc_flex(*PTR, FAM, COUNT, ...)
(where TYPE may also be *VAR)
The resulting allocations no longer return "void *", instead returning
"TYPE *".
Signed-off-by: Kees Cook <kees@kernel.org>
2026-02-20 23:49:23 -08:00
|
|
|
|
Convert remaining multi-line kmalloc_obj/flex GFP_KERNEL uses
Conversion performed via this Coccinelle script:
// SPDX-License-Identifier: GPL-2.0-only
// Options: --include-headers-for-types --all-includes --include-headers --keep-comments
virtual patch
@gfp depends on patch && !(file in "tools") && !(file in "samples")@
identifier ALLOC = {kmalloc_obj,kmalloc_objs,kmalloc_flex,
kzalloc_obj,kzalloc_objs,kzalloc_flex,
kvmalloc_obj,kvmalloc_objs,kvmalloc_flex,
kvzalloc_obj,kvzalloc_objs,kvzalloc_flex};
@@
ALLOC(...
- , GFP_KERNEL
)
$ make coccicheck MODE=patch COCCI=gfp.cocci
Build and boot tested x86_64 with Fedora 42's GCC and Clang:
Linux version 6.19.0+ (user@host) (gcc (GCC) 15.2.1 20260123 (Red Hat 15.2.1-7), GNU ld version 2.44-12.fc42) #1 SMP PREEMPT_DYNAMIC 1970-01-01
Linux version 6.19.0+ (user@host) (clang version 20.1.8 (Fedora 20.1.8-4.fc42), LLD 20.1.8) #1 SMP PREEMPT_DYNAMIC 1970-01-01
Signed-off-by: Kees Cook <kees@kernel.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2026-02-21 23:46:04 -08:00
|
|
|
|
2022-02-24 12:54:58 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-03-23 04:38:01 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
treewide: Replace kmalloc with kmalloc_obj for non-scalar types
This is the result of running the Coccinelle script from
scripts/coccinelle/api/kmalloc_objs.cocci. The script is designed to
avoid scalar types (which need careful case-by-case checking), and
instead replace kmalloc-family calls that allocate struct or union
object instances:
Single allocations: kmalloc(sizeof(TYPE), ...)
are replaced with: kmalloc_obj(TYPE, ...)
Array allocations: kmalloc_array(COUNT, sizeof(TYPE), ...)
are replaced with: kmalloc_objs(TYPE, COUNT, ...)
Flex array allocations: kmalloc(struct_size(PTR, FAM, COUNT), ...)
are replaced with: kmalloc_flex(*PTR, FAM, COUNT, ...)
(where TYPE may also be *VAR)
The resulting allocations no longer return "void *", instead returning
"TYPE *".
Signed-off-by: Kees Cook <kees@kernel.org>
2026-02-20 23:49:23 -08:00
|
|
|
|
Convert remaining multi-line kmalloc_obj/flex GFP_KERNEL uses
Conversion performed via this Coccinelle script:
// SPDX-License-Identifier: GPL-2.0-only
// Options: --include-headers-for-types --all-includes --include-headers --keep-comments
virtual patch
@gfp depends on patch && !(file in "tools") && !(file in "samples")@
identifier ALLOC = {kmalloc_obj,kmalloc_objs,kmalloc_flex,
kzalloc_obj,kzalloc_objs,kzalloc_flex,
kvmalloc_obj,kvmalloc_objs,kvmalloc_flex,
kvzalloc_obj,kvzalloc_objs,kvzalloc_flex};
@@
ALLOC(...
- , GFP_KERNEL
)
$ make coccicheck MODE=patch COCCI=gfp.cocci
Build and boot tested x86_64 with Fedora 42's GCC and Clang:
Linux version 6.19.0+ (user@host) (gcc (GCC) 15.2.1 20260123 (Red Hat 15.2.1-7), GNU ld version 2.44-12.fc42) #1 SMP PREEMPT_DYNAMIC 1970-01-01
Linux version 6.19.0+ (user@host) (clang version 20.1.8 (Fedora 20.1.8-4.fc42), LLD 20.1.8) #1 SMP PREEMPT_DYNAMIC 1970-01-01
Signed-off-by: Kees Cook <kees@kernel.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2026-02-21 23:46:04 -08:00
|
|
|
|
2023-03-23 04:38:01 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-02-24 12:54:58 +01:00
|
|
|
|
|
|
|
|
|
2013-07-11 16:09:06 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-02-02 16:31:23 +01:00
|
|
|
|
2013-07-11 16:09:06 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-03-23 04:38:01 -07:00
|
|
|
|
2022-02-24 12:54:58 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-03-23 04:38:01 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-10-30 09:17:45 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-10-03 20:19:20 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-07-11 16:09:06 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-01-30 19:39:18 +05:30
|
|
|
|
mac80211: only set CSA beacon when at least one beacon must be transmitted
A beacon should never have a Channel Switch Announcement information
element with a count of 0, because a count of 1 means switch just
before the next beacon. So, if a count of 0 was valid in a beacon, it
would have been transmitted in the next channel already, which is
useless. A CSA count equal to zero is only meaningful in action
frames or probe_responses.
Fix the ieee80211_csa_is_complete() and ieee80211_update_csa()
functions accordingly.
With a CSA count of 0, we won't transmit any CSA beacons, because the
switch will happen before the next TBTT. To avoid extra work and
potential confusion in the drivers, complete the CSA immediately,
instead of waiting for the driver to call ieee80211_csa_finish().
To keep things simpler, we also switch immediately when the CSA count
is 1, while in theory we should delay the switch until just before the
next TBTT.
Additionally, move the ieee80211_csa_finish() function to cfg.c,
where it makes more sense.
Tested-by: Simon Wunderlich <sw@simonwunderlich.de>
Acked-by: Simon Wunderlich <sw@simonwunderlich.de>
Signed-off-by: Luciano Coelho <luciano.coelho@intel.com>
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2014-01-13 19:43:00 +02:00
|
|
|
|
|
|
|
|
|
2022-02-24 12:54:59 +01:00
|
|
|
|
2025-04-08 11:45:00 -07:00
|
|
|
|
2024-01-30 19:39:18 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
mac80211: only set CSA beacon when at least one beacon must be transmitted
A beacon should never have a Channel Switch Announcement information
element with a count of 0, because a count of 1 means switch just
before the next beacon. So, if a count of 0 was valid in a beacon, it
would have been transmitted in the next channel already, which is
useless. A CSA count equal to zero is only meaningful in action
frames or probe_responses.
Fix the ieee80211_csa_is_complete() and ieee80211_update_csa()
functions accordingly.
With a CSA count of 0, we won't transmit any CSA beacons, because the
switch will happen before the next TBTT. To avoid extra work and
potential confusion in the drivers, complete the CSA immediately,
instead of waiting for the driver to call ieee80211_csa_finish().
To keep things simpler, we also switch immediately when the CSA count
is 1, while in theory we should delay the switch until just before the
next TBTT.
Additionally, move the ieee80211_csa_finish() function to cfg.c,
where it makes more sense.
Tested-by: Simon Wunderlich <sw@simonwunderlich.de>
Acked-by: Simon Wunderlich <sw@simonwunderlich.de>
Signed-off-by: Luciano Coelho <luciano.coelho@intel.com>
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2014-01-13 19:43:00 +02:00
|
|
|
|
2022-02-24 12:54:59 +01:00
|
|
|
|
|
|
|
|
|
2024-01-30 19:39:18 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-04-08 11:45:00 -07:00
|
|
|
|
|
|
|
|
|
2022-02-24 12:54:59 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-04-08 11:45:00 -07:00
|
|
|
|
2022-02-24 12:54:59 +01:00
|
|
|
|
2025-07-11 09:08:46 +05:30
|
|
|
|
2025-04-08 11:45:00 -07:00
|
|
|
|
|
|
|
|
|
2022-02-24 12:54:59 +01:00
|
|
|
|
|
|
|
|
|
2025-04-08 11:45:00 -07:00
|
|
|
|
|
|
|
|
|
2022-02-24 12:54:59 +01:00
|
|
|
|
|
|
|
|
|
2025-04-08 11:45:00 -07:00
|
|
|
|
2024-05-06 21:54:49 +02:00
|
|
|
|
2022-02-24 12:54:59 +01:00
|
|
|
|
|
|
|
|
|
mac80211: only set CSA beacon when at least one beacon must be transmitted
A beacon should never have a Channel Switch Announcement information
element with a count of 0, because a count of 1 means switch just
before the next beacon. So, if a count of 0 was valid in a beacon, it
would have been transmitted in the next channel already, which is
useless. A CSA count equal to zero is only meaningful in action
frames or probe_responses.
Fix the ieee80211_csa_is_complete() and ieee80211_update_csa()
functions accordingly.
With a CSA count of 0, we won't transmit any CSA beacons, because the
switch will happen before the next TBTT. To avoid extra work and
potential confusion in the drivers, complete the CSA immediately,
instead of waiting for the driver to call ieee80211_csa_finish().
To keep things simpler, we also switch immediately when the CSA count
is 1, while in theory we should delay the switch until just before the
next TBTT.
Additionally, move the ieee80211_csa_finish() function to cfg.c,
where it makes more sense.
Tested-by: Simon Wunderlich <sw@simonwunderlich.de>
Acked-by: Simon Wunderlich <sw@simonwunderlich.de>
Signed-off-by: Luciano Coelho <luciano.coelho@intel.com>
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2014-01-13 19:43:00 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-11-19 17:35:40 +02:00
|
|
|
|
2021-11-29 15:32:38 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-06 14:49:31 +02:00
|
|
|
|
2021-11-29 15:32:38 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-01-30 19:39:16 +05:30
|
|
|
|
2023-06-04 12:11:26 +03:00
|
|
|
|
2014-04-09 15:11:00 +02:00
|
|
|
|
2024-01-30 19:39:16 +05:30
|
|
|
|
2014-04-09 15:11:00 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-01-30 19:39:16 +05:30
|
|
|
|
2022-04-07 12:36:58 +02:00
|
|
|
|
|
|
|
|
|
2024-01-30 19:39:16 +05:30
|
|
|
|
|
|
|
|
|
2023-06-04 12:11:26 +03:00
|
|
|
|
2024-01-30 19:39:16 +05:30
|
|
|
|
2014-04-09 15:11:00 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-04 12:11:26 +03:00
|
|
|
|
2014-04-09 15:11:00 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-04 12:11:26 +03:00
|
|
|
|
2014-04-09 15:11:00 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-08-28 13:04:10 +03:00
|
|
|
|
2013-07-11 16:09:06 +02:00
|
|
|
|
2023-08-28 13:04:10 +03:00
|
|
|
|
2013-07-11 16:09:06 +02:00
|
|
|
|
2024-01-30 19:39:17 +05:30
|
|
|
|
2023-06-04 12:11:26 +03:00
|
|
|
|
2014-04-09 15:11:00 +02:00
|
|
|
|
2013-07-11 16:09:06 +02:00
|
|
|
|
2023-08-28 14:00:03 +02:00
|
|
|
|
2014-01-29 07:56:21 +01:00
|
|
|
|
2014-06-25 12:35:08 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-07-11 16:09:06 +02:00
|
|
|
|
2023-08-28 13:04:10 +03:00
|
|
|
|
2014-06-25 12:35:08 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-08-28 13:04:10 +03:00
|
|
|
|
2014-06-25 12:35:08 +02:00
|
|
|
|
|
|
|
|
|
2024-01-30 19:39:17 +05:30
|
|
|
|
2013-09-01 17:15:51 +03:00
|
|
|
|
|
|
|
|
|
2024-01-30 19:39:17 +05:30
|
|
|
|
2024-05-06 21:54:49 +02:00
|
|
|
|
2014-06-25 12:35:08 +02:00
|
|
|
|
|
|
|
|
|
2024-01-30 19:39:17 +05:30
|
|
|
|
2014-01-29 07:56:18 +01:00
|
|
|
|
2024-01-30 19:39:17 +05:30
|
|
|
|
2014-04-09 15:11:00 +02:00
|
|
|
|
2014-05-08 09:10:02 +02:00
|
|
|
|
2013-07-11 16:09:06 +02:00
|
|
|
|
2023-08-27 14:05:32 +03:00
|
|
|
|
2014-04-09 15:10:59 +02:00
|
|
|
|
2026-05-29 10:25:08 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-06-12 14:28:35 +02:00
|
|
|
|
2014-05-08 09:10:02 +02:00
|
|
|
|
2023-08-28 13:04:10 +03:00
|
|
|
|
2014-10-08 09:48:38 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-05-06 21:54:49 +02:00
|
|
|
|
2024-01-29 19:34:49 +01:00
|
|
|
|
2014-10-08 09:48:38 +03:00
|
|
|
|
2014-05-08 09:10:02 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-08-28 13:04:10 +03:00
|
|
|
|
2014-05-08 09:10:02 +02:00
|
|
|
|
2023-08-28 13:04:10 +03:00
|
|
|
|
2025-11-27 15:41:24 +05:30
|
|
|
|
2023-08-28 13:04:10 +03:00
|
|
|
|
|
|
|
|
|
2024-01-30 19:39:17 +05:30
|
|
|
|
|
|
|
|
|
2025-11-27 15:41:24 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-05-08 09:10:02 +02:00
|
|
|
|
mac80211: only set CSA beacon when at least one beacon must be transmitted
A beacon should never have a Channel Switch Announcement information
element with a count of 0, because a count of 1 means switch just
before the next beacon. So, if a count of 0 was valid in a beacon, it
would have been transmitted in the next channel already, which is
useless. A CSA count equal to zero is only meaningful in action
frames or probe_responses.
Fix the ieee80211_csa_is_complete() and ieee80211_update_csa()
functions accordingly.
With a CSA count of 0, we won't transmit any CSA beacons, because the
switch will happen before the next TBTT. To avoid extra work and
potential confusion in the drivers, complete the CSA immediately,
instead of waiting for the driver to call ieee80211_csa_finish().
To keep things simpler, we also switch immediately when the CSA count
is 1, while in theory we should delay the switch until just before the
next TBTT.
Additionally, move the ieee80211_csa_finish() function to cfg.c,
where it makes more sense.
Tested-by: Simon Wunderlich <sw@simonwunderlich.de>
Acked-by: Simon Wunderlich <sw@simonwunderlich.de>
Signed-off-by: Luciano Coelho <luciano.coelho@intel.com>
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2014-01-13 19:43:00 +02:00
|
|
|
|
|
|
|
|
|
2023-08-28 13:59:50 +02:00
|
|
|
|
mac80211: only set CSA beacon when at least one beacon must be transmitted
A beacon should never have a Channel Switch Announcement information
element with a count of 0, because a count of 1 means switch just
before the next beacon. So, if a count of 0 was valid in a beacon, it
would have been transmitted in the next channel already, which is
useless. A CSA count equal to zero is only meaningful in action
frames or probe_responses.
Fix the ieee80211_csa_is_complete() and ieee80211_update_csa()
functions accordingly.
With a CSA count of 0, we won't transmit any CSA beacons, because the
switch will happen before the next TBTT. To avoid extra work and
potential confusion in the drivers, complete the CSA immediately,
instead of waiting for the driver to call ieee80211_csa_finish().
To keep things simpler, we also switch immediately when the CSA count
is 1, while in theory we should delay the switch until just before the
next TBTT.
Additionally, move the ieee80211_csa_finish() function to cfg.c,
where it makes more sense.
Tested-by: Simon Wunderlich <sw@simonwunderlich.de>
Acked-by: Simon Wunderlich <sw@simonwunderlich.de>
Signed-off-by: Luciano Coelho <luciano.coelho@intel.com>
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2014-01-13 19:43:00 +02:00
|
|
|
|
2023-08-28 13:04:10 +03:00
|
|
|
|
2024-05-06 21:54:49 +02:00
|
|
|
|
2023-08-28 13:04:10 +03:00
|
|
|
|
2014-04-09 15:10:59 +02:00
|
|
|
|
mac80211: only set CSA beacon when at least one beacon must be transmitted
A beacon should never have a Channel Switch Announcement information
element with a count of 0, because a count of 1 means switch just
before the next beacon. So, if a count of 0 was valid in a beacon, it
would have been transmitted in the next channel already, which is
useless. A CSA count equal to zero is only meaningful in action
frames or probe_responses.
Fix the ieee80211_csa_is_complete() and ieee80211_update_csa()
functions accordingly.
With a CSA count of 0, we won't transmit any CSA beacons, because the
switch will happen before the next TBTT. To avoid extra work and
potential confusion in the drivers, complete the CSA immediately,
instead of waiting for the driver to call ieee80211_csa_finish().
To keep things simpler, we also switch immediately when the CSA count
is 1, while in theory we should delay the switch until just before the
next TBTT.
Additionally, move the ieee80211_csa_finish() function to cfg.c,
where it makes more sense.
Tested-by: Simon Wunderlich <sw@simonwunderlich.de>
Acked-by: Simon Wunderlich <sw@simonwunderlich.de>
Signed-off-by: Luciano Coelho <luciano.coelho@intel.com>
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2014-01-13 19:43:00 +02:00
|
|
|
|
2023-08-28 14:00:03 +02:00
|
|
|
|
2014-04-09 15:10:59 +02:00
|
|
|
|
mac80211: only set CSA beacon when at least one beacon must be transmitted
A beacon should never have a Channel Switch Announcement information
element with a count of 0, because a count of 1 means switch just
before the next beacon. So, if a count of 0 was valid in a beacon, it
would have been transmitted in the next channel already, which is
useless. A CSA count equal to zero is only meaningful in action
frames or probe_responses.
Fix the ieee80211_csa_is_complete() and ieee80211_update_csa()
functions accordingly.
With a CSA count of 0, we won't transmit any CSA beacons, because the
switch will happen before the next TBTT. To avoid extra work and
potential confusion in the drivers, complete the CSA immediately,
instead of waiting for the driver to call ieee80211_csa_finish().
To keep things simpler, we also switch immediately when the CSA count
is 1, while in theory we should delay the switch until just before the
next TBTT.
Additionally, move the ieee80211_csa_finish() function to cfg.c,
where it makes more sense.
Tested-by: Simon Wunderlich <sw@simonwunderlich.de>
Acked-by: Simon Wunderlich <sw@simonwunderlich.de>
Signed-off-by: Luciano Coelho <luciano.coelho@intel.com>
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2014-01-13 19:43:00 +02:00
|
|
|
|
2023-08-28 13:04:10 +03:00
|
|
|
|
2023-08-29 12:18:56 +02:00
|
|
|
|
mac80211: only set CSA beacon when at least one beacon must be transmitted
A beacon should never have a Channel Switch Announcement information
element with a count of 0, because a count of 1 means switch just
before the next beacon. So, if a count of 0 was valid in a beacon, it
would have been transmitted in the next channel already, which is
useless. A CSA count equal to zero is only meaningful in action
frames or probe_responses.
Fix the ieee80211_csa_is_complete() and ieee80211_update_csa()
functions accordingly.
With a CSA count of 0, we won't transmit any CSA beacons, because the
switch will happen before the next TBTT. To avoid extra work and
potential confusion in the drivers, complete the CSA immediately,
instead of waiting for the driver to call ieee80211_csa_finish().
To keep things simpler, we also switch immediately when the CSA count
is 1, while in theory we should delay the switch until just before the
next TBTT.
Additionally, move the ieee80211_csa_finish() function to cfg.c,
where it makes more sense.
Tested-by: Simon Wunderlich <sw@simonwunderlich.de>
Acked-by: Simon Wunderlich <sw@simonwunderlich.de>
Signed-off-by: Luciano Coelho <luciano.coelho@intel.com>
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2014-01-13 19:43:00 +02:00
|
|
|
|
|
|
|
|
|
2023-08-29 12:18:56 +02:00
|
|
|
|
mac80211: only set CSA beacon when at least one beacon must be transmitted
A beacon should never have a Channel Switch Announcement information
element with a count of 0, because a count of 1 means switch just
before the next beacon. So, if a count of 0 was valid in a beacon, it
would have been transmitted in the next channel already, which is
useless. A CSA count equal to zero is only meaningful in action
frames or probe_responses.
Fix the ieee80211_csa_is_complete() and ieee80211_update_csa()
functions accordingly.
With a CSA count of 0, we won't transmit any CSA beacons, because the
switch will happen before the next TBTT. To avoid extra work and
potential confusion in the drivers, complete the CSA immediately,
instead of waiting for the driver to call ieee80211_csa_finish().
To keep things simpler, we also switch immediately when the CSA count
is 1, while in theory we should delay the switch until just before the
next TBTT.
Additionally, move the ieee80211_csa_finish() function to cfg.c,
where it makes more sense.
Tested-by: Simon Wunderlich <sw@simonwunderlich.de>
Acked-by: Simon Wunderlich <sw@simonwunderlich.de>
Signed-off-by: Luciano Coelho <luciano.coelho@intel.com>
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2014-01-13 19:43:00 +02:00
|
|
|
|
2023-08-28 13:04:10 +03:00
|
|
|
|
2013-07-11 16:09:06 +02:00
|
|
|
|
|
|
|
|
|
2024-01-30 19:39:16 +05:30
|
|
|
|
2014-02-28 15:59:06 +01:00
|
|
|
|
2023-06-04 12:11:26 +03:00
|
|
|
|
2014-02-28 15:59:06 +01:00
|
|
|
|
2024-01-30 19:39:16 +05:30
|
|
|
|
2014-06-05 14:21:36 +02:00
|
|
|
|
2014-02-28 15:59:06 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-01-30 19:39:16 +05:30
|
|
|
|
2014-02-28 15:59:06 +01:00
|
|
|
|
2024-01-30 19:39:16 +05:30
|
|
|
|
2014-02-28 15:59:06 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-05-09 14:11:47 +03:00
|
|
|
|
2020-08-11 10:01:04 +02:00
|
|
|
|
2014-05-09 14:11:47 +03:00
|
|
|
|
2022-02-24 12:54:58 +01:00
|
|
|
|
2024-01-30 19:39:16 +05:30
|
|
|
|
2014-05-09 14:11:47 +03:00
|
|
|
|
2022-02-24 12:54:58 +01:00
|
|
|
|
2014-05-09 14:11:46 +03:00
|
|
|
|
2014-06-05 14:21:36 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-05-09 14:11:47 +03:00
|
|
|
|
2024-01-30 19:39:16 +05:30
|
|
|
|
2022-06-17 22:36:37 +02:00
|
|
|
|
2023-06-04 12:11:26 +03:00
|
|
|
|
2014-02-28 15:59:06 +01:00
|
|
|
|
2024-01-30 19:39:16 +05:30
|
|
|
|
2014-02-28 15:59:06 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
wifi: mac80211: move interface config to new struct
We'll use bss_conf for per-link configuration later, so
move out all the non-link-specific data out into a new
struct ieee80211_vif_cfg used in the vif.
Some adjustments were done with the following spatch:
@@
expression sdata;
struct ieee80211_vif *vifp;
identifier var = { assoc, ibss_joined, aid, arp_addr_list, arp_addr_cnt, ssid, ssid_len, s1g, ibss_creator };
@@
(
-sdata->vif.bss_conf.var
+sdata->vif.cfg.var
|
-vifp->bss_conf.var
+vifp->cfg.var
)
@bss_conf@
struct ieee80211_bss_conf *bss_conf;
identifier var = { assoc, ibss_joined, aid, arp_addr_list, arp_addr_cnt, ssid, ssid_len, s1g, ibss_creator };
@@
-bss_conf->var
+vif_cfg->var
(though more manual fixups were needed, e.g. replacing
"vif_cfg->" by "vif->cfg." in many files.)
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2022-05-10 17:05:04 +02:00
|
|
|
|
2014-02-28 15:59:06 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-11-20 12:36:45 -06:00
|
|
|
|
2014-02-28 15:59:06 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-04 12:11:26 +03:00
|
|
|
|
2014-02-28 15:59:06 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
wifi: mac80211: introduce 'channel request'
For channel contexts, mac80211 currently uses the cfg80211
chandef struct (control channel, center freq(s), width) to
define towards drivers and internally how these behave. In
fact, there are _two_ such structs used, where the min_def
can reduce bandwidth according to the stations connected.
Unfortunately, with EHT this is longer be sufficient, at
least not for all hardware. EHT requires that non-AP STAs
that are connected to an AP with a lower bandwidth than it
(the AP) advertises (e.g. 160 MHz STA connected to 320 MHz
AP) still be able to receive downlink OFDMA and respond to
trigger frames for uplink OFDMA that specify the position
and bandwidth for the non-AP STA relative to the channel
the AP is using. Therefore, they need to be aware of this,
and at least for some hardware (e.g. Intel) this awareness
is in the hardware. As a result, use of the "same" channel
may need to be split over two channel contexts where they
differ by the AP being used.
As a first step, introduce a concept of a channel request
('chanreq') for each interface, to control the context it
requests. This step does nothing but reorganise the code,
so that later the AP's chandef can be added to the request
in order to handle the EHT case described above.
Link: https://msgid.link/20240129194108.2e88e48bd2e9.I4256183debe975c5ed71621611206fdbb69ba330@changeid
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2024-01-29 19:34:40 +01:00
|
|
|
|
2014-02-28 15:59:06 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-04 12:11:26 +03:00
|
|
|
|
2014-02-28 15:59:06 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-04-22 11:04:08 +05:30
|
|
|
|
2021-07-02 19:44:08 +02:00
|
|
|
|
2024-04-22 11:04:08 +05:30
|
|
|
|
2022-05-16 12:57:32 +02:00
|
|
|
|
2024-04-22 11:04:08 +05:30
|
|
|
|
2021-07-02 19:44:08 +02:00
|
|
|
|
2024-04-22 11:04:08 +05:30
|
|
|
|
2021-07-02 19:44:08 +02:00
|
|
|
|
|
|
|
|
|
2014-05-07 20:05:12 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-07-11 16:09:06 +02:00
|
|
|
|
|
|
|
|
|
2026-04-28 11:25:37 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-07-11 16:09:06 +02:00
|
|
|
|
2024-02-28 09:55:43 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-04-09 15:29:32 +02:00
|
|
|
|
2013-07-11 16:09:06 +02:00
|
|
|
|
2024-01-30 19:39:17 +05:30
|
|
|
|
|
|
|
|
|
2023-06-04 12:11:26 +03:00
|
|
|
|
2024-01-30 19:39:17 +05:30
|
|
|
|
2014-10-20 21:36:04 +02:00
|
|
|
|
2013-07-11 16:09:06 +02:00
|
|
|
|
2023-08-28 14:00:03 +02:00
|
|
|
|
2013-11-21 18:19:50 +01:00
|
|
|
|
2025-05-27 14:11:44 +05:30
|
|
|
|
2013-07-11 16:09:06 +02:00
|
|
|
|
|
|
|
|
|
2024-09-06 12:14:25 +05:30
|
|
|
|
2013-07-11 16:09:06 +02:00
|
|
|
|
|
|
|
|
|
2024-01-30 19:39:17 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-01-29 19:34:49 +01:00
|
|
|
|
|
|
|
|
|
2013-07-11 16:09:06 +02:00
|
|
|
|
2024-01-30 19:39:17 +05:30
|
|
|
|
2013-07-11 16:09:06 +02:00
|
|
|
|
|
|
|
|
|
2024-01-30 19:39:17 +05:30
|
|
|
|
2014-06-25 12:35:08 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-04-01 18:18:04 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-07-10 11:04:28 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-06-25 12:35:08 +02:00
|
|
|
|
|
|
|
|
|
2014-11-07 15:28:33 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
wifi: mac80211: introduce 'channel request'
For channel contexts, mac80211 currently uses the cfg80211
chandef struct (control channel, center freq(s), width) to
define towards drivers and internally how these behave. In
fact, there are _two_ such structs used, where the min_def
can reduce bandwidth according to the stations connected.
Unfortunately, with EHT this is longer be sufficient, at
least not for all hardware. EHT requires that non-AP STAs
that are connected to an AP with a lower bandwidth than it
(the AP) advertises (e.g. 160 MHz STA connected to 320 MHz
AP) still be able to receive downlink OFDMA and respond to
trigger frames for uplink OFDMA that specify the position
and bandwidth for the non-AP STA relative to the channel
the AP is using. Therefore, they need to be aware of this,
and at least for some hardware (e.g. Intel) this awareness
is in the hardware. As a result, use of the "same" channel
may need to be split over two channel contexts where they
differ by the AP being used.
As a first step, introduce a concept of a channel request
('chanreq') for each interface, to control the context it
requests. This step does nothing but reorganise the code,
so that later the AP's chandef can be added to the request
in order to handle the EHT case described above.
Link: https://msgid.link/20240129194108.2e88e48bd2e9.I4256183debe975c5ed71621611206fdbb69ba330@changeid
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2024-01-29 19:34:40 +01:00
|
|
|
|
2014-11-07 15:28:33 +02:00
|
|
|
|
|
|
|
|
|
2014-10-08 09:48:37 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-01-30 19:39:17 +05:30
|
|
|
|
2022-05-30 18:35:23 +02:00
|
|
|
|
|
|
|
|
|
2014-06-25 12:35:08 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-01-11 19:25:32 +02:00
|
|
|
|
2014-06-25 12:35:08 +02:00
|
|
|
|
2024-01-30 19:39:17 +05:30
|
|
|
|
2014-06-25 12:35:08 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-07-02 19:44:08 +02:00
|
|
|
|
2024-01-30 19:39:17 +05:30
|
|
|
|
2024-04-22 11:04:08 +05:30
|
|
|
|
2021-07-02 19:44:08 +02:00
|
|
|
|
2024-01-30 19:39:17 +05:30
|
|
|
|
2014-06-25 12:35:08 +02:00
|
|
|
|
2024-01-30 19:39:17 +05:30
|
|
|
|
2014-06-25 12:35:08 +02:00
|
|
|
|
|
|
|
|
|
2013-07-11 16:09:06 +02:00
|
|
|
|
2024-05-06 21:54:49 +02:00
|
|
|
|
2024-01-30 19:39:17 +05:30
|
|
|
|
2013-07-11 16:09:06 +02:00
|
|
|
|
2024-06-12 14:28:35 +02:00
|
|
|
|
|
|
|
|
|
2014-04-09 15:10:59 +02:00
|
|
|
|
2022-05-16 15:00:15 +02:00
|
|
|
|
wireless-next patches for v6.11
The first "new features" pull request for v6.11 with changes both in
stack and in drivers. Nothing out of ordinary, except that we have two
conflicts this time:
CONFLICT (content): Merge conflict in net/mac80211/cfg.c
CONFLICT (content): Merge conflict in drivers/net/wireless/microchip/wilc1000/netdev.c
Here are Stephen's resolutions for them:
https://lore.kernel.org/all/20240531124415.05b25e7a@canb.auug.org.au/
https://lore.kernel.org/all/20240603110023.23572803@canb.auug.org.au/
Major changes:
cfg80211/mac80211
* parse Transmit Power Envelope (TPE) data in mac80211 instead of in drivers
wilc1000
* read MAC address during probe to make it visible to user space
iwlwifi
* bump FW API to 91 for BZ/SC devices
* report 64-bit radiotap timestamp
* Enable P2P low latency by default
* handle Transmit Power Envelope (TPE) advertised by AP
* start using guard()
rtlwifi
* RTL8192DU support
ath12k
* remove unsupported tx monitor handling
* channel 2 in 6 GHz band support
* Spatial Multiplexing Power Save (SMPS) in 6 GHz band support
* multiple BSSID (MBSSID) and Enhanced Multi-BSSID Advertisements (EMA) support
* dynamic VLAN support
* add panic handler for resetting the firmware state
ath10k
* add qcom,no-msa-ready-indicator Device Tree property
* LED support for various chipsets
-----BEGIN PGP SIGNATURE-----
iQFFBAABCgAvFiEEiBjanGPFTz4PRfLobhckVSbrbZsFAmZi07URHGt2YWxvQGtl
cm5lbC5vcmcACgkQbhckVSbrbZu3/QgAo7jyKgvpwMaNIVRLyfYCo0r3Q9wb7QPd
QeRNsftYxlWpPTJ4+Y95aZupy91Ay+RaEQXbbtl7PMIiyQrs7wb4V4Iqzedkws3t
DZsR5BitH+1BIGY0Omo0fiSB5HlWEwZGUj6inqlgKHpBtdIVTANSMjuwkdoMAV5y
ZU57axIGToySvDbRlhJQW833Nnh4KnaseA+TtyfXSaBVerzbshkjBr0d9pMBMiH9
irMQW5CW+7fbxp3OCNsKxX4eG6MFGmm/uP1hFmeYQi2qzUE4SddHMeV4I6oNKOrH
vFB+ZVmYvOjJUYsNhlCUe6Vy+EKwvmfiDWwE1egelEkgozCixJXAAQ==
=QT4C
-----END PGP SIGNATURE-----
Merge tag 'wireless-next-2024-06-07' of git://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless-next
Kalle Valo says:
====================
wireless-next patches for v6.11
The first "new features" pull request for v6.11 with changes both in
stack and in drivers. Nothing out of ordinary, except that we have
two conflicts this time:
net/mac80211/cfg.c
https://lore.kernel.org/all/20240531124415.05b25e7a@canb.auug.org.au
drivers/net/wireless/microchip/wilc1000/netdev.c
https://lore.kernel.org/all/20240603110023.23572803@canb.auug.org.au
Major changes:
cfg80211/mac80211
* parse Transmit Power Envelope (TPE) data in mac80211 instead of in drivers
wilc1000
* read MAC address during probe to make it visible to user space
iwlwifi
* bump FW API to 91 for BZ/SC devices
* report 64-bit radiotap timestamp
* enable P2P low latency by default
* handle Transmit Power Envelope (TPE) advertised by AP
* start using guard()
rtlwifi
* RTL8192DU support
ath12k
* remove unsupported tx monitor handling
* channel 2 in 6 GHz band support
* Spatial Multiplexing Power Save (SMPS) in 6 GHz band support
* multiple BSSID (MBSSID) and Enhanced Multi-BSSID Advertisements (EMA)
support
* dynamic VLAN support
* add panic handler for resetting the firmware state
ath10k
* add qcom,no-msa-ready-indicator Device Tree property
* LED support for various chipsets
* tag 'wireless-next-2024-06-07' of git://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless-next: (194 commits)
wifi: ath12k: add hw_link_id in ath12k_pdev
wifi: ath12k: add panic handler
wifi: rtw89: chan: Use swap() in rtw89_swap_sub_entity()
wifi: brcm80211: remove unused structs
wifi: brcm80211: use sizeof(*pointer) instead of sizeof(type)
wifi: ath12k: do not process consecutive RDDM event
dt-bindings: net: wireless: ath11k: Drop "qcom,ipq8074-wcss-pil" from example
wifi: ath12k: fix memory leak in ath12k_dp_rx_peer_frag_setup()
wifi: rtlwifi: handle return value of usb init TX/RX
wifi: rtlwifi: Enable the new rtl8192du driver
wifi: rtlwifi: Add rtl8192du/sw.c
wifi: rtlwifi: Constify rtl_hal_cfg.{ops,usb_interface_cfg} and rtl_priv.cfg
wifi: rtlwifi: Add rtl8192du/dm.{c,h}
wifi: rtlwifi: Add rtl8192du/fw.{c,h} and rtl8192du/led.{c,h}
wifi: rtlwifi: Add rtl8192du/rf.{c,h}
wifi: rtlwifi: Add rtl8192du/trx.{c,h}
wifi: rtlwifi: Add rtl8192du/phy.{c,h}
wifi: rtlwifi: Add rtl8192du/hw.{c,h}
wifi: rtlwifi: Add new members to struct rtl_priv for RTL8192DU
wifi: rtlwifi: Add rtl8192du/table.{c,h}
...
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
====================
Link: https://lore.kernel.org/r/20240607093517.41394C2BBFC@smtp.kernel.org
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
2024-06-10 17:40:25 -07:00
|
|
|
|
2024-01-29 19:34:49 +01:00
|
|
|
|
2014-11-07 14:31:36 +02:00
|
|
|
|
mac80211: only set CSA beacon when at least one beacon must be transmitted
A beacon should never have a Channel Switch Announcement information
element with a count of 0, because a count of 1 means switch just
before the next beacon. So, if a count of 0 was valid in a beacon, it
would have been transmitted in the next channel already, which is
useless. A CSA count equal to zero is only meaningful in action
frames or probe_responses.
Fix the ieee80211_csa_is_complete() and ieee80211_update_csa()
functions accordingly.
With a CSA count of 0, we won't transmit any CSA beacons, because the
switch will happen before the next TBTT. To avoid extra work and
potential confusion in the drivers, complete the CSA immediately,
instead of waiting for the driver to call ieee80211_csa_finish().
To keep things simpler, we also switch immediately when the CSA count
is 1, while in theory we should delay the switch until just before the
next TBTT.
Additionally, move the ieee80211_csa_finish() function to cfg.c,
where it makes more sense.
Tested-by: Simon Wunderlich <sw@simonwunderlich.de>
Acked-by: Simon Wunderlich <sw@simonwunderlich.de>
Signed-off-by: Luciano Coelho <luciano.coelho@intel.com>
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2014-01-13 19:43:00 +02:00
|
|
|
|
2024-01-30 19:39:17 +05:30
|
|
|
|
2024-05-06 21:54:49 +02:00
|
|
|
|
mac80211: only set CSA beacon when at least one beacon must be transmitted
A beacon should never have a Channel Switch Announcement information
element with a count of 0, because a count of 1 means switch just
before the next beacon. So, if a count of 0 was valid in a beacon, it
would have been transmitted in the next channel already, which is
useless. A CSA count equal to zero is only meaningful in action
frames or probe_responses.
Fix the ieee80211_csa_is_complete() and ieee80211_update_csa()
functions accordingly.
With a CSA count of 0, we won't transmit any CSA beacons, because the
switch will happen before the next TBTT. To avoid extra work and
potential confusion in the drivers, complete the CSA immediately,
instead of waiting for the driver to call ieee80211_csa_finish().
To keep things simpler, we also switch immediately when the CSA count
is 1, while in theory we should delay the switch until just before the
next TBTT.
Additionally, move the ieee80211_csa_finish() function to cfg.c,
where it makes more sense.
Tested-by: Simon Wunderlich <sw@simonwunderlich.de>
Acked-by: Simon Wunderlich <sw@simonwunderlich.de>
Signed-off-by: Luciano Coelho <luciano.coelho@intel.com>
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2014-01-13 19:43:00 +02:00
|
|
|
|
|
|
|
|
|
2024-01-30 19:39:17 +05:30
|
|
|
|
mac80211: only set CSA beacon when at least one beacon must be transmitted
A beacon should never have a Channel Switch Announcement information
element with a count of 0, because a count of 1 means switch just
before the next beacon. So, if a count of 0 was valid in a beacon, it
would have been transmitted in the next channel already, which is
useless. A CSA count equal to zero is only meaningful in action
frames or probe_responses.
Fix the ieee80211_csa_is_complete() and ieee80211_update_csa()
functions accordingly.
With a CSA count of 0, we won't transmit any CSA beacons, because the
switch will happen before the next TBTT. To avoid extra work and
potential confusion in the drivers, complete the CSA immediately,
instead of waiting for the driver to call ieee80211_csa_finish().
To keep things simpler, we also switch immediately when the CSA count
is 1, while in theory we should delay the switch until just before the
next TBTT.
Additionally, move the ieee80211_csa_finish() function to cfg.c,
where it makes more sense.
Tested-by: Simon Wunderlich <sw@simonwunderlich.de>
Acked-by: Simon Wunderlich <sw@simonwunderlich.de>
Signed-off-by: Luciano Coelho <luciano.coelho@intel.com>
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2014-01-13 19:43:00 +02:00
|
|
|
|
2013-07-11 16:09:06 +02:00
|
|
|
|
2014-06-25 12:35:08 +02:00
|
|
|
|
|
|
|
|
|
2013-07-11 16:09:06 +02:00
|
|
|
|
|
|
|
|
|
2014-04-09 15:10:59 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-08-28 14:00:05 +02:00
|
|
|
|
2014-04-09 15:10:59 +02:00
|
|
|
|
2023-08-28 14:00:05 +02:00
|
|
|
|
2014-04-09 15:10:59 +02:00
|
|
|
|
|
|
|
|
|
2015-11-23 17:18:35 +01:00
|
|
|
|
|
|
|
|
|
2023-08-28 14:00:05 +02:00
|
|
|
|
2015-11-23 17:18:35 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-11-24 14:25:49 +01:00
|
|
|
|
|
|
|
|
|
2015-06-01 23:14:59 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-11-24 14:25:49 +01:00
|
|
|
|
2015-06-01 23:14:59 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-01-15 12:25:50 +01:00
|
|
|
|
2015-06-01 23:14:59 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-11-24 14:25:49 +01:00
|
|
|
|
2015-06-01 23:14:59 +02:00
|
|
|
|
|
|
|
|
|
2023-08-28 15:09:24 +02:00
|
|
|
|
|
|
|
|
|
2015-06-01 23:14:59 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-11-24 14:25:49 +01:00
|
|
|
|
2015-06-01 23:14:59 +02:00
|
|
|
|
|
|
|
|
|
2020-04-17 12:43:01 +02:00
|
|
|
|
|
|
|
|
|
2012-06-15 15:30:18 +02:00
|
|
|
|
2020-04-17 12:43:01 +02:00
|
|
|
|
2010-10-13 12:06:24 +02:00
|
|
|
|
|
|
|
|
|
2015-08-15 22:39:50 +03:00
|
|
|
|
2020-04-17 12:43:01 +02:00
|
|
|
|
2020-04-21 17:48:15 +03:00
|
|
|
|
2020-04-17 12:43:01 +02:00
|
|
|
|
2010-10-13 12:06:24 +02:00
|
|
|
|
2020-04-17 12:43:01 +02:00
|
|
|
|
2020-04-21 17:48:15 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-04-17 12:43:01 +02:00
|
|
|
|
2020-04-21 17:48:15 +03:00
|
|
|
|
2015-08-15 22:39:50 +03:00
|
|
|
|
2020-04-21 17:48:15 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-04-17 12:43:01 +02:00
|
|
|
|
2020-04-21 17:48:15 +03:00
|
|
|
|
|
|
|
|
|
2010-10-13 12:06:24 +02:00
|
|
|
|
2020-04-17 12:43:01 +02:00
|
|
|
|
|
|
|
|
|
2012-10-31 15:50:34 +01:00
|
|
|
|
2020-04-17 12:43:01 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-08-15 22:39:50 +03:00
|
|
|
|
2020-04-17 12:43:01 +02:00
|
|
|
|
2015-08-15 22:39:50 +03:00
|
|
|
|
2010-10-13 12:06:24 +02:00
|
|
|
|
|
|
|
|
|
2025-06-15 13:53:09 +05:30
|
|
|
|
|
|
|
|
|
2010-11-10 12:50:56 +09:00
|
|
|
|
|
|
|
|
|
2023-09-20 21:25:13 +03:00
|
|
|
|
2010-11-10 12:50:56 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-09-20 21:25:13 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-11-10 12:50:56 +09:00
|
|
|
|
|
|
|
|
|
2025-06-15 13:53:09 +05:30
|
|
|
|
|
|
|
|
|
2010-11-10 12:50:56 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-06-15 13:53:09 +05:30
|
|
|
|
2010-11-10 12:50:56 +09:00
|
|
|
|
|
|
|
|
|
2011-07-05 16:35:41 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-11-04 11:18:16 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-11-24 14:25:49 +01:00
|
|
|
|
2011-11-04 11:18:16 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-07-26 17:24:39 +02:00
|
|
|
|
2026-02-13 15:31:26 +05:30
|
|
|
|
2016-04-12 15:56:15 +02:00
|
|
|
|
2026-02-13 15:31:26 +05:30
|
|
|
|
2015-06-01 23:14:59 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-08-28 14:00:05 +02:00
|
|
|
|
2011-11-04 11:18:16 +01:00
|
|
|
|
|
|
|
|
|
2023-08-15 18:41:32 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-02-13 15:31:25 +05:30
|
|
|
|
2026-02-13 15:31:26 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-02-13 15:31:25 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-02-13 15:31:26 +05:30
|
|
|
|
2012-07-26 17:24:39 +02:00
|
|
|
|
2011-11-04 11:18:16 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-07-26 17:24:39 +02:00
|
|
|
|
2015-06-01 23:14:59 +02:00
|
|
|
|
|
|
|
|
|
2012-07-26 17:24:39 +02:00
|
|
|
|
2011-11-04 11:18:16 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
networking: make skb_put & friends return void pointers
It seems like a historic accident that these return unsigned char *,
and in many places that means casts are required, more often than not.
Make these functions (skb_put, __skb_put and pskb_put) return void *
and remove all the casts across the tree, adding a (u8 *) cast only
where the unsigned char pointer was used directly, all done with the
following spatch:
@@
expression SKB, LEN;
typedef u8;
identifier fn = { skb_put, __skb_put };
@@
- *(fn(SKB, LEN))
+ *(u8 *)fn(SKB, LEN)
@@
expression E, SKB, LEN;
identifier fn = { skb_put, __skb_put };
type T;
@@
- E = ((T *)(fn(SKB, LEN)))
+ E = fn(SKB, LEN)
which actually doesn't cover pskb_put since there are only three
users overall.
A handful of stragglers were converted manually, notably a macro in
drivers/isdn/i4l/isdn_bsdcomp.c and, oddly enough, one of the many
instances in net/bluetooth/hci_sock.c. In the former file, I also
had to fix one whitespace problem spatch introduced.
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2017-06-16 14:29:21 +02:00
|
|
|
|
2011-11-04 11:18:16 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-02-13 15:31:26 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-11-04 11:18:16 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-11-09 18:50:09 +02:00
|
|
|
|
2011-11-04 11:18:16 +01:00
|
|
|
|
2026-02-13 15:31:26 +05:30
|
|
|
|
|
|
|
|
|
2011-11-04 11:18:16 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-11-24 14:25:49 +01:00
|
|
|
|
|
|
|
|
|
2015-06-01 23:14:59 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-11-04 11:18:16 +01:00
|
|
|
|
2020-07-23 14:01:52 +04:00
|
|
|
|
2011-11-04 11:18:16 +01:00
|
|
|
|
|
|
|
|
|
2015-06-01 23:14:59 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-11-04 11:18:16 +01:00
|
|
|
|
|
|
|
|
|
2012-11-08 21:25:48 +01:00
|
|
|
|
|
|
|
|
|
2022-04-14 16:50:57 +02:00
|
|
|
|
2012-11-08 21:25:48 +01:00
|
|
|
|
2012-07-12 19:45:08 +02:00
|
|
|
|
2012-07-26 17:24:39 +02:00
|
|
|
|
2013-02-23 19:02:14 +01:00
|
|
|
|
2012-07-26 17:24:39 +02:00
|
|
|
|
2022-06-17 22:36:37 +02:00
|
|
|
|
2012-11-08 21:25:48 +01:00
|
|
|
|
2012-07-12 19:45:08 +02:00
|
|
|
|
2012-07-26 17:24:39 +02:00
|
|
|
|
2022-06-17 22:36:37 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-02-28 09:59:22 +01:00
|
|
|
|
wifi: mac80211: introduce 'channel request'
For channel contexts, mac80211 currently uses the cfg80211
chandef struct (control channel, center freq(s), width) to
define towards drivers and internally how these behave. In
fact, there are _two_ such structs used, where the min_def
can reduce bandwidth according to the stations connected.
Unfortunately, with EHT this is longer be sufficient, at
least not for all hardware. EHT requires that non-AP STAs
that are connected to an AP with a lower bandwidth than it
(the AP) advertises (e.g. 160 MHz STA connected to 320 MHz
AP) still be able to receive downlink OFDMA and respond to
trigger frames for uplink OFDMA that specify the position
and bandwidth for the non-AP STA relative to the channel
the AP is using. Therefore, they need to be aware of this,
and at least for some hardware (e.g. Intel) this awareness
is in the hardware. As a result, use of the "same" channel
may need to be split over two channel contexts where they
differ by the AP being used.
As a first step, introduce a concept of a channel request
('chanreq') for each interface, to control the context it
requests. This step does nothing but reorganise the code,
so that later the AP's chandef can be added to the request
in order to handle the EHT case described above.
Link: https://msgid.link/20240129194108.2e88e48bd2e9.I4256183debe975c5ed71621611206fdbb69ba330@changeid
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2024-01-29 19:34:40 +01:00
|
|
|
|
2013-02-28 09:59:22 +01:00
|
|
|
|
2025-02-20 10:41:39 +01:00
|
|
|
|
|
|
|
|
|
2013-02-28 09:59:22 +01:00
|
|
|
|
wifi: mac80211: introduce 'channel request'
For channel contexts, mac80211 currently uses the cfg80211
chandef struct (control channel, center freq(s), width) to
define towards drivers and internally how these behave. In
fact, there are _two_ such structs used, where the min_def
can reduce bandwidth according to the stations connected.
Unfortunately, with EHT this is longer be sufficient, at
least not for all hardware. EHT requires that non-AP STAs
that are connected to an AP with a lower bandwidth than it
(the AP) advertises (e.g. 160 MHz STA connected to 320 MHz
AP) still be able to receive downlink OFDMA and respond to
trigger frames for uplink OFDMA that specify the position
and bandwidth for the non-AP STA relative to the channel
the AP is using. Therefore, they need to be aware of this,
and at least for some hardware (e.g. Intel) this awareness
is in the hardware. As a result, use of the "same" channel
may need to be split over two channel contexts where they
differ by the AP being used.
As a first step, introduce a concept of a channel request
('chanreq') for each interface, to control the context it
requests. This step does nothing but reorganise the code,
so that later the AP's chandef can be added to the request
in order to handle the EHT case described above.
Link: https://msgid.link/20240129194108.2e88e48bd2e9.I4256183debe975c5ed71621611206fdbb69ba330@changeid
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2024-01-29 19:34:40 +01:00
|
|
|
|
2012-11-08 21:25:48 +01:00
|
|
|
|
2012-07-26 17:24:39 +02:00
|
|
|
|
2022-06-17 22:36:37 +02:00
|
|
|
|
2012-07-26 17:24:39 +02:00
|
|
|
|
|
|
|
|
|
2012-11-08 21:25:48 +01:00
|
|
|
|
2012-07-12 19:45:08 +02:00
|
|
|
|
|
|
|
|
|
2012-04-04 15:05:25 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-12-16 23:04:43 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-02-21 16:37:42 -08:00
|
|
|
|
2013-12-16 23:04:43 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-12-30 23:12:37 +01:00
|
|
|
|
2013-12-16 23:04:43 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-04-28 11:22:25 +03:00
|
|
|
|
|
|
|
|
|
2022-04-14 16:50:57 +02:00
|
|
|
|
2014-04-28 11:22:25 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-06-17 22:36:37 +02:00
|
|
|
|
2026-04-28 11:25:37 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-04-28 11:22:25 +03:00
|
|
|
|
2023-01-27 12:39:31 +01:00
|
|
|
|
2014-04-28 11:22:25 +03:00
|
|
|
|
2022-06-17 22:36:37 +02:00
|
|
|
|
|
|
|
|
|
wifi: mac80211: introduce 'channel request'
For channel contexts, mac80211 currently uses the cfg80211
chandef struct (control channel, center freq(s), width) to
define towards drivers and internally how these behave. In
fact, there are _two_ such structs used, where the min_def
can reduce bandwidth according to the stations connected.
Unfortunately, with EHT this is longer be sufficient, at
least not for all hardware. EHT requires that non-AP STAs
that are connected to an AP with a lower bandwidth than it
(the AP) advertises (e.g. 160 MHz STA connected to 320 MHz
AP) still be able to receive downlink OFDMA and respond to
trigger frames for uplink OFDMA that specify the position
and bandwidth for the non-AP STA relative to the channel
the AP is using. Therefore, they need to be aware of this,
and at least for some hardware (e.g. Intel) this awareness
is in the hardware. As a result, use of the "same" channel
may need to be split over two channel contexts where they
differ by the AP being used.
As a first step, introduce a concept of a channel request
('chanreq') for each interface, to control the context it
requests. This step does nothing but reorganise the code,
so that later the AP's chandef can be added to the request
in order to handle the EHT case described above.
Link: https://msgid.link/20240129194108.2e88e48bd2e9.I4256183debe975c5ed71621611206fdbb69ba330@changeid
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2024-01-29 19:34:40 +01:00
|
|
|
|
2014-04-28 11:22:25 +03:00
|
|
|
|
2022-06-17 22:36:37 +02:00
|
|
|
|
2014-04-28 11:22:25 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-10-07 10:38:50 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-01-07 15:42:39 +02:00
|
|
|
|
2014-10-07 10:38:50 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-09-20 17:31:20 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-03-26 12:14:34 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-09-20 17:31:20 +03:00
|
|
|
|
2026-03-26 12:14:34 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-09-20 17:31:20 +03:00
|
|
|
|
2026-03-26 12:14:34 +02:00
|
|
|
|
2016-09-20 17:31:20 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-03-26 12:14:34 +02:00
|
|
|
|
2016-09-20 17:31:20 +03:00
|
|
|
|
2026-03-26 12:14:34 +02:00
|
|
|
|
2016-09-20 17:31:20 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-09-20 17:31:21 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-03-26 12:14:34 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-09-20 17:31:21 +03:00
|
|
|
|
2026-03-26 12:14:34 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-09-20 17:31:21 +03:00
|
|
|
|
2026-03-26 12:14:34 +02:00
|
|
|
|
2016-09-20 17:31:21 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-03-26 12:14:34 +02:00
|
|
|
|
2016-09-20 17:31:21 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-05-04 10:20:41 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-11-22 11:52:18 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-05-08 13:03:50 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-10-03 20:19:20 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-10-16 11:24:47 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-01-20 13:21:27 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-08-28 14:00:01 +02:00
|
|
|
|
|
|
|
|
|
2020-01-20 13:21:27 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-08-28 14:00:01 +02:00
|
|
|
|
2020-01-20 13:21:27 +05:30
|
|
|
|
|
|
|
|
|
2023-08-28 14:00:01 +02:00
|
|
|
|
2020-01-20 13:21:27 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-04-24 14:29:02 +03:00
|
|
|
|
2020-01-20 13:21:27 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-08-28 14:00:01 +02:00
|
|
|
|
|
|
|
|
|
2020-01-20 13:21:27 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-04-24 14:29:02 +03:00
|
|
|
|
2020-01-20 13:21:27 +05:30
|
|
|
|
|
|
|
|
|
2023-08-28 14:00:01 +02:00
|
|
|
|
2020-01-20 13:21:27 +05:30
|
|
|
|
|
|
|
|
|
2023-08-28 14:00:01 +02:00
|
|
|
|
2020-01-20 13:21:27 +05:30
|
|
|
|
|
|
|
|
|
2020-12-03 05:37:27 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-07-02 19:44:08 +02:00
|
|
|
|
2024-04-22 11:04:08 +05:30
|
|
|
|
2023-06-04 12:11:26 +03:00
|
|
|
|
2021-07-02 19:44:08 +02:00
|
|
|
|
2024-04-22 11:04:08 +05:30
|
|
|
|
|
|
|
|
|
2021-07-02 19:44:08 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-04-22 11:04:08 +05:30
|
|
|
|
2022-04-07 12:36:58 +02:00
|
|
|
|
|
|
|
|
|
2024-04-22 11:04:08 +05:30
|
|
|
|
|
|
|
|
|
2023-06-04 12:11:26 +03:00
|
|
|
|
2024-04-22 11:04:08 +05:30
|
|
|
|
2021-07-02 19:44:08 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-04-22 11:04:08 +05:30
|
|
|
|
2021-07-02 19:44:08 +02:00
|
|
|
|
2023-06-04 12:11:26 +03:00
|
|
|
|
2021-07-02 19:44:08 +02:00
|
|
|
|
2024-04-22 11:04:08 +05:30
|
|
|
|
2021-07-02 19:44:08 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-04-22 11:04:08 +05:30
|
|
|
|
2021-07-02 19:44:08 +02:00
|
|
|
|
2024-04-22 11:04:08 +05:30
|
|
|
|
2021-07-02 19:44:08 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-04-22 11:04:08 +05:30
|
|
|
|
2022-06-17 22:36:37 +02:00
|
|
|
|
2023-06-04 12:11:26 +03:00
|
|
|
|
2021-07-02 19:44:08 +02:00
|
|
|
|
2024-04-22 11:04:08 +05:30
|
|
|
|
2021-07-02 19:44:08 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-04-22 11:04:08 +05:30
|
|
|
|
2023-06-04 12:11:26 +03:00
|
|
|
|
2021-07-02 19:44:08 +02:00
|
|
|
|
2024-04-22 11:04:08 +05:30
|
|
|
|
|
|
|
|
|
2023-08-28 14:00:06 +02:00
|
|
|
|
|
|
|
|
|
2024-04-22 11:04:08 +05:30
|
|
|
|
|
|
|
|
|
2021-07-02 19:44:08 +02:00
|
|
|
|
|
|
|
|
|
2024-04-22 11:04:08 +05:30
|
|
|
|
2021-11-17 16:27:27 +05:30
|
|
|
|
2025-04-08 11:45:00 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-11-17 16:27:27 +05:30
|
|
|
|
2025-04-08 11:45:00 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-11-17 16:27:27 +05:30
|
|
|
|
|
|
|
|
|
2021-07-02 19:44:08 +02:00
|
|
|
|
|
|
|
|
|
2024-04-22 11:04:08 +05:30
|
|
|
|
2021-07-02 19:44:08 +02:00
|
|
|
|
2024-04-22 11:04:08 +05:30
|
|
|
|
2021-07-02 19:44:08 +02:00
|
|
|
|
2023-06-04 12:11:26 +03:00
|
|
|
|
2021-07-02 19:44:08 +02:00
|
|
|
|
|
|
|
|
|
2023-08-28 14:00:05 +02:00
|
|
|
|
2021-07-02 19:44:08 +02:00
|
|
|
|
2024-04-22 11:04:08 +05:30
|
|
|
|
2021-07-02 19:44:08 +02:00
|
|
|
|
2024-04-22 11:04:08 +05:30
|
|
|
|
2021-07-02 19:44:08 +02:00
|
|
|
|
2024-04-22 11:04:08 +05:30
|
|
|
|
2021-07-02 19:44:08 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-04-22 11:04:08 +05:30
|
|
|
|
|
|
|
|
|
2021-07-02 19:44:08 +02:00
|
|
|
|
2024-04-22 11:04:08 +05:30
|
|
|
|
2021-07-02 19:44:08 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-08-28 13:59:51 +02:00
|
|
|
|
|
|
|
|
|
2021-07-02 19:44:08 +02:00
|
|
|
|
2024-04-22 11:04:08 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-07-02 19:44:08 +02:00
|
|
|
|
|
|
|
|
|
2023-08-28 14:00:05 +02:00
|
|
|
|
2021-07-02 19:44:08 +02:00
|
|
|
|
|
|
|
|
|
2024-04-22 11:04:08 +05:30
|
|
|
|
2023-08-29 12:18:56 +02:00
|
|
|
|
2021-07-02 19:44:08 +02:00
|
|
|
|
|
|
|
|
|
2023-08-29 12:18:56 +02:00
|
|
|
|
2021-07-02 19:44:08 +02:00
|
|
|
|
2024-04-22 11:04:08 +05:30
|
|
|
|
2021-07-02 19:44:08 +02:00
|
|
|
|
|
|
|
|
|
2024-09-24 21:28:05 +02:00
|
|
|
|
|
|
|
|
|
2023-01-25 12:01:02 +01:00
|
|
|
|
|
|
|
|
|
2024-09-24 21:28:05 +02:00
|
|
|
|
|
|
|
|
|
2023-01-25 12:01:02 +01:00
|
|
|
|
|
|
|
|
|
2024-04-22 11:04:08 +05:30
|
|
|
|
|
|
|
|
|
2023-01-25 12:01:02 +01:00
|
|
|
|
|
|
|
|
|
2024-04-22 11:04:08 +05:30
|
|
|
|
2021-07-02 19:44:08 +02:00
|
|
|
|
|
|
|
|
|
2024-04-22 11:04:08 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-07-02 19:44:08 +02:00
|
|
|
|
2023-08-28 13:59:51 +02:00
|
|
|
|
2024-04-22 11:04:08 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-07-02 19:44:08 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-01-19 14:57:11 +01:00
|
|
|
|
2024-04-22 11:04:08 +05:30
|
|
|
|
2021-07-02 19:44:08 +02:00
|
|
|
|
|
|
|
|
|
2024-04-22 11:04:08 +05:30
|
|
|
|
2021-07-02 19:44:08 +02:00
|
|
|
|
2024-04-22 11:04:08 +05:30
|
|
|
|
2021-07-02 19:44:08 +02:00
|
|
|
|
|
|
|
|
|
2024-04-22 11:04:08 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-01-25 12:01:02 +01:00
|
|
|
|
2024-04-22 11:04:08 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-09-24 21:28:05 +02:00
|
|
|
|
|
|
|
|
|
2024-04-22 11:04:08 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-01-25 12:01:02 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-09-24 21:28:05 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-04-22 11:04:08 +05:30
|
|
|
|
|
|
|
|
|
2021-07-02 19:44:08 +02:00
|
|
|
|
2023-01-19 14:57:11 +01:00
|
|
|
|
2021-07-02 19:44:08 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-04-22 11:04:08 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-04 12:11:26 +03:00
|
|
|
|
2021-07-02 19:44:08 +02:00
|
|
|
|
|
|
|
|
|
2023-08-28 14:00:05 +02:00
|
|
|
|
2021-07-02 19:44:08 +02:00
|
|
|
|
2024-04-22 11:04:08 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-11-17 16:27:27 +05:30
|
|
|
|
|
|
|
|
|
2021-07-02 19:44:08 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-04-22 11:04:08 +05:30
|
|
|
|
2021-07-02 19:44:08 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-07-10 11:04:28 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-04-22 11:04:08 +05:30
|
|
|
|
2021-07-02 19:44:08 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-04-22 11:04:08 +05:30
|
|
|
|
|
|
|
|
|
2021-07-02 19:44:08 +02:00
|
|
|
|
2024-04-22 11:04:08 +05:30
|
|
|
|
2021-07-02 19:44:08 +02:00
|
|
|
|
|
|
|
|
|
2024-04-22 11:04:08 +05:30
|
|
|
|
2021-07-02 19:44:08 +02:00
|
|
|
|
|
|
|
|
|
2024-04-22 11:04:08 +05:30
|
|
|
|
2021-07-02 19:44:08 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-10-23 11:10:51 +02:00
|
|
|
|
2021-11-29 14:11:24 +01:00
|
|
|
|
|
|
|
|
|
2021-10-23 11:10:51 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-11-29 14:11:24 +01:00
|
|
|
|
2021-10-23 11:10:51 +02:00
|
|
|
|
|
|
|
|
|
2021-11-29 14:11:24 +01:00
|
|
|
|
2021-10-23 11:10:51 +02:00
|
|
|
|
|
|
|
|
|
2022-06-10 11:21:21 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-08-28 14:00:05 +02:00
|
|
|
|
|
|
|
|
|
2022-06-10 11:21:21 +02:00
|
|
|
|
2023-08-28 14:00:05 +02:00
|
|
|
|
2022-06-10 11:21:21 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-11-21 09:45:30 +05:30
|
|
|
|
2022-06-10 11:21:21 +02:00
|
|
|
|
2023-08-28 14:00:05 +02:00
|
|
|
|
|
|
|
|
|
2024-11-21 09:45:30 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-06-10 11:21:21 +02:00
|
|
|
|
|
|
|
|
|
2024-05-06 21:19:34 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-06-14 17:27:03 +03:00
|
|
|
|
2024-05-06 21:19:34 +02:00
|
|
|
|
|
|
|
|
|
2022-06-14 17:27:03 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-05-06 21:19:34 +02:00
|
|
|
|
|
|
|
|
|
2022-06-14 17:27:03 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-07-18 23:01:19 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-06-14 17:27:03 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
wifi: mac80211: fix erroneous errors for STA changes
When e.g. wpa_supplicant sets only the MLD "sta" authorized
state, the code actually applies that change, but then returns
an error to userspace anyway because there were no changes to
the link station, and no link ID was given. However, it's not
incorrect to not have a link ID when wanting to change only
the MLD peer ("sta") state, so the code shouldn't require it.
To fix this, separate the "new_link" argument out into a new
three-state enum, because if modify is called on a link STA
only, it should return an error if no link is given or if it
doesn't exist. For modify on the MLD "sta", not having a link
ID is OK, but if there is one it should be validated.
This seems to not have mattered much as wpa_supplicant just
prints a message and continues, and the authorized state was
already set before this error return. However, in the later
code powersave recalculation etc. will be skipped, so that it
may result in never allowing powersave on MLO connections.
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: Miri Korenblit <miriam.rachel.korenblit@intel.com>
Link: https://msgid.link/20240605135233.48e2b8af07e3.Ib9793c383fcba118c05100e024f4a11a1c3d0e85@changeid
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2024-06-05 13:57:18 +03:00
|
|
|
|
2022-06-14 17:27:03 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
wifi: mac80211: allow rate_control_rate_init() for links
Andrei previously fixed an issue in the client where the NSS
for links other than the primary/assoc/deflink isn't set. The
same issue appears to exist on the AP side, because there's
only a call to rate_control_rate_init() for the deflink, and
not any other links.
Rework the code a bit to do rate_control_rate_init() for links,
even if it really doesn't work with software rate control yet,
it does other things as well.
Also add rate_control_rate_init_all_links() to actually do it
properly when moving to ASSOC state in cfg80211.
Change the explicit call to ieee80211_sta_init_nss() to instead
be rate_control_rate_init() now in the client code, but also
add a call to rate_control_rate_init() when a link is added in
AP mode and the STA is already associated.
This should fix the NSS initialization issue, and perhaps pave
the way for actual software rate scaling a bit, in case anyone
cares in the future, but that of course needs a lot more than
just the init call.
We still need to fix the rate control _update_ as well, and the
sta_rc_update() driver method especially, but that will be in a
different patch.
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: Miri Korenblit <miriam.rachel.korenblit@intel.com>
Link: https://patch.msgid.link/20241007144851.c693274a908f.I0376da02e9f5a30eaa1b5d0d01371ff09506d453@changeid
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2024-10-07 15:00:53 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-06-14 17:27:03 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-05-06 21:19:34 +02:00
|
|
|
|
2022-06-14 17:27:03 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-05-06 21:19:34 +02:00
|
|
|
|
|
|
|
|
|
2022-06-14 17:27:03 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
wifi: mac80211: fix erroneous errors for STA changes
When e.g. wpa_supplicant sets only the MLD "sta" authorized
state, the code actually applies that change, but then returns
an error to userspace anyway because there were no changes to
the link station, and no link ID was given. However, it's not
incorrect to not have a link ID when wanting to change only
the MLD peer ("sta") state, so the code shouldn't require it.
To fix this, separate the "new_link" argument out into a new
three-state enum, because if modify is called on a link STA
only, it should return an error if no link is given or if it
doesn't exist. For modify on the MLD "sta", not having a link
ID is OK, but if there is one it should be validated.
This seems to not have mattered much as wpa_supplicant just
prints a message and continues, and the authorized state was
already set before this error return. However, in the later
code powersave recalculation etc. will be skipped, so that it
may result in never allowing powersave on MLO connections.
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: Miri Korenblit <miriam.rachel.korenblit@intel.com>
Link: https://msgid.link/20240605135233.48e2b8af07e3.Ib9793c383fcba118c05100e024f4a11a1c3d0e85@changeid
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2024-06-05 13:57:18 +03:00
|
|
|
|
|
|
|
|
|
2022-06-14 17:27:03 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-05-06 21:19:34 +02:00
|
|
|
|
|
|
|
|
|
2022-06-14 17:27:03 +03:00
|
|
|
|
|
|
|
|
|
2024-05-06 21:19:34 +02:00
|
|
|
|
2022-06-14 17:27:03 +03:00
|
|
|
|
2023-08-28 14:00:01 +02:00
|
|
|
|
2022-06-14 17:27:03 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-07-18 23:01:19 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-06-14 17:27:03 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-03-01 12:09:22 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-01-02 21:35:37 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-01-02 16:19:58 +02:00
|
|
|
|
|
|
|
|
|
2025-03-08 23:03:27 +02:00
|
|
|
|
2025-01-02 16:19:58 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-03-08 23:03:27 +02:00
|
|
|
|
2025-01-02 16:19:58 +02:00
|
|
|
|
|
|
|
|
|
2025-02-05 11:39:13 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-03-26 12:14:35 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-03-26 12:14:39 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-01-20 23:55:44 +01:00
|
|
|
|
2007-05-05 11:45:53 -07:00
|
|
|
|
|
|
|
|
|
2007-09-28 21:52:27 +02:00
|
|
|
|
2012-06-18 20:07:15 +02:00
|
|
|
|
|
|
|
|
|
2007-12-19 02:03:30 +01:00
|
|
|
|
|
|
|
|
|
2007-12-19 02:03:31 +01:00
|
|
|
|
2007-12-19 02:03:30 +01:00
|
|
|
|
2009-01-08 13:32:02 +02:00
|
|
|
|
2020-02-22 15:25:44 +02:00
|
|
|
|
2012-02-13 15:17:18 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-12-19 02:03:35 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-12-19 02:03:37 +01:00
|
|
|
|
2008-02-23 15:17:17 +01:00
|
|
|
|
2010-04-19 10:23:57 +02:00
|
|
|
|
2008-02-23 15:17:17 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-09-12 08:58:50 +02:00
|
|
|
|
|
|
|
|
|
2010-12-16 17:37:48 -08:00
|
|
|
|
|
|
|
|
|
2010-12-03 09:20:44 +01:00
|
|
|
|
|
|
|
|
|
2008-02-23 15:17:17 +01:00
|
|
|
|
2014-11-03 10:33:19 +01:00
|
|
|
|
|
|
|
|
|
2008-08-07 20:07:01 +03:00
|
|
|
|
2023-06-16 09:54:01 +03:00
|
|
|
|
2008-10-30 16:59:24 +02:00
|
|
|
|
2012-06-06 08:18:22 +02:00
|
|
|
|
2009-01-19 11:20:53 -05:00
|
|
|
|
|
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
2015-10-30 19:14:50 +05:30
|
|
|
|
2011-05-11 17:09:36 +03:00
|
|
|
|
|
|
|
|
|
2009-03-19 13:39:22 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-04-19 21:25:43 +02:00
|
|
|
|
|
|
|
|
|
2012-11-02 13:27:49 +01:00
|
|
|
|
2009-04-20 18:39:05 +02:00
|
|
|
|
2009-06-02 13:01:39 +02:00
|
|
|
|
|
|
|
|
|
2009-06-02 13:01:41 +02:00
|
|
|
|
2009-07-01 21:26:51 +02:00
|
|
|
|
2011-05-20 09:05:54 -07:00
|
|
|
|
2009-07-01 21:26:57 +02:00
|
|
|
|
2009-07-01 21:26:59 +02:00
|
|
|
|
2009-12-23 13:15:42 +01:00
|
|
|
|
|
|
|
|
|
2010-08-12 15:38:38 +02:00
|
|
|
|
2010-11-25 10:02:30 +01:00
|
|
|
|
2010-03-23 09:02:34 +02:00
|
|
|
|
2017-02-10 04:50:22 +01:00
|
|
|
|
2020-04-17 12:43:01 +02:00
|
|
|
|
|
|
|
|
|
2010-11-10 12:50:56 +09:00
|
|
|
|
|
|
|
|
|
2011-07-05 16:35:41 +02:00
|
|
|
|
2011-09-28 14:12:52 +03:00
|
|
|
|
|
|
|
|
|
2014-11-09 18:50:19 +02:00
|
|
|
|
|
|
|
|
|
2011-11-04 11:18:16 +01:00
|
|
|
|
2011-11-18 14:20:44 +01:00
|
|
|
|
2012-04-04 15:05:25 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-07-12 19:45:08 +02:00
|
|
|
|
2013-02-08 18:16:20 +01:00
|
|
|
|
2019-12-22 14:55:31 +00:00
|
|
|
|
2013-07-11 16:09:06 +02:00
|
|
|
|
2013-12-16 23:04:43 -08:00
|
|
|
|
2014-04-28 11:22:25 +03:00
|
|
|
|
2014-10-07 10:38:50 +03:00
|
|
|
|
|
|
|
|
|
2016-09-20 17:31:14 +03:00
|
|
|
|
|
|
|
|
|
2016-09-20 17:31:19 +03:00
|
|
|
|
2016-09-20 17:31:20 +03:00
|
|
|
|
|
|
|
|
|
2016-11-22 11:52:18 +01:00
|
|
|
|
2018-03-26 12:52:50 -05:00
|
|
|
|
2018-05-08 13:03:50 +02:00
|
|
|
|
2018-10-03 20:19:20 -07:00
|
|
|
|
2018-10-16 11:24:47 +02:00
|
|
|
|
|
|
|
|
|
2019-04-11 13:47:26 -07:00
|
|
|
|
2020-01-20 13:21:27 +05:30
|
|
|
|
|
|
|
|
|
2020-12-03 05:37:27 -05:00
|
|
|
|
2021-07-02 19:44:08 +02:00
|
|
|
|
2021-11-29 14:11:24 +01:00
|
|
|
|
2022-06-10 11:21:21 +02:00
|
|
|
|
|
|
|
|
|
2022-06-14 17:27:03 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-03-01 12:09:22 +02:00
|
|
|
|
2024-01-02 21:35:37 +02:00
|
|
|
|
2024-07-09 10:38:35 +02:00
|
|
|
|
2025-01-02 16:19:58 +02:00
|
|
|
|
2025-02-05 11:39:13 +02:00
|
|
|
|
2026-03-26 12:14:35 +02:00
|
|
|
|
2026-03-26 12:14:39 +02:00
|
|
|
|
2007-05-05 11:45:53 -07:00
|
|
|
|