License cleanup: add SPDX GPL-2.0 license identifier to files with no license
Many source files in the tree are missing licensing information, which
makes it harder for compliance tools to determine the correct license.
By default all files without license information are under the default
license of the kernel, which is GPL version 2.
Update the files which contain no license information with the 'GPL-2.0'
SPDX license identifier. The SPDX identifier is a legally binding
shorthand, which can be used instead of the full boiler plate text.
This patch is based on work done by Thomas Gleixner and Kate Stewart and
Philippe Ombredanne.
How this work was done:
Patches were generated and checked against linux-4.14-rc6 for a subset of
the use cases:
- file had no licensing information it it.
- file was a */uapi/* one with no licensing information in it,
- file was a */uapi/* one with existing licensing information,
Further patches will be generated in subsequent months to fix up cases
where non-standard license headers were used, and references to license
had to be inferred by heuristics based on keywords.
The analysis to determine which SPDX License Identifier to be applied to
a file was done in a spreadsheet of side by side results from of the
output of two independent scanners (ScanCode & Windriver) producing SPDX
tag:value files created by Philippe Ombredanne. Philippe prepared the
base worksheet, and did an initial spot review of a few 1000 files.
The 4.13 kernel was the starting point of the analysis with 60,537 files
assessed. Kate Stewart did a file by file comparison of the scanner
results in the spreadsheet to determine which SPDX license identifier(s)
to be applied to the file. She confirmed any determination that was not
immediately clear with lawyers working with the Linux Foundation.
Criteria used to select files for SPDX license identifier tagging was:
- Files considered eligible had to be source code files.
- Make and config files were included as candidates if they contained >5
lines of source
- File already had some variant of a license header in it (even if <5
lines).
All documentation files were explicitly excluded.
The following heuristics were used to determine which SPDX license
identifiers to apply.
- when both scanners couldn't find any license traces, file was
considered to have no license information in it, and the top level
COPYING file license applied.
For non */uapi/* files that summary was:
SPDX license identifier # files
---------------------------------------------------|-------
GPL-2.0 11139
and resulted in the first patch in this series.
If that file was a */uapi/* path one, it was "GPL-2.0 WITH
Linux-syscall-note" otherwise it was "GPL-2.0". Results of that was:
SPDX license identifier # files
---------------------------------------------------|-------
GPL-2.0 WITH Linux-syscall-note 930
and resulted in the second patch in this series.
- if a file had some form of licensing information in it, and was one
of the */uapi/* ones, it was denoted with the Linux-syscall-note if
any GPL family license was found in the file or had no licensing in
it (per prior point). Results summary:
SPDX license identifier # files
---------------------------------------------------|------
GPL-2.0 WITH Linux-syscall-note 270
GPL-2.0+ WITH Linux-syscall-note 169
((GPL-2.0 WITH Linux-syscall-note) OR BSD-2-Clause) 21
((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause) 17
LGPL-2.1+ WITH Linux-syscall-note 15
GPL-1.0+ WITH Linux-syscall-note 14
((GPL-2.0+ WITH Linux-syscall-note) OR BSD-3-Clause) 5
LGPL-2.0+ WITH Linux-syscall-note 4
LGPL-2.1 WITH Linux-syscall-note 3
((GPL-2.0 WITH Linux-syscall-note) OR MIT) 3
((GPL-2.0 WITH Linux-syscall-note) AND MIT) 1
and that resulted in the third patch in this series.
- when the two scanners agreed on the detected license(s), that became
the concluded license(s).
- when there was disagreement between the two scanners (one detected a
license but the other didn't, or they both detected different
licenses) a manual inspection of the file occurred.
- In most cases a manual inspection of the information in the file
resulted in a clear resolution of the license that should apply (and
which scanner probably needed to revisit its heuristics).
- When it was not immediately clear, the license identifier was
confirmed with lawyers working with the Linux Foundation.
- If there was any question as to the appropriate license identifier,
the file was flagged for further research and to be revisited later
in time.
In total, over 70 hours of logged manual review was done on the
spreadsheet to determine the SPDX license identifiers to apply to the
source files by Kate, Philippe, Thomas and, in some cases, confirmation
by lawyers working with the Linux Foundation.
Kate also obtained a third independent scan of the 4.13 code base from
FOSSology, and compared selected files where the other two scanners
disagreed against that SPDX file, to see if there was new insights. The
Windriver scanner is based on an older version of FOSSology in part, so
they are related.
Thomas did random spot checks in about 500 files from the spreadsheets
for the uapi headers and agreed with SPDX license identifier in the
files he inspected. For the non-uapi files Thomas did random spot checks
in about 15000 files.
In initial set of patches against 4.14-rc6, 3 files were found to have
copy/paste license identifier errors, and have been fixed to reflect the
correct identifier.
Additionally Philippe spent 10 hours this week doing a detailed manual
inspection and review of the 12,461 patched files from the initial patch
version early this week with:
- a full scancode scan run, collecting the matched texts, detected
license ids and scores
- reviewing anything where there was a license detected (about 500+
files) to ensure that the applied SPDX license was correct
- reviewing anything where there was no detection but the patch license
was not GPL-2.0 WITH Linux-syscall-note to ensure that the applied
SPDX license was correct
This produced a worksheet with 20 files needing minor correction. This
worksheet was then exported into 3 different .csv files for the
different types of files to be modified.
These .csv files were then reviewed by Greg. Thomas wrote a script to
parse the csv files and add the proper SPDX tag to the file, in the
format that the file expected. This script was further refined by Greg
based on the output to detect more types of files automatically and to
distinguish between header and source .c files (which need different
comment types.) Finally Greg ran the script using the .csv files to
generate the patches.
Reviewed-by: Kate Stewart <kstewart@linuxfoundation.org>
Reviewed-by: Philippe Ombredanne <pombredanne@nexb.com>
Reviewed-by: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2017-11-01 15:07:57 +01:00
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-09-03 15:24:58 +03:00
|
|
|
|
2016-07-05 17:10:13 +03:00
|
|
|
|
2026-05-29 10:25:00 +02:00
|
|
|
|
2009-02-10 21:25:55 +01: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
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-09-18 11:33:13 +02:00
|
|
|
|
|
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
|
|
|
|
|
2011-07-13 10:39:09 +02:00
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
2023-12-20 16:19:52 +01:00
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
|
|
|
|
|
2009-07-27 12:01:53 +02:00
|
|
|
|
2012-06-27 17:19:42 +03:00
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
2013-02-01 02:06:18 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-08-22 16:19:51 -07:00
|
|
|
|
2013-02-01 02:06:18 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-11-15 12:05:11 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-04-13 16:38:40 +05:30
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
2013-02-01 02:06:18 +01:00
|
|
|
|
2012-10-11 21:03:33 -07:00
|
|
|
|
2012-11-29 01:25:20 +01:00
|
|
|
|
2012-11-28 22:14:56 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-11-29 01:25:20 +01:00
|
|
|
|
2013-02-01 02:06:18 +01:00
|
|
|
|
2012-11-29 01:25:20 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-10-11 21:03:33 -07:00
|
|
|
|
2013-02-01 02:06:18 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-10-11 21:03:33 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-04-21 12:53:02 +08:00
|
|
|
|
2013-02-01 02:06:18 +01:00
|
|
|
|
2013-02-01 01:34:36 +01:00
|
|
|
|
2014-04-21 12:53:02 +08:00
|
|
|
|
2013-02-01 02:06:18 +01:00
|
|
|
|
|
|
|
|
|
2022-09-30 23:44:23 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-02-01 01:34:36 +01:00
|
|
|
|
|
|
|
|
|
2014-04-21 12:53:02 +08:00
|
|
|
|
2013-02-01 02:06:18 +01:00
|
|
|
|
2013-02-01 01:34:36 +01:00
|
|
|
|
2014-04-21 12:53:02 +08:00
|
|
|
|
2013-02-01 02:06:18 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-10-17 09:03:48 +02:00
|
|
|
|
|
|
|
|
|
2013-02-01 02:06:18 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-01-21 12:22:21 +02:00
|
|
|
|
2019-01-21 12:25:59 +02:00
|
|
|
|
2019-01-21 12:22:21 +02:00
|
|
|
|
|
|
|
|
|
2022-10-17 09:03:48 +02:00
|
|
|
|
2019-01-21 12:22:21 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-02-01 02:06:18 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-02-01 01:34:36 +01:00
|
|
|
|
|
|
|
|
|
2014-04-21 12:53:02 +08:00
|
|
|
|
2012-10-11 21:03:33 -07:00
|
|
|
|
|
|
|
|
|
2014-04-21 12:53:02 +08:00
|
|
|
|
2013-02-01 01:05:43 +01:00
|
|
|
|
2013-02-01 02:06:18 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-10-11 21:03:33 -07:00
|
|
|
|
2019-01-21 12:25:59 +02:00
|
|
|
|
2014-04-21 12:53:02 +08:00
|
|
|
|
2016-11-15 12:05:11 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-04-21 12:53:02 +08:00
|
|
|
|
2013-02-01 02:06:18 +01:00
|
|
|
|
2012-10-11 21:03:33 -07:00
|
|
|
|
|
|
|
|
|
2019-03-15 17:39:03 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-18 21:49:48 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-03-15 17:39:03 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-07-07 18:48:28 +09:00
|
|
|
|
2019-03-15 17:39:03 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-16 09:54:03 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-01-21 12:14:57 +02:00
|
|
|
|
2023-06-16 09:54:03 +03:00
|
|
|
|
|
|
|
|
|
2019-01-21 12:14:57 +02:00
|
|
|
|
|
|
|
|
|
2023-06-16 09:54:03 +03:00
|
|
|
|
|
|
|
|
|
2019-01-21 12:14:57 +02:00
|
|
|
|
2023-06-16 09:54:03 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-01-21 12:14:57 +02:00
|
|
|
|
|
|
|
|
|
2023-06-16 09:54:03 +03:00
|
|
|
|
|
|
|
|
|
2019-03-15 17:39:03 +02:00
|
|
|
|
2023-12-20 16:19:52 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-16 09:54:03 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-12-25 15:37:25 +08:00
|
|
|
|
|
|
|
|
|
2023-06-16 09:54:03 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-12-25 15:37:25 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-16 09:54:03 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-01-21 12:14:57 +02:00
|
|
|
|
2023-06-16 09:54:03 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-01-21 12:14:57 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-12-25 15:37:25 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-07-01 17:33:27 +08:00
|
|
|
|
2024-12-25 15:37:25 +08:00
|
|
|
|
2026-07-01 17:33:27 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-12-25 15:37:25 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-16 09:54:03 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-01-29 14:00:58 +02:00
|
|
|
|
2023-06-16 09:54:03 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-03-15 17:39:03 +02:00
|
|
|
|
2023-06-16 09:54:03 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-01-21 12:14:57 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-16 09:54:03 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-01-21 12:14:57 +02:00
|
|
|
|
2023-06-16 09:54:03 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-01-21 12:14:57 +02:00
|
|
|
|
2023-06-16 09:54:03 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-01-21 12:14:57 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-12-20 16:19:52 +01:00
|
|
|
|
2019-01-21 12:14:57 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-09-30 13:11:30 +02:00
|
|
|
|
2019-01-21 12:14:57 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-09-30 13:11:30 +02:00
|
|
|
|
|
|
|
|
|
2019-01-21 12:14:57 +02:00
|
|
|
|
2021-09-30 13:11:30 +02:00
|
|
|
|
2019-01-21 12:14:57 +02:00
|
|
|
|
2021-09-30 13:11:30 +02:00
|
|
|
|
2019-01-21 12:14:57 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-01-21 12:25:59 +02:00
|
|
|
|
|
|
|
|
|
2019-01-21 12:14:57 +02:00
|
|
|
|
2021-09-30 13:11:32 +02:00
|
|
|
|
2019-01-21 12:25:59 +02:00
|
|
|
|
2019-01-21 12:14:57 +02:00
|
|
|
|
|
|
|
|
|
2021-09-30 13:11:32 +02:00
|
|
|
|
|
|
|
|
|
2019-01-21 12:14:57 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-09-30 13:11:32 +02:00
|
|
|
|
|
|
|
|
|
2021-09-30 13:11:21 +02:00
|
|
|
|
2019-01-21 12:14:57 +02:00
|
|
|
|
2021-09-30 13:11:21 +02:00
|
|
|
|
2019-01-21 12:14:57 +02:00
|
|
|
|
|
|
|
|
|
2021-09-30 13:11:21 +02:00
|
|
|
|
|
|
|
|
|
2022-10-01 00:01:44 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-01-21 12:14:57 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-04-21 12:53:02 +08:00
|
|
|
|
2012-10-11 21:03:34 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-04-21 12:53:02 +08:00
|
|
|
|
2013-02-01 01:05:43 +01:00
|
|
|
|
2014-04-21 12:53:02 +08:00
|
|
|
|
2012-10-11 21:03:34 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-04-21 12:53:02 +08:00
|
|
|
|
2013-02-01 02:06:18 +01:00
|
|
|
|
2012-10-11 21:03:34 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-04-21 12:53:02 +08:00
|
|
|
|
2012-10-11 21:03:34 -07:00
|
|
|
|
|
|
|
|
|
2016-11-15 12:05:11 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-09-18 11:33:13 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-01-29 22:09:19 +01:00
|
|
|
|
|
|
|
|
|
2020-09-18 11:33:13 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-02-04 11:03:39 +01:00
|
|
|
|
2020-09-18 11:33:13 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-18 21:49:52 +03:00
|
|
|
|
2020-09-18 11:33:13 +02:00
|
|
|
|
2023-06-18 21:49:52 +03:00
|
|
|
|
|
|
|
|
|
2023-06-19 16:26:52 +03:00
|
|
|
|
|
|
|
|
|
2023-06-18 21:49:52 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-18 21:49:54 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-19 16:26:52 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-18 21:49:52 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-19 16:26:52 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-18 21:49:52 +03:00
|
|
|
|
2020-09-18 11:33:13 +02:00
|
|
|
|
2023-04-24 10:32:24 +03:00
|
|
|
|
2023-06-18 21:49:52 +03:00
|
|
|
|
2023-04-24 10:32:24 +03:00
|
|
|
|
|
|
|
|
|
2020-09-18 11:33:13 +02:00
|
|
|
|
2023-06-18 21:49:52 +03:00
|
|
|
|
2020-09-18 11:33:13 +02:00
|
|
|
|
|
|
|
|
|
2023-06-18 21:49:52 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-09-18 11:33:13 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-18 21:49:52 +03:00
|
|
|
|
2020-09-18 11:33:13 +02:00
|
|
|
|
|
|
|
|
|
2023-06-18 21:49:52 +03:00
|
|
|
|
2020-09-18 11:33:13 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-02-28 09:55:41 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-09-18 11:33:13 +02:00
|
|
|
|
2024-02-16 13:54:30 +02:00
|
|
|
|
2020-09-18 11:33:13 +02:00
|
|
|
|
|
|
|
|
|
2024-02-16 13:54:30 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-09-18 11:33:13 +02:00
|
|
|
|
2024-02-16 13:54:30 +02:00
|
|
|
|
|
|
|
|
|
2020-09-18 11:33:13 +02:00
|
|
|
|
2023-06-18 21:50:01 +03:00
|
|
|
|
2024-02-16 13:54:30 +02:00
|
|
|
|
2023-06-18 21:50:01 +03:00
|
|
|
|
2024-02-16 13:54:30 +02:00
|
|
|
|
2020-09-18 11:33:13 +02:00
|
|
|
|
2024-02-16 13:54:30 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-09-18 11:33:13 +02:00
|
|
|
|
2024-02-16 13:54:30 +02:00
|
|
|
|
2020-09-18 11:33:13 +02:00
|
|
|
|
2024-02-16 13:54:30 +02:00
|
|
|
|
|
|
|
|
|
2020-09-18 11:33:13 +02:00
|
|
|
|
2024-02-16 13:54:30 +02:00
|
|
|
|
|
|
|
|
|
2023-06-18 21:50:01 +03:00
|
|
|
|
|
|
|
|
|
2024-02-16 13:54:30 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-18 21:50:01 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-09-18 11:33:13 +02:00
|
|
|
|
|
|
|
|
|
2024-02-16 13:54:30 +02:00
|
|
|
|
|
|
|
|
|
2020-09-18 11:33:13 +02:00
|
|
|
|
|
|
|
|
|
2024-02-16 13:54:30 +02:00
|
|
|
|
|
|
|
|
|
2024-02-28 09:55:41 +01:00
|
|
|
|
2024-02-16 13:54:30 +02: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
|
|
|
|
2024-02-16 13:54:30 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-01-01 07:05:26 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-02-16 13:54:30 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-09-18 11:33:13 +02:00
|
|
|
|
2024-02-04 11:03:39 +01:00
|
|
|
|
2020-09-18 11:33:13 +02:00
|
|
|
|
2025-06-09 21:35:19 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-09-18 11:33:13 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-12-30 10:36:14 -08:00
|
|
|
|
2020-09-18 11:33:13 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-10-29 22:24:07 +00:00
|
|
|
|
2020-09-18 11:33:13 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-02-02 10:49:37 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-09-18 11:33:13 +02:00
|
|
|
|
2022-02-02 10:49:37 +02:00
|
|
|
|
2020-09-18 11:33:13 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-06-09 21:35:23 +03:00
|
|
|
|
|
|
|
|
|
2020-09-18 11:33:13 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-06-09 21:35:19 +03:00
|
|
|
|
2020-09-18 11:33:13 +02:00
|
|
|
|
2020-11-29 17:30:48 +02:00
|
|
|
|
2020-09-18 11:33:13 +02:00
|
|
|
|
wifi: cfg80211: fix 6 GHz scan request building
The 6 GHz scan request struct allocated by cfg80211_scan_6ghz() is
meant to be formed this way:
[base struct][channels][ssids][6ghz_params]
It is allocated with [channels] as the maximum number of channels
supported by the driver in the 6 GHz band, since allocation is
before knowing how many there will be.
However, the inner pointers are set incorrectly: initially, the
6 GHz scan parameters pointer is set:
[base struct][channels]
^ scan_6ghz_params
and later the SSID pointer is set to the end of the actually
_used_ channels.
[base struct][channels]
^ ssids
If many APs were to be discovered, and many channels used, and
there were many SSIDs, then the SSIDs could overlap the 6 GHz
parameters.
Additionally, the request->ssids for most of the function points
to the original request still (given the struct copy) but is used
normally, which is confusing.
Clear this up, by actually using the allocated space for 6 GHz
parameters _after_ the SSIDs, and set up the SSIDs initially so
they are used more clearly. Just like in nl80211.c, set them
only if there actually are SSIDs though.
Finally, also copy the elements (ie/ie_len) so they're part of
the same request, not pointing to the old request.
Co-developed-by: Miri Korenblit <miriam.rachel.korenblit@intel.com>
Signed-off-by: Miri Korenblit <miriam.rachel.korenblit@intel.com>
Reviewed-by: Ilan Peer <ilan.peer@intel.com>
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Link: https://msgid.link/20240510113738.4190692ef4ee.I0cb19188be17a8abd029805e3373c0a7777c214c@changeid
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2024-05-10 11:37:38 +02:00
|
|
|
|
2020-09-18 11:33:13 +02:00
|
|
|
|
2025-06-09 21:35:19 +03:00
|
|
|
|
2025-06-09 21:35:23 +03:00
|
|
|
|
2020-09-18 11:33:13 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-06-09 21:35:19 +03:00
|
|
|
|
2020-09-18 11:33:13 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-06-09 21:35:19 +03:00
|
|
|
|
2020-09-18 11:33:13 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-09-28 17:35:30 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-09-18 11:33:13 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-09-28 17:35:30 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-06-09 21:35:19 +03:00
|
|
|
|
|
|
|
|
|
2023-09-28 17:35:30 +03: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
|
|
|
|
2023-09-28 17:35:30 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-09-18 11:33:13 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-06-09 21:35:19 +03:00
|
|
|
|
wifi: cfg80211: fix 6 GHz scan request building
The 6 GHz scan request struct allocated by cfg80211_scan_6ghz() is
meant to be formed this way:
[base struct][channels][ssids][6ghz_params]
It is allocated with [channels] as the maximum number of channels
supported by the driver in the 6 GHz band, since allocation is
before knowing how many there will be.
However, the inner pointers are set incorrectly: initially, the
6 GHz scan parameters pointer is set:
[base struct][channels]
^ scan_6ghz_params
and later the SSID pointer is set to the end of the actually
_used_ channels.
[base struct][channels]
^ ssids
If many APs were to be discovered, and many channels used, and
there were many SSIDs, then the SSIDs could overlap the 6 GHz
parameters.
Additionally, the request->ssids for most of the function points
to the original request still (given the struct copy) but is used
normally, which is confusing.
Clear this up, by actually using the allocated space for 6 GHz
parameters _after_ the SSIDs, and set up the SSIDs initially so
they are used more clearly. Just like in nl80211.c, set them
only if there actually are SSIDs though.
Finally, also copy the elements (ie/ie_len) so they're part of
the same request, not pointing to the old request.
Co-developed-by: Miri Korenblit <miriam.rachel.korenblit@intel.com>
Signed-off-by: Miri Korenblit <miriam.rachel.korenblit@intel.com>
Reviewed-by: Ilan Peer <ilan.peer@intel.com>
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Link: https://msgid.link/20240510113738.4190692ef4ee.I0cb19188be17a8abd029805e3373c0a7777c214c@changeid
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2024-05-10 11:37:38 +02:00
|
|
|
|
2025-06-09 21:35:19 +03:00
|
|
|
|
wifi: cfg80211: fix 6 GHz scan request building
The 6 GHz scan request struct allocated by cfg80211_scan_6ghz() is
meant to be formed this way:
[base struct][channels][ssids][6ghz_params]
It is allocated with [channels] as the maximum number of channels
supported by the driver in the 6 GHz band, since allocation is
before knowing how many there will be.
However, the inner pointers are set incorrectly: initially, the
6 GHz scan parameters pointer is set:
[base struct][channels]
^ scan_6ghz_params
and later the SSID pointer is set to the end of the actually
_used_ channels.
[base struct][channels]
^ ssids
If many APs were to be discovered, and many channels used, and
there were many SSIDs, then the SSIDs could overlap the 6 GHz
parameters.
Additionally, the request->ssids for most of the function points
to the original request still (given the struct copy) but is used
normally, which is confusing.
Clear this up, by actually using the allocated space for 6 GHz
parameters _after_ the SSIDs, and set up the SSIDs initially so
they are used more clearly. Just like in nl80211.c, set them
only if there actually are SSIDs though.
Finally, also copy the elements (ie/ie_len) so they're part of
the same request, not pointing to the old request.
Co-developed-by: Miri Korenblit <miriam.rachel.korenblit@intel.com>
Signed-off-by: Miri Korenblit <miriam.rachel.korenblit@intel.com>
Reviewed-by: Ilan Peer <ilan.peer@intel.com>
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Link: https://msgid.link/20240510113738.4190692ef4ee.I0cb19188be17a8abd029805e3373c0a7777c214c@changeid
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2024-05-10 11:37:38 +02:00
|
|
|
|
2025-06-09 21:35:19 +03:00
|
|
|
|
wifi: cfg80211: fix 6 GHz scan request building
The 6 GHz scan request struct allocated by cfg80211_scan_6ghz() is
meant to be formed this way:
[base struct][channels][ssids][6ghz_params]
It is allocated with [channels] as the maximum number of channels
supported by the driver in the 6 GHz band, since allocation is
before knowing how many there will be.
However, the inner pointers are set incorrectly: initially, the
6 GHz scan parameters pointer is set:
[base struct][channels]
^ scan_6ghz_params
and later the SSID pointer is set to the end of the actually
_used_ channels.
[base struct][channels]
^ ssids
If many APs were to be discovered, and many channels used, and
there were many SSIDs, then the SSIDs could overlap the 6 GHz
parameters.
Additionally, the request->ssids for most of the function points
to the original request still (given the struct copy) but is used
normally, which is confusing.
Clear this up, by actually using the allocated space for 6 GHz
parameters _after_ the SSIDs, and set up the SSIDs initially so
they are used more clearly. Just like in nl80211.c, set them
only if there actually are SSIDs though.
Finally, also copy the elements (ie/ie_len) so they're part of
the same request, not pointing to the old request.
Co-developed-by: Miri Korenblit <miriam.rachel.korenblit@intel.com>
Signed-off-by: Miri Korenblit <miriam.rachel.korenblit@intel.com>
Reviewed-by: Ilan Peer <ilan.peer@intel.com>
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Link: https://msgid.link/20240510113738.4190692ef4ee.I0cb19188be17a8abd029805e3373c0a7777c214c@changeid
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2024-05-10 11:37:38 +02:00
|
|
|
|
2025-06-09 21:35:19 +03:00
|
|
|
|
wifi: cfg80211: fix 6 GHz scan request building
The 6 GHz scan request struct allocated by cfg80211_scan_6ghz() is
meant to be formed this way:
[base struct][channels][ssids][6ghz_params]
It is allocated with [channels] as the maximum number of channels
supported by the driver in the 6 GHz band, since allocation is
before knowing how many there will be.
However, the inner pointers are set incorrectly: initially, the
6 GHz scan parameters pointer is set:
[base struct][channels]
^ scan_6ghz_params
and later the SSID pointer is set to the end of the actually
_used_ channels.
[base struct][channels]
^ ssids
If many APs were to be discovered, and many channels used, and
there were many SSIDs, then the SSIDs could overlap the 6 GHz
parameters.
Additionally, the request->ssids for most of the function points
to the original request still (given the struct copy) but is used
normally, which is confusing.
Clear this up, by actually using the allocated space for 6 GHz
parameters _after_ the SSIDs, and set up the SSIDs initially so
they are used more clearly. Just like in nl80211.c, set them
only if there actually are SSIDs though.
Finally, also copy the elements (ie/ie_len) so they're part of
the same request, not pointing to the old request.
Co-developed-by: Miri Korenblit <miriam.rachel.korenblit@intel.com>
Signed-off-by: Miri Korenblit <miriam.rachel.korenblit@intel.com>
Reviewed-by: Ilan Peer <ilan.peer@intel.com>
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Link: https://msgid.link/20240510113738.4190692ef4ee.I0cb19188be17a8abd029805e3373c0a7777c214c@changeid
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2024-05-10 11:37:38 +02:00
|
|
|
|
|
|
|
|
|
2020-09-18 11:33:13 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-06-09 21:35:19 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
wifi: cfg80211: fix 6 GHz scan request building
The 6 GHz scan request struct allocated by cfg80211_scan_6ghz() is
meant to be formed this way:
[base struct][channels][ssids][6ghz_params]
It is allocated with [channels] as the maximum number of channels
supported by the driver in the 6 GHz band, since allocation is
before knowing how many there will be.
However, the inner pointers are set incorrectly: initially, the
6 GHz scan parameters pointer is set:
[base struct][channels]
^ scan_6ghz_params
and later the SSID pointer is set to the end of the actually
_used_ channels.
[base struct][channels]
^ ssids
If many APs were to be discovered, and many channels used, and
there were many SSIDs, then the SSIDs could overlap the 6 GHz
parameters.
Additionally, the request->ssids for most of the function points
to the original request still (given the struct copy) but is used
normally, which is confusing.
Clear this up, by actually using the allocated space for 6 GHz
parameters _after_ the SSIDs, and set up the SSIDs initially so
they are used more clearly. Just like in nl80211.c, set them
only if there actually are SSIDs though.
Finally, also copy the elements (ie/ie_len) so they're part of
the same request, not pointing to the old request.
Co-developed-by: Miri Korenblit <miriam.rachel.korenblit@intel.com>
Signed-off-by: Miri Korenblit <miriam.rachel.korenblit@intel.com>
Reviewed-by: Ilan Peer <ilan.peer@intel.com>
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Link: https://msgid.link/20240510113738.4190692ef4ee.I0cb19188be17a8abd029805e3373c0a7777c214c@changeid
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2024-05-10 11:37:38 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-06-09 21:35:19 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
wifi: cfg80211: fix 6 GHz scan request building
The 6 GHz scan request struct allocated by cfg80211_scan_6ghz() is
meant to be formed this way:
[base struct][channels][ssids][6ghz_params]
It is allocated with [channels] as the maximum number of channels
supported by the driver in the 6 GHz band, since allocation is
before knowing how many there will be.
However, the inner pointers are set incorrectly: initially, the
6 GHz scan parameters pointer is set:
[base struct][channels]
^ scan_6ghz_params
and later the SSID pointer is set to the end of the actually
_used_ channels.
[base struct][channels]
^ ssids
If many APs were to be discovered, and many channels used, and
there were many SSIDs, then the SSIDs could overlap the 6 GHz
parameters.
Additionally, the request->ssids for most of the function points
to the original request still (given the struct copy) but is used
normally, which is confusing.
Clear this up, by actually using the allocated space for 6 GHz
parameters _after_ the SSIDs, and set up the SSIDs initially so
they are used more clearly. Just like in nl80211.c, set them
only if there actually are SSIDs though.
Finally, also copy the elements (ie/ie_len) so they're part of
the same request, not pointing to the old request.
Co-developed-by: Miri Korenblit <miriam.rachel.korenblit@intel.com>
Signed-off-by: Miri Korenblit <miriam.rachel.korenblit@intel.com>
Reviewed-by: Ilan Peer <ilan.peer@intel.com>
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Link: https://msgid.link/20240510113738.4190692ef4ee.I0cb19188be17a8abd029805e3373c0a7777c214c@changeid
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2024-05-10 11:37:38 +02:00
|
|
|
|
2025-06-09 21:35:19 +03:00
|
|
|
|
wifi: cfg80211: fix 6 GHz scan request building
The 6 GHz scan request struct allocated by cfg80211_scan_6ghz() is
meant to be formed this way:
[base struct][channels][ssids][6ghz_params]
It is allocated with [channels] as the maximum number of channels
supported by the driver in the 6 GHz band, since allocation is
before knowing how many there will be.
However, the inner pointers are set incorrectly: initially, the
6 GHz scan parameters pointer is set:
[base struct][channels]
^ scan_6ghz_params
and later the SSID pointer is set to the end of the actually
_used_ channels.
[base struct][channels]
^ ssids
If many APs were to be discovered, and many channels used, and
there were many SSIDs, then the SSIDs could overlap the 6 GHz
parameters.
Additionally, the request->ssids for most of the function points
to the original request still (given the struct copy) but is used
normally, which is confusing.
Clear this up, by actually using the allocated space for 6 GHz
parameters _after_ the SSIDs, and set up the SSIDs initially so
they are used more clearly. Just like in nl80211.c, set them
only if there actually are SSIDs though.
Finally, also copy the elements (ie/ie_len) so they're part of
the same request, not pointing to the old request.
Co-developed-by: Miri Korenblit <miriam.rachel.korenblit@intel.com>
Signed-off-by: Miri Korenblit <miriam.rachel.korenblit@intel.com>
Reviewed-by: Ilan Peer <ilan.peer@intel.com>
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Link: https://msgid.link/20240510113738.4190692ef4ee.I0cb19188be17a8abd029805e3373c0a7777c214c@changeid
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2024-05-10 11:37:38 +02:00
|
|
|
|
2025-06-09 21:35:19 +03:00
|
|
|
|
wifi: cfg80211: fix 6 GHz scan request building
The 6 GHz scan request struct allocated by cfg80211_scan_6ghz() is
meant to be formed this way:
[base struct][channels][ssids][6ghz_params]
It is allocated with [channels] as the maximum number of channels
supported by the driver in the 6 GHz band, since allocation is
before knowing how many there will be.
However, the inner pointers are set incorrectly: initially, the
6 GHz scan parameters pointer is set:
[base struct][channels]
^ scan_6ghz_params
and later the SSID pointer is set to the end of the actually
_used_ channels.
[base struct][channels]
^ ssids
If many APs were to be discovered, and many channels used, and
there were many SSIDs, then the SSIDs could overlap the 6 GHz
parameters.
Additionally, the request->ssids for most of the function points
to the original request still (given the struct copy) but is used
normally, which is confusing.
Clear this up, by actually using the allocated space for 6 GHz
parameters _after_ the SSIDs, and set up the SSIDs initially so
they are used more clearly. Just like in nl80211.c, set them
only if there actually are SSIDs though.
Finally, also copy the elements (ie/ie_len) so they're part of
the same request, not pointing to the old request.
Co-developed-by: Miri Korenblit <miriam.rachel.korenblit@intel.com>
Signed-off-by: Miri Korenblit <miriam.rachel.korenblit@intel.com>
Reviewed-by: Ilan Peer <ilan.peer@intel.com>
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Link: https://msgid.link/20240510113738.4190692ef4ee.I0cb19188be17a8abd029805e3373c0a7777c214c@changeid
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2024-05-10 11:37:38 +02:00
|
|
|
|
|
|
|
|
|
2025-06-09 21:35:19 +03:00
|
|
|
|
|
|
|
|
|
wifi: cfg80211: fix 6 GHz scan request building
The 6 GHz scan request struct allocated by cfg80211_scan_6ghz() is
meant to be formed this way:
[base struct][channels][ssids][6ghz_params]
It is allocated with [channels] as the maximum number of channels
supported by the driver in the 6 GHz band, since allocation is
before knowing how many there will be.
However, the inner pointers are set incorrectly: initially, the
6 GHz scan parameters pointer is set:
[base struct][channels]
^ scan_6ghz_params
and later the SSID pointer is set to the end of the actually
_used_ channels.
[base struct][channels]
^ ssids
If many APs were to be discovered, and many channels used, and
there were many SSIDs, then the SSIDs could overlap the 6 GHz
parameters.
Additionally, the request->ssids for most of the function points
to the original request still (given the struct copy) but is used
normally, which is confusing.
Clear this up, by actually using the allocated space for 6 GHz
parameters _after_ the SSIDs, and set up the SSIDs initially so
they are used more clearly. Just like in nl80211.c, set them
only if there actually are SSIDs though.
Finally, also copy the elements (ie/ie_len) so they're part of
the same request, not pointing to the old request.
Co-developed-by: Miri Korenblit <miriam.rachel.korenblit@intel.com>
Signed-off-by: Miri Korenblit <miriam.rachel.korenblit@intel.com>
Reviewed-by: Ilan Peer <ilan.peer@intel.com>
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Link: https://msgid.link/20240510113738.4190692ef4ee.I0cb19188be17a8abd029805e3373c0a7777c214c@changeid
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2024-05-10 11:37:38 +02:00
|
|
|
|
2020-09-18 11:33:13 +02:00
|
|
|
|
|
|
|
|
|
2020-11-29 17:30:48 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-09-18 11:33:13 +02:00
|
|
|
|
2025-06-09 21:35:19 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-09-18 11:33:13 +02:00
|
|
|
|
2020-11-29 17:30:48 +02:00
|
|
|
|
2025-06-09 21:35:19 +03:00
|
|
|
|
2020-11-29 17:30:48 +02:00
|
|
|
|
2020-09-18 11:33:13 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-06-09 21:35:19 +03:00
|
|
|
|
|
|
|
|
|
2020-09-18 11:33:13 +02:00
|
|
|
|
2025-06-09 21:35:19 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-09-18 11:33:13 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-06-09 21:35:19 +03:00
|
|
|
|
2020-09-18 11:33:13 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-06-09 21:35:19 +03:00
|
|
|
|
2020-09-18 11:33:13 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-10-09 10:25:42 +02:00
|
|
|
|
2025-06-09 21:35:19 +03:00
|
|
|
|
2020-09-18 11:33:13 +02:00
|
|
|
|
|
|
|
|
|
2025-06-09 21:35:19 +03:00
|
|
|
|
|
|
|
|
|
2020-09-18 11:33:13 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-06-09 21:35:19 +03:00
|
|
|
|
|
|
|
|
|
2020-09-18 11:33:13 +02:00
|
|
|
|
|
|
|
|
|
2025-06-09 21:35:19 +03:00
|
|
|
|
|
|
|
|
|
2023-09-18 14:10:54 +03:00
|
|
|
|
|
|
|
|
|
2025-06-09 21:35:19 +03:00
|
|
|
|
|
|
|
|
|
2022-02-02 10:49:37 +02:00
|
|
|
|
|
|
|
|
|
2025-06-09 21:35:19 +03:00
|
|
|
|
2020-09-18 11:33:13 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-19 16:26:52 +03:00
|
|
|
|
2020-09-18 11:33:13 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-06-09 21:35:19 +03:00
|
|
|
|
2020-09-18 11:33:13 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-06-09 21:35:19 +03:00
|
|
|
|
|
|
|
|
|
2020-09-18 11:33:13 +02:00
|
|
|
|
wifi: cfg80211: fix 6 GHz scan request building
The 6 GHz scan request struct allocated by cfg80211_scan_6ghz() is
meant to be formed this way:
[base struct][channels][ssids][6ghz_params]
It is allocated with [channels] as the maximum number of channels
supported by the driver in the 6 GHz band, since allocation is
before knowing how many there will be.
However, the inner pointers are set incorrectly: initially, the
6 GHz scan parameters pointer is set:
[base struct][channels]
^ scan_6ghz_params
and later the SSID pointer is set to the end of the actually
_used_ channels.
[base struct][channels]
^ ssids
If many APs were to be discovered, and many channels used, and
there were many SSIDs, then the SSIDs could overlap the 6 GHz
parameters.
Additionally, the request->ssids for most of the function points
to the original request still (given the struct copy) but is used
normally, which is confusing.
Clear this up, by actually using the allocated space for 6 GHz
parameters _after_ the SSIDs, and set up the SSIDs initially so
they are used more clearly. Just like in nl80211.c, set them
only if there actually are SSIDs though.
Finally, also copy the elements (ie/ie_len) so they're part of
the same request, not pointing to the old request.
Co-developed-by: Miri Korenblit <miriam.rachel.korenblit@intel.com>
Signed-off-by: Miri Korenblit <miriam.rachel.korenblit@intel.com>
Reviewed-by: Ilan Peer <ilan.peer@intel.com>
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Link: https://msgid.link/20240510113738.4190692ef4ee.I0cb19188be17a8abd029805e3373c0a7777c214c@changeid
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2024-05-10 11:37:38 +02:00
|
|
|
|
2021-06-18 13:41:41 +03:00
|
|
|
|
2020-09-18 11:33:13 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-06-09 21:35:23 +03:00
|
|
|
|
2020-09-18 11:33:13 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-06-09 21:35:19 +03:00
|
|
|
|
|
|
|
|
|
2020-09-18 11:33:13 +02:00
|
|
|
|
2026-06-01 12:41:56 +03:00
|
|
|
|
2020-09-18 11:33:13 +02:00
|
|
|
|
2025-06-09 21:35:23 +03:00
|
|
|
|
|
|
|
|
|
2020-09-18 11:33:13 +02:00
|
|
|
|
2025-06-09 21:35:23 +03:00
|
|
|
|
2020-09-18 11:33:13 +02:00
|
|
|
|
2025-06-09 21:35:19 +03:00
|
|
|
|
|
|
|
|
|
2020-09-18 11:33:13 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-06-09 21:35:23 +03:00
|
|
|
|
2020-09-18 11:33:13 +02:00
|
|
|
|
2026-02-21 17:06:51 -08:00
|
|
|
|
2020-09-18 11:33:13 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-06-09 21:35:19 +03:00
|
|
|
|
2020-09-18 11:33:13 +02:00
|
|
|
|
2025-06-09 21:35:19 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-09-18 11:33:13 +02:00
|
|
|
|
|
|
|
|
|
2025-06-09 21:35:19 +03:00
|
|
|
|
2025-06-09 21:35:23 +03:00
|
|
|
|
2026-06-01 12:41:56 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-09-18 11:33:13 +02:00
|
|
|
|
2026-06-01 12:41:56 +03:00
|
|
|
|
2020-09-18 11:33:13 +02:00
|
|
|
|
|
|
|
|
|
2026-09-04 16:55:03 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
cfg80211: send scan results from work queue
Due to the previous commit, when a scan finishes, it is in theory
possible to hit the following sequence:
1. interface starts being removed
2. scan is cancelled by driver and cfg80211 is notified
3. scan done work is scheduled
4. interface is removed completely, rdev->scan_req is freed,
event sent to userspace but scan done work remains pending
5. new scan is requested on another virtual interface
6. scan done work runs, freeing the still-running scan
To fix this situation, hang on to the scan done message and block
new scans while that is the case, and only send the message from
the work function, regardless of whether the scan_req is already
freed from interface removal. This makes step 5 above impossible
and changes step 6 to be
5. scan done work runs, sending the scan done message
As this can't work for wext, so we send the message immediately,
but this shouldn't be an issue since we still return -EBUSY.
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2014-01-22 11:14:19 +02:00
|
|
|
|
|
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
2025-06-09 21:35:19 +03:00
|
|
|
|
2012-06-18 19:17:03 +02:00
|
|
|
|
cfg80211: send scan results from work queue
Due to the previous commit, when a scan finishes, it is in theory
possible to hit the following sequence:
1. interface starts being removed
2. scan is cancelled by driver and cfg80211 is notified
3. scan done work is scheduled
4. interface is removed completely, rdev->scan_req is freed,
event sent to userspace but scan done work remains pending
5. new scan is requested on another virtual interface
6. scan done work runs, freeing the still-running scan
To fix this situation, hang on to the scan done message and block
new scans while that is the case, and only send the message from
the work function, regardless of whether the scan_req is already
freed from interface removal. This makes step 5 above impossible
and changes step 6 to be
5. scan done work runs, sending the scan done message
As this can't work for wext, so we send the message immediately,
but this shouldn't be an issue since we still return -EBUSY.
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2014-01-22 11:14:19 +02:00
|
|
|
|
2009-09-29 23:27:28 +02:00
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-01-22 16:19:43 +01:00
|
|
|
|
2009-08-20 21:36:16 +02:00
|
|
|
|
cfg80211: send scan results from work queue
Due to the previous commit, when a scan finishes, it is in theory
possible to hit the following sequence:
1. interface starts being removed
2. scan is cancelled by driver and cfg80211 is notified
3. scan done work is scheduled
4. interface is removed completely, rdev->scan_req is freed,
event sent to userspace but scan done work remains pending
5. new scan is requested on another virtual interface
6. scan done work runs, freeing the still-running scan
To fix this situation, hang on to the scan done message and block
new scans while that is the case, and only send the message from
the work function, regardless of whether the scan_req is already
freed from interface removal. This makes step 5 above impossible
and changes step 6 to be
5. scan done work runs, sending the scan done message
As this can't work for wext, so we send the message immediately,
but this shouldn't be an issue since we still return -EBUSY.
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2014-01-22 11:14:19 +02:00
|
|
|
|
2016-12-16 11:21:54 +00:00
|
|
|
|
cfg80211: send scan results from work queue
Due to the previous commit, when a scan finishes, it is in theory
possible to hit the following sequence:
1. interface starts being removed
2. scan is cancelled by driver and cfg80211 is notified
3. scan done work is scheduled
4. interface is removed completely, rdev->scan_req is freed,
event sent to userspace but scan done work remains pending
5. new scan is requested on another virtual interface
6. scan done work runs, freeing the still-running scan
To fix this situation, hang on to the scan done message and block
new scans while that is the case, and only send the message from
the work function, regardless of whether the scan_req is already
freed from interface removal. This makes step 5 above impossible
and changes step 6 to be
5. scan done work runs, sending the scan done message
As this can't work for wext, so we send the message immediately,
but this shouldn't be an issue since we still return -EBUSY.
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2014-01-22 11:14:19 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-07-07 03:56:11 +02:00
|
|
|
|
2020-09-18 11:33:13 +02:00
|
|
|
|
|
|
|
|
|
2009-08-20 21:36:16 +02:00
|
|
|
|
|
|
|
|
|
2025-06-09 21:35:19 +03:00
|
|
|
|
2020-09-18 11:33:13 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-06-09 21:35:19 +03:00
|
|
|
|
2025-06-09 21:35:23 +03:00
|
|
|
|
2020-09-18 11:33:13 +02:00
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
2009-07-02 09:13:27 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-06-18 19:17:03 +02:00
|
|
|
|
|
|
|
|
|
2009-07-02 09:13:27 +02:00
|
|
|
|
2016-07-05 17:10:13 +03:00
|
|
|
|
2025-06-09 21:35:19 +03:00
|
|
|
|
cfg80211: send scan results from work queue
Due to the previous commit, when a scan finishes, it is in theory
possible to hit the following sequence:
1. interface starts being removed
2. scan is cancelled by driver and cfg80211 is notified
3. scan done work is scheduled
4. interface is removed completely, rdev->scan_req is freed,
event sent to userspace but scan done work remains pending
5. new scan is requested on another virtual interface
6. scan done work runs, freeing the still-running scan
To fix this situation, hang on to the scan done message and block
new scans while that is the case, and only send the message from
the work function, regardless of whether the scan_req is already
freed from interface removal. This makes step 5 above impossible
and changes step 6 to be
5. scan done work runs, sending the scan done message
As this can't work for wext, so we send the message immediately,
but this shouldn't be an issue since we still return -EBUSY.
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2014-01-22 11:14:19 +02:00
|
|
|
|
|
|
|
|
|
2025-06-09 21:35:19 +03:00
|
|
|
|
cfg80211: send scan results from work queue
Due to the previous commit, when a scan finishes, it is in theory
possible to hit the following sequence:
1. interface starts being removed
2. scan is cancelled by driver and cfg80211 is notified
3. scan done work is scheduled
4. interface is removed completely, rdev->scan_req is freed,
event sent to userspace but scan done work remains pending
5. new scan is requested on another virtual interface
6. scan done work runs, freeing the still-running scan
To fix this situation, hang on to the scan done message and block
new scans while that is the case, and only send the message from
the work function, regardless of whether the scan_req is already
freed from interface removal. This makes step 5 above impossible
and changes step 6 to be
5. scan done work runs, sending the scan done message
As this can't work for wext, so we send the message immediately,
but this shouldn't be an issue since we still return -EBUSY.
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2014-01-22 11:14:19 +02:00
|
|
|
|
2012-10-11 21:03:34 -07:00
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
2016-07-05 17:10:13 +03:00
|
|
|
|
cfg80211: send scan results from work queue
Due to the previous commit, when a scan finishes, it is in theory
possible to hit the following sequence:
1. interface starts being removed
2. scan is cancelled by driver and cfg80211 is notified
3. scan done work is scheduled
4. interface is removed completely, rdev->scan_req is freed,
event sent to userspace but scan done work remains pending
5. new scan is requested on another virtual interface
6. scan done work runs, freeing the still-running scan
To fix this situation, hang on to the scan done message and block
new scans while that is the case, and only send the message from
the work function, regardless of whether the scan_req is already
freed from interface removal. This makes step 5 above impossible
and changes step 6 to be
5. scan done work runs, sending the scan done message
As this can't work for wext, so we send the message immediately,
but this shouldn't be an issue since we still return -EBUSY.
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2014-01-22 11:14:19 +02:00
|
|
|
|
2009-09-29 23:27:28 +02:00
|
|
|
|
2016-07-05 17:10:13 +03:00
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
|
|
|
|
|
2012-06-18 19:17:03 +02:00
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-08-05 19:55:27 +08:00
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
2026-09-04 16:55:03 +02:00
|
|
|
|
2020-09-18 11:33:13 +02:00
|
|
|
|
|
|
|
|
|
2026-09-04 16:55:03 +02:00
|
|
|
|
2009-08-12 22:21:21 +02:00
|
|
|
|
cfg80211: send scan results from work queue
Due to the previous commit, when a scan finishes, it is in theory
possible to hit the following sequence:
1. interface starts being removed
2. scan is cancelled by driver and cfg80211 is notified
3. scan done work is scheduled
4. interface is removed completely, rdev->scan_req is freed,
event sent to userspace but scan done work remains pending
5. new scan is requested on another virtual interface
6. scan done work runs, freeing the still-running scan
To fix this situation, hang on to the scan done message and block
new scans while that is the case, and only send the message from
the work function, regardless of whether the scan_req is already
freed from interface removal. This makes step 5 above impossible
and changes step 6 to be
5. scan done work runs, sending the scan done message
As this can't work for wext, so we send the message immediately,
but this shouldn't be an issue since we still return -EBUSY.
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2014-01-22 11:14:19 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-12-16 11:21:54 +00:00
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
2009-07-07 03:56:11 +02:00
|
|
|
|
2023-06-06 14:49:33 +02:00
|
|
|
|
2009-08-12 22:21:21 +02:00
|
|
|
|
2023-06-06 14:49:33 +02:00
|
|
|
|
2009-08-12 22:21:21 +02:00
|
|
|
|
|
|
|
|
|
2016-07-05 17:10:13 +03:00
|
|
|
|
|
|
|
|
|
2009-07-07 03:56:11 +02:00
|
|
|
|
2025-06-09 21:35:19 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-09-18 11:33:13 +02:00
|
|
|
|
2025-06-09 21:35:19 +03:00
|
|
|
|
2026-09-04 16:55:03 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-06-09 21:35:19 +03:00
|
|
|
|
|
|
|
|
|
2009-07-07 03:56:11 +02:00
|
|
|
|
2025-06-09 21:35:19 +03:00
|
|
|
|
2020-09-18 11:33:13 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-06-09 21:35:19 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-09-18 11:33:13 +02:00
|
|
|
|
|
|
|
|
|
2025-06-09 21:35:19 +03:00
|
|
|
|
|
|
|
|
|
2009-07-07 03:56:11 +02:00
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
|
|
|
|
|
2017-04-21 13:05:00 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-01-22 16:19:43 +01:00
|
|
|
|
2017-04-21 13:05:00 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-01-22 16:19:43 +01:00
|
|
|
|
2017-04-21 13:05:00 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-02-19 14:41:04 +05:30
|
|
|
|
2021-01-22 16:19:43 +01:00
|
|
|
|
2017-04-21 13:05:00 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-04-28 13:40:28 +01:00
|
|
|
|
2017-04-21 13:05:00 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-04-28 13:40:28 +01:00
|
|
|
|
2011-05-11 17:09:35 +03:00
|
|
|
|
|
|
|
|
|
2017-04-28 13:40:28 +01:00
|
|
|
|
2011-05-11 17:09:35 +03:00
|
|
|
|
2017-04-28 13:40:28 +01:00
|
|
|
|
|
|
|
|
|
2011-05-11 17:09:35 +03:00
|
|
|
|
2024-11-22 09:42:25 +01:00
|
|
|
|
|
|
|
|
|
2017-04-28 13:40:28 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-10-11 21:03:34 -07:00
|
|
|
|
|
|
|
|
|
2011-05-11 17:09:35 +03:00
|
|
|
|
|
|
|
|
|
2017-04-28 13:40:28 +01:00
|
|
|
|
2011-05-11 17:09:35 +03:00
|
|
|
|
2017-04-21 13:05:00 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-04-28 13:40:28 +01:00
|
|
|
|
2011-05-11 17:09:35 +03:00
|
|
|
|
2014-12-15 13:25:38 +02:00
|
|
|
|
2017-05-23 09:58:07 +01:00
|
|
|
|
2017-04-28 13:40:28 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-05-23 09:58:07 +01:00
|
|
|
|
2011-05-11 17:09:35 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-01-22 16:19:43 +01:00
|
|
|
|
2011-05-11 17:09:35 +03:00
|
|
|
|
2014-04-21 12:53:03 +08:00
|
|
|
|
2011-05-11 17:09:35 +03:00
|
|
|
|
2021-01-22 16:19:43 +01:00
|
|
|
|
2014-04-30 16:14:23 +03:00
|
|
|
|
2017-04-28 13:40:28 +01:00
|
|
|
|
2012-08-27 12:49:39 +03:00
|
|
|
|
2017-04-28 13:40:28 +01:00
|
|
|
|
2014-04-30 16:14:23 +03:00
|
|
|
|
2021-01-22 16:19:43 +01:00
|
|
|
|
2014-04-30 16:14:23 +03:00
|
|
|
|
2017-04-28 13:40:28 +01:00
|
|
|
|
2014-04-30 16:14:23 +03:00
|
|
|
|
2024-11-22 09:42:25 +01:00
|
|
|
|
|
|
|
|
|
2021-01-22 16:19:43 +01:00
|
|
|
|
2011-05-11 17:09:35 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-04-21 13:05:00 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-05-11 17:09:35 +03:00
|
|
|
|
2021-01-22 16:19:43 +01:00
|
|
|
|
2011-05-11 17:09:35 +03:00
|
|
|
|
2011-05-12 16:28:29 +03:00
|
|
|
|
2017-04-21 13:05:02 +01:00
|
|
|
|
2011-05-12 16:28:29 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-05-11 17:09:35 +03:00
|
|
|
|
2017-04-21 13:05:00 +01:00
|
|
|
|
2011-05-11 17:09:35 +03:00
|
|
|
|
2017-04-21 13:05:00 +01:00
|
|
|
|
2011-05-11 17:09:35 +03:00
|
|
|
|
2011-06-29 22:49:33 +02:00
|
|
|
|
2011-05-11 17:09:35 +03:00
|
|
|
|
|
|
|
|
|
2017-04-21 13:05:00 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-01-22 16:19:43 +01:00
|
|
|
|
2017-04-21 13:05:00 +01:00
|
|
|
|
|
|
|
|
|
2017-04-28 13:40:28 +01:00
|
|
|
|
|
|
|
|
|
2017-04-21 13:05:00 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-04-21 12:53:02 +08:00
|
|
|
|
2009-02-11 17:14:43 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-02-19 20:32:40 +00:00
|
|
|
|
2009-02-11 17:14:43 -05:00
|
|
|
|
2014-04-21 12:53:02 +08:00
|
|
|
|
|
|
|
|
|
2009-02-11 17:14:43 -05:00
|
|
|
|
2014-04-21 12:53:02 +08:00
|
|
|
|
2009-02-11 17:14:43 -05:00
|
|
|
|
|
|
|
|
|
2014-04-21 12:53:02 +08:00
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
2014-04-21 12:53:02 +08:00
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
|
|
|
|
|
2020-06-25 14:15:24 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-02-07 23:26:38 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
2019-02-07 21:44:41 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-02-07 23:26:38 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
2016-09-15 18:15:09 +03:00
|
|
|
|
|
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
2019-02-07 23:26:38 +01:00
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
2019-02-07 23:26:38 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-09-15 11:53:01 +03:00
|
|
|
|
2019-02-07 23:26:38 +01:00
|
|
|
|
2016-09-15 18:15:09 +03:00
|
|
|
|
|
|
|
|
|
2011-09-15 11:53:01 +03:00
|
|
|
|
2016-05-03 16:08:07 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-02-07 23:26:38 +01:00
|
|
|
|
|
|
|
|
|
2011-09-15 11:53:01 +03:00
|
|
|
|
2019-02-07 23:26:38 +01:00
|
|
|
|
2016-09-15 18:15:09 +03:00
|
|
|
|
2013-02-12 20:11:38 +02:00
|
|
|
|
2019-02-07 23:26:38 +01:00
|
|
|
|
2011-09-15 11:53:01 +03:00
|
|
|
|
2019-02-07 23:26:38 +01:00
|
|
|
|
2011-09-15 11:53:01 +03:00
|
|
|
|
2013-02-01 19:20:03 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-11-04 17:12:07 +01:00
|
|
|
|
2013-01-30 00:26:45 +01:00
|
|
|
|
2013-02-01 19:20:03 +01:00
|
|
|
|
2011-11-04 17:12:07 +01:00
|
|
|
|
2012-11-29 01:25:20 +01:00
|
|
|
|
2013-01-30 00:40:20 +01:00
|
|
|
|
|
|
|
|
|
2013-01-30 00:26:45 +01:00
|
|
|
|
2011-11-04 17:12:07 +01:00
|
|
|
|
2013-01-30 00:40:20 +01:00
|
|
|
|
2022-11-11 11:33:04 +09:00
|
|
|
|
|
|
|
|
|
2011-11-04 17:12:07 +01:00
|
|
|
|
2012-11-29 01:25:20 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-01-30 00:40:20 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-11-29 01:25:20 +01:00
|
|
|
|
|
|
|
|
|
2011-11-04 17:12:07 +01:00
|
|
|
|
2013-01-30 00:26:45 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-11-28 22:42:34 +01:00
|
|
|
|
2013-01-30 00:26:45 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-11-28 22:42:34 +01:00
|
|
|
|
2011-11-04 17:12:07 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-02-01 19:20:03 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-01-30 00:26:45 +01:00
|
|
|
|
2013-02-01 19:20:03 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-11-04 17:12:07 +01:00
|
|
|
|
|
|
|
|
|
2015-02-08 15:52:03 +02:00
|
|
|
|
2016-04-12 15:56:15 +02:00
|
|
|
|
2015-02-08 15:52:03 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-04-12 15:56:15 +02:00
|
|
|
|
2015-02-08 15:52:03 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-06-19 14:06:27 -07:00
|
|
|
|
2023-12-11 09:05:20 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
wifi: cfg80211: say why the auth/assoc BSS lookup failed
The BSS lookup for an authentication or association request can fail
for three distinct reasons: cfg80211 has no scan entry at all for the
BSSID/channel, an entry exists but is older than
IEEE80211_SCAN_RESULT_EXPIRE (and not held), or a fresh entry exists
but its use_for flags do not allow this use. All three currently
surface as the same generic extack message "Error fetching BSS for
link" on the MLO association path, and as a bare -ENOENT with no
message at all on the authentication and non-MLO association paths.
Since wpa_supplicant logs the extack message verbatim ("nl80211:
kernel reports: ..."), that message is often the only diagnostic a
user sees when an MLO association degrades to fewer links, and it
does not say whether a fresh scan could have helped. In practice the
expired case is common for MLO partner links: 6 GHz is passive-scan
in many regulatory domains, so the partner-link entry is routinely
stale by the time userspace requests the association even though the
link is perfectly usable.
Let __cfg80211_get_bss() take an optional extack and record, during
the same bss_lock walk that fails the lookup, whether any matching
entry was rejected for being expired or for not being usable for the
requested use, and set a distinct message for each case (and a
combined one when different entries were rejected for different
reasons). Reorder the checks in the walk so that an entry's identity
(type, privacy, channel, BSSID/SSID) is established before the
usability checks; this doesn't change which entry is returned since
an entry is only used when all checks pass.
Also give the -EINVAL paths in nl80211_assoc_bss() proper messages
while at it, and keep pointing the bad_attr at the failing link on
the MLO path there; the message for that case is already set by the
lookup itself.
Signed-off-by: Louis Kotze <loukot@gmail.com>
Link: https://patch.msgid.link/20260722070734.3612581-2-loukot@gmail.com
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2026-07-22 09:07:33 +02:00
|
|
|
|
|
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
2014-04-21 12:53:03 +08:00
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
wifi: cfg80211: say why the auth/assoc BSS lookup failed
The BSS lookup for an authentication or association request can fail
for three distinct reasons: cfg80211 has no scan entry at all for the
BSSID/channel, an entry exists but is older than
IEEE80211_SCAN_RESULT_EXPIRE (and not held), or a fresh entry exists
but its use_for flags do not allow this use. All three currently
surface as the same generic extack message "Error fetching BSS for
link" on the MLO association path, and as a bare -ENOENT with no
message at all on the authentication and non-MLO association paths.
Since wpa_supplicant logs the extack message verbatim ("nl80211:
kernel reports: ..."), that message is often the only diagnostic a
user sees when an MLO association degrades to fewer links, and it
does not say whether a fresh scan could have helped. In practice the
expired case is common for MLO partner links: 6 GHz is passive-scan
in many regulatory domains, so the partner-link entry is routinely
stale by the time userspace requests the association even though the
link is perfectly usable.
Let __cfg80211_get_bss() take an optional extack and record, during
the same bss_lock walk that fails the lookup, whether any matching
entry was rejected for being expired or for not being usable for the
requested use, and set a distinct message for each case (and a
combined one when different entries were rejected for different
reasons). Reorder the checks in the walk so that an entry's identity
(type, privacy, channel, BSSID/SSID) is established before the
usability checks; this doesn't change which entry is returned since
an entry is only used when all checks pass.
Also give the -EINVAL paths in nl80211_assoc_bss() proper messages
while at it, and keep pointing the bad_attr at the failing link on
the MLO path there; the message for that case is already set by the
lookup itself.
Signed-off-by: Louis Kotze <loukot@gmail.com>
Link: https://patch.msgid.link/20260722070734.3612581-2-loukot@gmail.com
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2026-07-22 09:07:33 +02:00
|
|
|
|
2010-07-13 10:55:38 +02:00
|
|
|
|
2015-02-08 15:52:03 +02:00
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
2015-02-08 15:52:03 +02:00
|
|
|
|
|
|
|
|
|
2012-08-27 12:49:39 +03:00
|
|
|
|
2014-04-21 12:53:02 +08:00
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
2014-04-21 12:53:02 +08:00
|
|
|
|
2015-02-08 15:52:03 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-02-10 21:25:59 +01:00
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
|
|
|
|
|
2014-04-09 22:36:50 +02:00
|
|
|
|
|
|
|
|
|
wifi: cfg80211: say why the auth/assoc BSS lookup failed
The BSS lookup for an authentication or association request can fail
for three distinct reasons: cfg80211 has no scan entry at all for the
BSSID/channel, an entry exists but is older than
IEEE80211_SCAN_RESULT_EXPIRE (and not held), or a fresh entry exists
but its use_for flags do not allow this use. All three currently
surface as the same generic extack message "Error fetching BSS for
link" on the MLO association path, and as a bare -ENOENT with no
message at all on the authentication and non-MLO association paths.
Since wpa_supplicant logs the extack message verbatim ("nl80211:
kernel reports: ..."), that message is often the only diagnostic a
user sees when an MLO association degrades to fewer links, and it
does not say whether a fresh scan could have helped. In practice the
expired case is common for MLO partner links: 6 GHz is passive-scan
in many regulatory domains, so the partner-link entry is routinely
stale by the time userspace requests the association even though the
link is perfectly usable.
Let __cfg80211_get_bss() take an optional extack and record, during
the same bss_lock walk that fails the lookup, whether any matching
entry was rejected for being expired or for not being usable for the
requested use, and set a distinct message for each case (and a
combined one when different entries were rejected for different
reasons). Reorder the checks in the walk so that an entry's identity
(type, privacy, channel, BSSID/SSID) is established before the
usability checks; this doesn't change which entry is returned since
an entry is only used when all checks pass.
Also give the -EINVAL paths in nl80211_assoc_bss() proper messages
while at it, and keep pointing the bad_attr at the failing link on
the MLO path there; the message for that case is already set by the
lookup itself.
Signed-off-by: Louis Kotze <loukot@gmail.com>
Link: https://patch.msgid.link/20260722070734.3612581-2-loukot@gmail.com
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2026-07-22 09:07:33 +02:00
|
|
|
|
2023-12-11 09:05:20 +02:00
|
|
|
|
wifi: cfg80211: say why the auth/assoc BSS lookup failed
The BSS lookup for an authentication or association request can fail
for three distinct reasons: cfg80211 has no scan entry at all for the
BSSID/channel, an entry exists but is older than
IEEE80211_SCAN_RESULT_EXPIRE (and not held), or a fresh entry exists
but its use_for flags do not allow this use. All three currently
surface as the same generic extack message "Error fetching BSS for
link" on the MLO association path, and as a bare -ENOENT with no
message at all on the authentication and non-MLO association paths.
Since wpa_supplicant logs the extack message verbatim ("nl80211:
kernel reports: ..."), that message is often the only diagnostic a
user sees when an MLO association degrades to fewer links, and it
does not say whether a fresh scan could have helped. In practice the
expired case is common for MLO partner links: 6 GHz is passive-scan
in many regulatory domains, so the partner-link entry is routinely
stale by the time userspace requests the association even though the
link is perfectly usable.
Let __cfg80211_get_bss() take an optional extack and record, during
the same bss_lock walk that fails the lookup, whether any matching
entry was rejected for being expired or for not being usable for the
requested use, and set a distinct message for each case (and a
combined one when different entries were rejected for different
reasons). Reorder the checks in the walk so that an entry's identity
(type, privacy, channel, BSSID/SSID) is established before the
usability checks; this doesn't change which entry is returned since
an entry is only used when all checks pass.
Also give the -EINVAL paths in nl80211_assoc_bss() proper messages
while at it, and keep pointing the bad_attr at the failing link on
the MLO path there; the message for that case is already set by the
lookup itself.
Signed-off-by: Louis Kotze <loukot@gmail.com>
Link: https://patch.msgid.link/20260722070734.3612581-2-loukot@gmail.com
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2026-07-22 09:07:33 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-07-13 10:55:38 +02:00
|
|
|
|
|
|
|
|
|
wifi: cfg80211: say why the auth/assoc BSS lookup failed
The BSS lookup for an authentication or association request can fail
for three distinct reasons: cfg80211 has no scan entry at all for the
BSSID/channel, an entry exists but is older than
IEEE80211_SCAN_RESULT_EXPIRE (and not held), or a fresh entry exists
but its use_for flags do not allow this use. All three currently
surface as the same generic extack message "Error fetching BSS for
link" on the MLO association path, and as a bare -ENOENT with no
message at all on the authentication and non-MLO association paths.
Since wpa_supplicant logs the extack message verbatim ("nl80211:
kernel reports: ..."), that message is often the only diagnostic a
user sees when an MLO association degrades to fewer links, and it
does not say whether a fresh scan could have helped. In practice the
expired case is common for MLO partner links: 6 GHz is passive-scan
in many regulatory domains, so the partner-link entry is routinely
stale by the time userspace requests the association even though the
link is perfectly usable.
Let __cfg80211_get_bss() take an optional extack and record, during
the same bss_lock walk that fails the lookup, whether any matching
entry was rejected for being expired or for not being usable for the
requested use, and set a distinct message for each case (and a
combined one when different entries were rejected for different
reasons). Reorder the checks in the walk so that an entry's identity
(type, privacy, channel, BSSID/SSID) is established before the
usability checks; this doesn't change which entry is returned since
an entry is only used when all checks pass.
Also give the -EINVAL paths in nl80211_assoc_bss() proper messages
while at it, and keep pointing the bad_attr at the failing link on
the MLO path there; the message for that case is already set by the
lookup itself.
Signed-off-by: Louis Kotze <loukot@gmail.com>
Link: https://patch.msgid.link/20260722070734.3612581-2-loukot@gmail.com
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2026-07-22 09:07:33 +02:00
|
|
|
|
|
|
|
|
|
2010-07-13 10:55:38 +02:00
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
wifi: cfg80211: say why the auth/assoc BSS lookup failed
The BSS lookup for an authentication or association request can fail
for three distinct reasons: cfg80211 has no scan entry at all for the
BSSID/channel, an entry exists but is older than
IEEE80211_SCAN_RESULT_EXPIRE (and not held), or a fresh entry exists
but its use_for flags do not allow this use. All three currently
surface as the same generic extack message "Error fetching BSS for
link" on the MLO association path, and as a bare -ENOENT with no
message at all on the authentication and non-MLO association paths.
Since wpa_supplicant logs the extack message verbatim ("nl80211:
kernel reports: ..."), that message is often the only diagnostic a
user sees when an MLO association degrades to fewer links, and it
does not say whether a fresh scan could have helped. In practice the
expired case is common for MLO partner links: 6 GHz is passive-scan
in many regulatory domains, so the partner-link entry is routinely
stale by the time userspace requests the association even though the
link is perfectly usable.
Let __cfg80211_get_bss() take an optional extack and record, during
the same bss_lock walk that fails the lookup, whether any matching
entry was rejected for being expired or for not being usable for the
requested use, and set a distinct message for each case (and a
combined one when different entries were rejected for different
reasons). Reorder the checks in the walk so that an entry's identity
(type, privacy, channel, BSSID/SSID) is established before the
usability checks; this doesn't change which entry is returned since
an entry is only used when all checks pass.
Also give the -EINVAL paths in nl80211_assoc_bss() proper messages
while at it, and keep pointing the bad_attr at the failing link on
the MLO path there; the message for that case is already set by the
lookup itself.
Signed-off-by: Louis Kotze <loukot@gmail.com>
Link: https://patch.msgid.link/20260722070734.3612581-2-loukot@gmail.com
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2026-07-22 09:07:33 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
|
|
|
|
|
2014-04-21 12:53:02 +08:00
|
|
|
|
wifi: cfg80211: say why the auth/assoc BSS lookup failed
The BSS lookup for an authentication or association request can fail
for three distinct reasons: cfg80211 has no scan entry at all for the
BSSID/channel, an entry exists but is older than
IEEE80211_SCAN_RESULT_EXPIRE (and not held), or a fresh entry exists
but its use_for flags do not allow this use. All three currently
surface as the same generic extack message "Error fetching BSS for
link" on the MLO association path, and as a bare -ENOENT with no
message at all on the authentication and non-MLO association paths.
Since wpa_supplicant logs the extack message verbatim ("nl80211:
kernel reports: ..."), that message is often the only diagnostic a
user sees when an MLO association degrades to fewer links, and it
does not say whether a fresh scan could have helped. In practice the
expired case is common for MLO partner links: 6 GHz is passive-scan
in many regulatory domains, so the partner-link entry is routinely
stale by the time userspace requests the association even though the
link is perfectly usable.
Let __cfg80211_get_bss() take an optional extack and record, during
the same bss_lock walk that fails the lookup, whether any matching
entry was rejected for being expired or for not being usable for the
requested use, and set a distinct message for each case (and a
combined one when different entries were rejected for different
reasons). Reorder the checks in the walk so that an entry's identity
(type, privacy, channel, BSSID/SSID) is established before the
usability checks; this doesn't change which entry is returned since
an entry is only used when all checks pass.
Also give the -EINVAL paths in nl80211_assoc_bss() proper messages
while at it, and keep pointing the bad_attr at the failing link on
the MLO path there; the message for that case is already set by the
lookup itself.
Signed-off-by: Louis Kotze <loukot@gmail.com>
Link: https://patch.msgid.link/20260722070734.3612581-2-loukot@gmail.com
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2026-07-22 09:07:33 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
wifi: cfg80211: say why the auth/assoc BSS lookup failed
The BSS lookup for an authentication or association request can fail
for three distinct reasons: cfg80211 has no scan entry at all for the
BSSID/channel, an entry exists but is older than
IEEE80211_SCAN_RESULT_EXPIRE (and not held), or a fresh entry exists
but its use_for flags do not allow this use. All three currently
surface as the same generic extack message "Error fetching BSS for
link" on the MLO association path, and as a bare -ENOENT with no
message at all on the authentication and non-MLO association paths.
Since wpa_supplicant logs the extack message verbatim ("nl80211:
kernel reports: ..."), that message is often the only diagnostic a
user sees when an MLO association degrades to fewer links, and it
does not say whether a fresh scan could have helped. In practice the
expired case is common for MLO partner links: 6 GHz is passive-scan
in many regulatory domains, so the partner-link entry is routinely
stale by the time userspace requests the association even though the
link is perfectly usable.
Let __cfg80211_get_bss() take an optional extack and record, during
the same bss_lock walk that fails the lookup, whether any matching
entry was rejected for being expired or for not being usable for the
requested use, and set a distinct message for each case (and a
combined one when different entries were rejected for different
reasons). Reorder the checks in the walk so that an entry's identity
(type, privacy, channel, BSSID/SSID) is established before the
usability checks; this doesn't change which entry is returned since
an entry is only used when all checks pass.
Also give the -EINVAL paths in nl80211_assoc_bss() proper messages
while at it, and keep pointing the bad_attr at the failing link on
the MLO path there; the message for that case is already set by the
lookup itself.
Signed-off-by: Louis Kotze <loukot@gmail.com>
Link: https://patch.msgid.link/20260722070734.3612581-2-loukot@gmail.com
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2026-07-22 09:07:33 +02:00
|
|
|
|
2012-08-27 12:49:39 +03:00
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
|
|
|
|
|
2023-12-11 09:05:20 +02:00
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
2024-06-07 20:17:17 +02:00
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
|
|
|
|
|
2014-04-21 12:53:02 +08:00
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-02-01 19:20:03 +01:00
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-06-07 20:17:17 +02:00
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-04-21 12:53:02 +08:00
|
|
|
|
2024-06-07 20:17:17 +02:00
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-04-21 12:53:02 +08:00
|
|
|
|
2013-01-30 00:26:45 +01:00
|
|
|
|
2013-02-01 19:20:03 +01:00
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
2014-04-21 12:53:02 +08:00
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-02-01 19:20:03 +01:00
|
|
|
|
2011-11-04 17:12:07 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-06-07 20:17:17 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-04-21 12:53:02 +08:00
|
|
|
|
2013-02-01 02:06:18 +01:00
|
|
|
|
2011-11-04 17:12:07 +01:00
|
|
|
|
2012-11-29 01:25:20 +01:00
|
|
|
|
2013-02-01 02:06:18 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-11-15 12:05:11 +01:00
|
|
|
|
2012-11-29 01:25:20 +01:00
|
|
|
|
2013-02-01 02:06:18 +01:00
|
|
|
|
2012-11-29 01:25:20 +01:00
|
|
|
|
2013-02-01 02:06:18 +01:00
|
|
|
|
2011-11-04 17:12:07 +01:00
|
|
|
|
2013-02-01 02:06:18 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-04-21 12:53:02 +08:00
|
|
|
|
2016-11-15 12:05:11 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-02-01 02:06:18 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-11-15 12:05:11 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-02-01 02:06:18 +01:00
|
|
|
|
2011-11-04 17:12:07 +01:00
|
|
|
|
|
|
|
|
|
2022-10-05 23:11:43 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-09-07 11:51:43 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-10-05 23:11:43 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-01-29 13:14:13 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-07-26 16:39:32 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-09-07 11:51:43 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-07-26 16:39:32 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-01-29 13:14:13 +01:00
|
|
|
|
|
|
|
|
|
2019-07-26 16:39:32 +00:00
|
|
|
|
2024-01-29 13:14:13 +01:00
|
|
|
|
2023-12-11 09:05:28 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-07-26 16:39:32 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-08-13 16:52:36 +03:00
|
|
|
|
|
|
|
|
|
2019-07-26 16:39:32 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-09-14 23:28:25 +08:00
|
|
|
|
|
|
|
|
|
2019-07-26 16:39:32 +00:00
|
|
|
|
2026-09-14 23:28:25 +08:00
|
|
|
|
2019-07-26 16:39:32 +00:00
|
|
|
|
2026-09-14 23:28:25 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-07-26 16:39:32 +00:00
|
|
|
|
2026-09-14 23:28:25 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-07-26 16:39:32 +00:00
|
|
|
|
2026-09-14 23:28:25 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-07-26 16:39:32 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-12-09 08:27:33 +05:30
|
|
|
|
2023-12-11 09:05:20 +02:00
|
|
|
|
2024-09-04 08:39:16 +05:30
|
|
|
|
2019-07-26 16:39:32 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-06-19 14:06:27 -07:00
|
|
|
|
2023-06-16 09:53:59 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
|
|
|
|
|
2023-12-20 13:41:42 +02:00
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
2012-11-29 01:25:20 +01:00
|
|
|
|
2023-12-20 13:41:42 +02:00
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
2019-05-01 18:25:24 +05:30
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
2023-12-20 13:41:42 +02:00
|
|
|
|
|
|
|
|
|
2012-11-29 01:25:20 +01:00
|
|
|
|
2014-04-21 12:53:02 +08:00
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
2009-04-16 15:00:58 +02:00
|
|
|
|
2019-07-26 16:39:32 +00:00
|
|
|
|
2023-06-16 09:53:59 +03:00
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
2012-11-29 01:25:20 +01:00
|
|
|
|
2011-11-04 17:12:07 +01:00
|
|
|
|
|
|
|
|
|
2012-11-29 01:25:20 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-04-21 12:53:02 +08:00
|
|
|
|
2012-11-29 01:25:20 +01:00
|
|
|
|
2023-12-20 13:41:42 +02:00
|
|
|
|
|
|
|
|
|
2012-11-29 01:25:20 +01:00
|
|
|
|
2013-02-01 02:06:18 +01:00
|
|
|
|
|
|
|
|
|
2019-01-21 12:25:59 +02:00
|
|
|
|
2022-09-30 23:44:23 +02:00
|
|
|
|
|
|
|
|
|
2013-02-01 02:06:18 +01:00
|
|
|
|
|
|
|
|
|
2014-04-21 12:53:02 +08:00
|
|
|
|
2013-02-01 02:06:18 +01:00
|
|
|
|
2014-04-21 12:53:02 +08:00
|
|
|
|
2013-02-01 02:06:18 +01:00
|
|
|
|
2026-09-04 16:55:04 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-02-01 02:06:18 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-12-20 13:41:41 +02:00
|
|
|
|
2024-01-03 20:13:51 +08:00
|
|
|
|
2013-02-01 02:06:18 +01:00
|
|
|
|
|
|
|
|
|
2023-12-20 13:41:41 +02:00
|
|
|
|
|
|
|
|
|
2013-02-01 02:06:18 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-04-21 12:53:02 +08:00
|
|
|
|
2021-06-28 21:23:34 +08:00
|
|
|
|
2023-06-16 09:53:59 +03:00
|
|
|
|
2013-02-01 02:06:18 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-11-15 12:05:11 +01:00
|
|
|
|
|
|
|
|
|
2021-06-28 21:23:34 +08:00
|
|
|
|
2023-06-16 09:53:59 +03:00
|
|
|
|
2016-11-15 12:05:11 +01:00
|
|
|
|
|
|
|
|
|
2019-01-21 12:22:21 +02:00
|
|
|
|
2019-01-22 09:50:50 +02:00
|
|
|
|
|
|
|
|
|
2022-10-17 09:03:48 +02:00
|
|
|
|
2019-01-21 12:22:21 +02:00
|
|
|
|
|
|
|
|
|
2024-06-07 20:17:17 +02:00
|
|
|
|
2012-11-29 01:25:20 +01:00
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
|
|
|
|
|
2014-04-21 12:53:02 +08:00
|
|
|
|
|
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
|
|
|
|
|
2023-12-20 13:41:42 +02:00
|
|
|
|
|
|
|
|
|
2024-09-04 19:50:21 +05:30
|
|
|
|
2023-12-20 13:41:42 +02:00
|
|
|
|
|
|
|
|
|
2024-09-04 19:50:21 +05:30
|
|
|
|
2023-12-20 13:41:42 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-16 09:53:59 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-04-21 12:53:02 +08:00
|
|
|
|
2023-06-16 09:53:59 +03:00
|
|
|
|
|
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
|
|
|
|
|
2021-09-30 04:15:33 -04:00
|
|
|
|
2023-03-01 12:09:20 +02:00
|
|
|
|
2012-11-23 14:23:30 +01:00
|
|
|
|
2021-12-02 13:09:14 +01:00
|
|
|
|
2012-11-23 14:23:30 +01:00
|
|
|
|
2021-12-02 14:36:10 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-12-02 13:09:14 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-12-02 14:36:10 +02:00
|
|
|
|
|
|
|
|
|
2021-12-02 13:09:14 +01:00
|
|
|
|
2021-12-02 14:36:10 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-12-02 13:09:14 +01:00
|
|
|
|
2021-12-02 14:36:10 +02:00
|
|
|
|
2023-03-01 12:09:18 +02:00
|
|
|
|
2021-12-02 14:36:10 +02:00
|
|
|
|
|
|
|
|
|
2021-12-02 13:09:14 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-11-23 14:23:30 +01:00
|
|
|
|
2022-04-20 04:13:20 +00:00
|
|
|
|
2020-09-21 19:28:07 -07:00
|
|
|
|
|
|
|
|
|
2021-12-02 13:09:14 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-09-21 19:28:07 -07:00
|
|
|
|
2021-12-02 13:09:14 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-11-23 14:23:30 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-12-02 13:09:14 +01:00
|
|
|
|
2021-09-30 04:15:33 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-12-02 14:36:10 +02:00
|
|
|
|
2021-09-30 04:15:33 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-08-29 12:17:43 +02:00
|
|
|
|
2021-09-30 04:15:33 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-12-02 14:36:10 +02:00
|
|
|
|
2023-03-01 12:09:20 +02:00
|
|
|
|
2021-09-30 04:15:33 -04:00
|
|
|
|
2018-09-05 18:52:22 +03:00
|
|
|
|
|
|
|
|
|
2012-11-23 14:23:30 +01:00
|
|
|
|
2018-09-05 18:52:22 +03:00
|
|
|
|
2012-11-23 14:23:30 +01:00
|
|
|
|
2020-04-01 18:18:03 -07:00
|
|
|
|
2021-12-02 14:36:10 +02:00
|
|
|
|
|
|
|
|
|
2023-03-01 12:09:19 +02:00
|
|
|
|
|
|
|
|
|
2021-12-02 14:36:10 +02:00
|
|
|
|
2023-03-01 12:09:19 +02:00
|
|
|
|
2021-12-02 14:36:10 +02:00
|
|
|
|
|
|
|
|
|
2020-04-01 18:18:03 -07:00
|
|
|
|
2018-09-05 18:52:22 +03:00
|
|
|
|
2023-03-01 12:09:19 +02:00
|
|
|
|
|
|
|
|
|
2018-09-05 18:52:22 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-03-01 12:09:19 +02:00
|
|
|
|
2018-09-05 18:52:22 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-11-23 14:23:30 +01:00
|
|
|
|
2018-09-05 18:52:22 +03:00
|
|
|
|
2012-11-23 14:23:30 +01:00
|
|
|
|
|
|
|
|
|
2023-06-18 21:49:50 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-18 21:49:53 +03:00
|
|
|
|
2023-06-18 21:49:50 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-09-04 08:39:15 +05:30
|
|
|
|
2023-06-18 21:49:53 +03:00
|
|
|
|
2023-06-18 21:49:50 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-12-11 09:05:20 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-18 21:49:50 +03:00
|
|
|
|
|
|
|
|
|
2024-05-23 12:09:47 +02:00
|
|
|
|
2025-11-10 14:10:30 +02:00
|
|
|
|
|
|
|
|
|
2024-05-23 12:09:47 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-11-10 14:10:30 +02:00
|
|
|
|
2024-05-23 12:09:47 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-02-16 13:54:28 +02:00
|
|
|
|
|
|
|
|
|
2025-11-10 14:10:30 +02:00
|
|
|
|
2024-05-23 12:09:47 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-02-16 13:54:28 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-06-19 14:06:27 -07:00
|
|
|
|
2019-01-21 12:14:57 +02:00
|
|
|
|
|
|
|
|
|
2023-06-18 21:49:50 +03:00
|
|
|
|
2019-01-21 12:14:57 +02:00
|
|
|
|
2009-03-26 23:40:09 +02:00
|
|
|
|
2019-01-21 12:14:57 +02:00
|
|
|
|
2023-06-18 21:49:50 +03:00
|
|
|
|
2012-11-29 01:25:20 +01:00
|
|
|
|
2014-03-04 16:50:13 +02:00
|
|
|
|
2019-01-21 12:25:59 +02:00
|
|
|
|
2015-02-08 15:52:03 +02:00
|
|
|
|
2014-05-18 10:15:24 +03:00
|
|
|
|
2019-07-03 15:38:23 +02:00
|
|
|
|
2009-03-26 23:40:09 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-05-13 10:34:08 +05:30
|
|
|
|
2023-06-18 21:49:50 +03:00
|
|
|
|
2009-03-26 23:40:09 +02:00
|
|
|
|
|
|
|
|
|
2023-06-18 21:49:53 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-08-29 12:17:43 +02:00
|
|
|
|
2012-11-23 14:23:30 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-02-16 13:54:28 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-18 21:49:50 +03:00
|
|
|
|
2012-11-29 01:25:20 +01:00
|
|
|
|
2023-06-18 21:49:53 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-18 21:49:50 +03:00
|
|
|
|
|
|
|
|
|
2025-02-12 08:22:58 +02:00
|
|
|
|
2023-06-18 21:49:50 +03:00
|
|
|
|
|
|
|
|
|
2024-02-16 13:54:28 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-12-11 09:05:20 +02:00
|
|
|
|
|
|
|
|
|
2024-09-04 08:39:16 +05:30
|
|
|
|
2020-11-29 17:30:49 +02:00
|
|
|
|
2024-03-18 18:53:29 +02:00
|
|
|
|
|
|
|
|
|
2023-06-18 21:49:50 +03:00
|
|
|
|
2024-03-18 18:53:29 +02:00
|
|
|
|
|
|
|
|
|
2023-06-18 21:49:50 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-03-18 18:53:29 +02:00
|
|
|
|
|
|
|
|
|
2019-07-03 15:38:23 +02:00
|
|
|
|
2023-06-16 09:53:58 +03:00
|
|
|
|
|
|
|
|
|
2023-06-18 21:49:50 +03:00
|
|
|
|
|
|
|
|
|
2023-06-16 09:53:58 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-18 21:49:50 +03:00
|
|
|
|
2023-06-16 09:53:58 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-03-18 18:53:29 +02:00
|
|
|
|
2019-01-22 09:50:50 +02:00
|
|
|
|
2015-10-07 11:32:53 +02:00
|
|
|
|
2010-01-06 16:19:24 +02:00
|
|
|
|
2014-08-12 21:01:28 +02:00
|
|
|
|
2010-01-06 16:19:24 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-01-30 21:33:19 +01:00
|
|
|
|
2012-11-29 01:25:20 +01:00
|
|
|
|
2010-01-06 16:19:24 +02:00
|
|
|
|
2023-06-18 21:49:50 +03:00
|
|
|
|
2012-11-29 01:25:20 +01:00
|
|
|
|
|
|
|
|
|
2023-06-18 21:49:50 +03:00
|
|
|
|
|
|
|
|
|
2014-08-12 20:34:30 +02:00
|
|
|
|
2023-06-18 21:49:50 +03:00
|
|
|
|
2009-03-26 23:40:09 +02:00
|
|
|
|
2023-06-18 21:49:50 +03:00
|
|
|
|
2014-08-12 21:01:28 +02:00
|
|
|
|
2024-02-16 13:54:29 +02:00
|
|
|
|
2014-08-12 21:01:28 +02:00
|
|
|
|
2020-08-22 04:23:23 -04:00
|
|
|
|
2014-08-12 21:01:28 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-11-29 01:25:20 +01:00
|
|
|
|
2009-03-26 23:40:09 +02:00
|
|
|
|
2023-06-18 21:49:50 +03:00
|
|
|
|
2023-06-16 09:53:59 +03:00
|
|
|
|
|
|
|
|
|
2009-03-26 23:40:09 +02:00
|
|
|
|
2023-06-16 09:53:59 +03:00
|
|
|
|
2009-03-26 23:40:09 +02:00
|
|
|
|
2023-10-21 08:48:27 -07:00
|
|
|
|
2023-06-16 09:54:00 +03:00
|
|
|
|
2023-06-18 21:49:53 +03:00
|
|
|
|
2019-01-21 12:14:57 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-18 21:49:50 +03:00
|
|
|
|
2022-09-30 23:44:23 +02:00
|
|
|
|
2019-01-21 12:14:57 +02:00
|
|
|
|
2022-09-30 23:44:23 +02:00
|
|
|
|
|
|
|
|
|
2019-01-21 12:14:57 +02:00
|
|
|
|
2022-09-30 23:44:23 +02:00
|
|
|
|
|
|
|
|
|
2023-06-16 09:53:59 +03:00
|
|
|
|
2019-01-21 12:14:57 +02:00
|
|
|
|
2023-06-16 09:53:59 +03:00
|
|
|
|
2019-01-21 12:14:57 +02:00
|
|
|
|
2012-08-27 12:49:39 +03:00
|
|
|
|
2023-06-16 09:53:59 +03:00
|
|
|
|
2009-03-26 23:40:09 +02:00
|
|
|
|
2023-06-16 09:53:59 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-03-26 23:40:09 +02:00
|
|
|
|
2019-01-21 12:14:57 +02:00
|
|
|
|
2026-07-15 21:11:25 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-03-15 17:39:05 +02:00
|
|
|
|
2026-07-15 21:11:25 +03:00
|
|
|
|
2019-03-15 17:39:05 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-08-22 16:19:51 -07:00
|
|
|
|
2019-03-15 17:39:05 +02:00
|
|
|
|
|
|
|
|
|
2026-07-15 21:11:25 +03:00
|
|
|
|
2019-03-15 17:39:05 +02:00
|
|
|
|
2026-07-15 21:11:25 +03:00
|
|
|
|
2019-03-15 17:39:05 +02:00
|
|
|
|
2026-07-15 21:11:25 +03:00
|
|
|
|
2019-03-15 17:39:05 +02:00
|
|
|
|
|
|
|
|
|
2026-07-15 21:11:25 +03:00
|
|
|
|
2019-03-15 17:39:05 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-07-15 21:11:25 +03:00
|
|
|
|
2019-03-15 17:39:05 +02:00
|
|
|
|
|
|
|
|
|
2026-07-15 21:11:25 +03:00
|
|
|
|
2019-03-15 17:39:05 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-07-15 21:11:25 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-03-15 17:39:05 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-04-11 11:59:50 +03:00
|
|
|
|
2019-03-15 17:39:05 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-04-11 11:59:50 +03:00
|
|
|
|
2019-03-15 17:39:05 +02:00
|
|
|
|
2026-07-15 21:11:25 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-03-15 17:39:05 +02:00
|
|
|
|
2026-07-15 21:11:25 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-03-15 17:39:05 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-18 21:49:50 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-01-21 12:14:57 +02:00
|
|
|
|
2023-06-18 21:49:50 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-18 21:49:53 +03:00
|
|
|
|
2023-12-11 09:05:20 +02:00
|
|
|
|
|
|
|
|
|
2023-06-18 21:49:50 +03:00
|
|
|
|
2019-02-07 22:36:33 +01:00
|
|
|
|
|
|
|
|
|
2019-03-15 17:39:05 +02:00
|
|
|
|
|
|
|
|
|
2019-01-21 12:14:57 +02:00
|
|
|
|
|
|
|
|
|
2023-06-18 21:49:50 +03:00
|
|
|
|
2019-01-21 12:14:57 +02:00
|
|
|
|
2023-06-18 21:49:50 +03:00
|
|
|
|
|
|
|
|
|
2019-01-21 12:14:57 +02:00
|
|
|
|
2019-01-16 23:02:03 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-18 21:49:50 +03:00
|
|
|
|
|
|
|
|
|
2019-01-16 23:02:03 +02:00
|
|
|
|
2019-01-21 12:14:57 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-18 21:49:50 +03:00
|
|
|
|
2019-03-15 17:39:05 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-18 21:49:50 +03:00
|
|
|
|
|
|
|
|
|
2019-02-07 22:36:33 +01:00
|
|
|
|
|
|
|
|
|
2022-09-28 22:01:37 +02:00
|
|
|
|
|
|
|
|
|
2019-02-07 22:36:33 +01:00
|
|
|
|
2019-03-15 17:39:05 +02:00
|
|
|
|
|
|
|
|
|
2019-02-07 22:36:33 +01:00
|
|
|
|
2019-01-21 12:14:57 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-02-07 22:36:33 +01:00
|
|
|
|
|
|
|
|
|
2019-01-21 12:14:57 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-18 21:49:50 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-03-15 17:39:05 +02:00
|
|
|
|
|
|
|
|
|
2019-04-11 11:59:50 +03:00
|
|
|
|
2023-06-18 21:49:50 +03:00
|
|
|
|
2019-03-15 17:39:05 +02:00
|
|
|
|
2019-01-21 12:14:57 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-03-15 17:39:05 +02:00
|
|
|
|
2019-01-21 12:14:57 +02:00
|
|
|
|
2019-03-15 17:39:05 +02:00
|
|
|
|
2024-03-18 18:53:28 +02:00
|
|
|
|
|
|
|
|
|
2019-01-21 12:14:57 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-05-29 15:25:29 +03:00
|
|
|
|
2019-03-15 17:39:05 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-05-29 15:25:29 +03:00
|
|
|
|
2019-03-15 17:39:05 +02:00
|
|
|
|
2023-06-18 21:49:50 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-01-22 09:50:50 +02:00
|
|
|
|
2019-01-21 12:14:57 +02:00
|
|
|
|
2023-06-18 21:49:50 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-03-15 17:39:05 +02:00
|
|
|
|
2023-06-18 21:49:50 +03:00
|
|
|
|
|
|
|
|
|
2023-06-16 09:54:03 +03:00
|
|
|
|
2023-06-18 21:49:50 +03:00
|
|
|
|
2019-01-21 12:14:57 +02:00
|
|
|
|
|
|
|
|
|
2023-06-18 21:49:50 +03:00
|
|
|
|
|
|
|
|
|
2019-01-21 12:14:57 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-03-15 17:39:05 +02:00
|
|
|
|
2019-01-21 12:14:57 +02:00
|
|
|
|
2019-03-15 17:39:05 +02:00
|
|
|
|
2019-01-21 12:14:57 +02:00
|
|
|
|
|
|
|
|
|
2023-06-16 09:54:05 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-05-29 10:25:00 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-16 09:54:05 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-08-27 14:05:19 +03:00
|
|
|
|
2023-06-16 09:54:05 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-02-28 09:55:42 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-16 09:54:05 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-02-28 09:55:42 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-16 09:54:05 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-08-27 14:05:19 +03:00
|
|
|
|
2023-06-16 09:54:05 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-02-28 09:55:42 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-16 09:54:05 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-18 21:49:53 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-04-24 18:01:42 +05:30
|
|
|
|
2023-06-18 21:49:53 +03: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
|
|
|
|
2023-06-18 21:49:53 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-02-16 13:54:30 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-03-18 18:53:29 +02:00
|
|
|
|
2024-02-16 13:54:30 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-03-18 18:53:29 +02:00
|
|
|
|
2024-02-16 13:54:30 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-03-18 18:53:29 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-02-16 13:54:30 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-03-18 18:53:29 +02:00
|
|
|
|
2024-02-16 13:54:30 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-12-11 09:05:20 +02:00
|
|
|
|
2024-02-16 13:54:27 +02:00
|
|
|
|
|
|
|
|
|
2024-03-18 18:53:29 +02:00
|
|
|
|
2023-06-18 21:49:53 +03:00
|
|
|
|
2024-02-16 13:54:30 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-18 21:49:53 +03:00
|
|
|
|
2024-02-16 13:54:30 +02:00
|
|
|
|
2023-06-18 21:49:53 +03:00
|
|
|
|
2024-02-16 13:54:30 +02:00
|
|
|
|
|
|
|
|
|
2024-03-18 18:53:29 +02:00
|
|
|
|
2023-06-18 21:49:53 +03:00
|
|
|
|
2024-02-16 13:54:30 +02:00
|
|
|
|
2023-06-18 21:49:53 +03:00
|
|
|
|
|
|
|
|
|
2024-01-02 21:35:32 +02: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
|
|
|
|
|
|
|
|
|
2024-01-02 21:35:32 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-01-02 21:35:31 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-18 21:49:53 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-01-02 21:35:32 +02:00
|
|
|
|
2023-06-18 21:49:53 +03:00
|
|
|
|
|
|
|
|
|
2024-09-04 08:39:17 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-18 21:49:53 +03:00
|
|
|
|
2023-12-11 09:05:27 +02:00
|
|
|
|
2024-01-02 21:35:32 +02:00
|
|
|
|
2023-06-18 21:49:53 +03:00
|
|
|
|
2024-01-02 21:35:32 +02:00
|
|
|
|
2023-06-18 21:49:53 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-02-16 13:54:32 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-18 21:49:53 +03:00
|
|
|
|
|
|
|
|
|
2024-02-16 13:54:32 +02:00
|
|
|
|
2023-06-18 21:49:53 +03:00
|
|
|
|
2024-02-16 13:54:32 +02:00
|
|
|
|
2023-06-18 21:49:53 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-02-16 13:54:32 +02:00
|
|
|
|
|
|
|
|
|
2023-06-18 21:49:53 +03:00
|
|
|
|
2024-01-02 21:35:30 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-18 21:49:53 +03:00
|
|
|
|
2024-02-16 13:54:32 +02:00
|
|
|
|
2023-06-18 21:49:53 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-01-02 21:35:32 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-18 21:49:53 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-01-02 21:35:32 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-09-04 08:39:17 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-18 21:49:53 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-02-16 13:54:27 +02:00
|
|
|
|
2023-12-11 09:05:20 +02:00
|
|
|
|
2024-03-18 18:53:29 +02:00
|
|
|
|
2023-06-18 21:49:53 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-02-16 13:54:27 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-03-18 18:53:29 +02:00
|
|
|
|
|
|
|
|
|
2023-12-11 09:05:20 +02:00
|
|
|
|
2023-06-18 21:49:53 +03:00
|
|
|
|
|
|
|
|
|
2024-03-18 18:53:29 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-18 21:49:53 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-09-23 07:46:44 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-09-04 08:39:17 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-12-11 09:05:20 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-18 21:49:53 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-12-11 09:05:27 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-02-16 13:54:27 +02:00
|
|
|
|
|
|
|
|
|
2023-12-11 09:05:27 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-02-16 13:54:27 +02:00
|
|
|
|
|
|
|
|
|
2023-12-11 09:05:27 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-01-02 21:35:32 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-12-11 09:05:27 +02:00
|
|
|
|
2023-06-18 21:49:53 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-01-02 21:35:32 +02:00
|
|
|
|
2023-06-18 21:49:53 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-01-02 21:35:31 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-01-21 12:14:57 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-18 21:49:50 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-12-11 09:05:20 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-18 21:49:50 +03:00
|
|
|
|
2019-01-21 12:14:57 +02:00
|
|
|
|
|
|
|
|
|
2023-06-18 21:49:50 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-07-03 15:38:22 +02:00
|
|
|
|
|
|
|
|
|
2023-06-18 21:49:50 +03:00
|
|
|
|
2024-02-16 13:54:29 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-18 21:49:50 +03:00
|
|
|
|
2023-06-18 21:49:53 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-01-21 12:14:57 +02:00
|
|
|
|
|
|
|
|
|
2015-10-07 11:32:53 +02:00
|
|
|
|
2009-03-26 23:40:09 +02:00
|
|
|
|
2024-02-16 13:54:28 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-12-20 13:41:38 +02:00
|
|
|
|
2024-07-24 13:29:12 +02:00
|
|
|
|
2020-09-21 19:28:06 -07:00
|
|
|
|
2024-02-16 13:54:29 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-06-03 15:35:38 +10:00
|
|
|
|
2012-08-27 12:49:39 +03:00
|
|
|
|
2011-03-26 19:26:55 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
2024-02-16 13:54:28 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
2020-09-21 19:28:06 -07:00
|
|
|
|
|
|
|
|
|
2025-06-03 15:35:38 +10:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-07-24 13:29:12 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-09-21 19:28:06 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
|
|
|
|
|
2024-02-16 13:54:29 +02:00
|
|
|
|
|
|
|
|
|
2020-09-21 19:28:06 -07:00
|
|
|
|
2021-04-08 14:28:27 +02:00
|
|
|
|
|
|
|
|
|
2020-09-21 19:28:06 -07:00
|
|
|
|
2025-06-03 15:35:38 +10:00
|
|
|
|
2024-02-16 13:54:29 +02:00
|
|
|
|
2021-04-08 14:28:27 +02:00
|
|
|
|
2020-09-21 19:28:06 -07:00
|
|
|
|
2021-04-08 14:28:27 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-02-16 13:54:29 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-06-12 00:19:46 +08:00
|
|
|
|
|
|
|
|
|
2020-09-21 19:28:06 -07:00
|
|
|
|
2024-02-16 13:54:29 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-06-12 00:19:46 +08:00
|
|
|
|
2020-09-21 19:28:06 -07:00
|
|
|
|
|
|
|
|
|
2012-11-29 01:25:20 +01:00
|
|
|
|
2024-02-16 13:54:29 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-11-29 01:25:20 +01:00
|
|
|
|
2024-02-16 13:54:29 +02:00
|
|
|
|
2016-12-16 11:21:54 +00:00
|
|
|
|
2024-02-16 13:54:29 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-01-21 12:14:57 +02:00
|
|
|
|
2015-10-07 11:32:53 +02:00
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
2013-02-01 01:49:58 +01:00
|
|
|
|
2012-01-20 13:55:26 +01:00
|
|
|
|
2014-04-21 12:53:03 +08:00
|
|
|
|
2012-01-20 13:55:26 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-04-21 12:53:02 +08:00
|
|
|
|
2022-10-17 09:03:48 +02:00
|
|
|
|
2014-04-21 12:53:02 +08:00
|
|
|
|
2012-01-20 13:55:26 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-02-01 01:49:58 +01:00
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
2014-04-21 12:53:03 +08:00
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-04-21 12:53:02 +08:00
|
|
|
|
2022-10-17 09:03:48 +02:00
|
|
|
|
2014-04-21 12:53:02 +08:00
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-02-10 21:25:58 +01:00
|
|
|
|
|
|
|
|
|
2014-04-21 12:53:03 +08:00
|
|
|
|
2019-01-21 12:25:59 +02:00
|
|
|
|
|
|
|
|
|
2009-02-10 21:25:58 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-10-17 09:03:48 +02:00
|
|
|
|
2009-02-10 21:25:58 +01:00
|
|
|
|
2014-04-21 12:53:02 +08:00
|
|
|
|
2019-01-21 12:25:59 +02:00
|
|
|
|
|
|
|
|
|
2019-01-21 12:14:57 +02:00
|
|
|
|
2019-01-21 12:25:59 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-10-17 09:03:48 +02:00
|
|
|
|
2019-01-21 12:25:59 +02:00
|
|
|
|
2014-04-21 12:53:02 +08:00
|
|
|
|
2010-10-06 21:18:04 +02:00
|
|
|
|
2019-01-21 12:25:59 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-04-21 12:53:02 +08:00
|
|
|
|
2009-02-10 21:25:58 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-05-29 15:25:32 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-04-14 16:50:57 +02:00
|
|
|
|
|
|
|
|
|
2019-05-29 15:25:32 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
cfg80211: fix duplicated scan entries after channel switch
When associated BSS completes channel switch procedure, its channel
record needs to be updated. The existing mac80211 solution was
extended to cfg80211 in commit 5dc8cdce1d72 ("mac80211/cfg80211:
update bss channel on channel switch").
However that solution still appears to be incomplete as it may lead
to duplicated scan entries for associated BSS after channel switch.
The root cause of the problem is as follows. Each BSS entry is
included into the following data structures:
- bss list rdev->bss_list
- bss search tree rdev->bss_tree
Updating BSS channel record without rebuilding bss_tree may break
tree search since cmp_bss considers all of the following: channel,
bssid, ssid. When BSS channel is updated, but its location in bss_tree
is not updated, then subsequent search operations may fail to locate
this BSS since they will be traversing bss_tree in wrong direction.
As a result, for scan performed after associated BSS channel switch,
cfg80211_bss_update may add the second entry for the same BSS to both
bss_list and bss_tree, rather then update the existing one.
To summarize, if BSS channel needs to be updated, then bss_tree should
be rebuilt in order to put updated BSS entry into a proper location.
This commit suggests the following straightforward solution:
- if new entry has been already created for BSS after channel switch,
then use its IEs to update known BSS entry and then remove new
entry completely
- use rb_erase/rb_insert_bss reinstall updated BSS in bss_tree
- for nontransmit BSS entry, the whole transmit BSS hierarchy
is updated
Signed-off-by: Sergey Matyukevich <sergey.matyukevich.os@quantenna.com>
Link: https://lore.kernel.org/r/20190726163922.27509-3-sergey.matyukevich.os@quantenna.com
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2019-07-26 16:39:34 +00:00
|
|
|
|
2022-04-14 16:50:57 +02:00
|
|
|
|
cfg80211: fix duplicated scan entries after channel switch
When associated BSS completes channel switch procedure, its channel
record needs to be updated. The existing mac80211 solution was
extended to cfg80211 in commit 5dc8cdce1d72 ("mac80211/cfg80211:
update bss channel on channel switch").
However that solution still appears to be incomplete as it may lead
to duplicated scan entries for associated BSS after channel switch.
The root cause of the problem is as follows. Each BSS entry is
included into the following data structures:
- bss list rdev->bss_list
- bss search tree rdev->bss_tree
Updating BSS channel record without rebuilding bss_tree may break
tree search since cmp_bss considers all of the following: channel,
bssid, ssid. When BSS channel is updated, but its location in bss_tree
is not updated, then subsequent search operations may fail to locate
this BSS since they will be traversing bss_tree in wrong direction.
As a result, for scan performed after associated BSS channel switch,
cfg80211_bss_update may add the second entry for the same BSS to both
bss_list and bss_tree, rather then update the existing one.
To summarize, if BSS channel needs to be updated, then bss_tree should
be rebuilt in order to put updated BSS entry into a proper location.
This commit suggests the following straightforward solution:
- if new entry has been already created for BSS after channel switch,
then use its IEs to update known BSS entry and then remove new
entry completely
- use rb_erase/rb_insert_bss reinstall updated BSS in bss_tree
- for nontransmit BSS entry, the whole transmit BSS hierarchy
is updated
Signed-off-by: Sergey Matyukevich <sergey.matyukevich.os@quantenna.com>
Link: https://lore.kernel.org/r/20190726163922.27509-3-sergey.matyukevich.os@quantenna.com
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2019-07-26 16:39:34 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-04-14 16:50:57 +02:00
|
|
|
|
cfg80211: fix duplicated scan entries after channel switch
When associated BSS completes channel switch procedure, its channel
record needs to be updated. The existing mac80211 solution was
extended to cfg80211 in commit 5dc8cdce1d72 ("mac80211/cfg80211:
update bss channel on channel switch").
However that solution still appears to be incomplete as it may lead
to duplicated scan entries for associated BSS after channel switch.
The root cause of the problem is as follows. Each BSS entry is
included into the following data structures:
- bss list rdev->bss_list
- bss search tree rdev->bss_tree
Updating BSS channel record without rebuilding bss_tree may break
tree search since cmp_bss considers all of the following: channel,
bssid, ssid. When BSS channel is updated, but its location in bss_tree
is not updated, then subsequent search operations may fail to locate
this BSS since they will be traversing bss_tree in wrong direction.
As a result, for scan performed after associated BSS channel switch,
cfg80211_bss_update may add the second entry for the same BSS to both
bss_list and bss_tree, rather then update the existing one.
To summarize, if BSS channel needs to be updated, then bss_tree should
be rebuilt in order to put updated BSS entry into a proper location.
This commit suggests the following straightforward solution:
- if new entry has been already created for BSS after channel switch,
then use its IEs to update known BSS entry and then remove new
entry completely
- use rb_erase/rb_insert_bss reinstall updated BSS in bss_tree
- for nontransmit BSS entry, the whole transmit BSS hierarchy
is updated
Signed-off-by: Sergey Matyukevich <sergey.matyukevich.os@quantenna.com>
Link: https://lore.kernel.org/r/20190726163922.27509-3-sergey.matyukevich.os@quantenna.com
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2019-07-26 16:39:34 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-03-26 15:09:43 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
cfg80211: fix duplicated scan entries after channel switch
When associated BSS completes channel switch procedure, its channel
record needs to be updated. The existing mac80211 solution was
extended to cfg80211 in commit 5dc8cdce1d72 ("mac80211/cfg80211:
update bss channel on channel switch").
However that solution still appears to be incomplete as it may lead
to duplicated scan entries for associated BSS after channel switch.
The root cause of the problem is as follows. Each BSS entry is
included into the following data structures:
- bss list rdev->bss_list
- bss search tree rdev->bss_tree
Updating BSS channel record without rebuilding bss_tree may break
tree search since cmp_bss considers all of the following: channel,
bssid, ssid. When BSS channel is updated, but its location in bss_tree
is not updated, then subsequent search operations may fail to locate
this BSS since they will be traversing bss_tree in wrong direction.
As a result, for scan performed after associated BSS channel switch,
cfg80211_bss_update may add the second entry for the same BSS to both
bss_list and bss_tree, rather then update the existing one.
To summarize, if BSS channel needs to be updated, then bss_tree should
be rebuilt in order to put updated BSS entry into a proper location.
This commit suggests the following straightforward solution:
- if new entry has been already created for BSS after channel switch,
then use its IEs to update known BSS entry and then remove new
entry completely
- use rb_erase/rb_insert_bss reinstall updated BSS in bss_tree
- for nontransmit BSS entry, the whole transmit BSS hierarchy
is updated
Signed-off-by: Sergey Matyukevich <sergey.matyukevich.os@quantenna.com>
Link: https://lore.kernel.org/r/20190726163922.27509-3-sergey.matyukevich.os@quantenna.com
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2019-07-26 16:39:34 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-10-17 09:03:48 +02:00
|
|
|
|
cfg80211: fix duplicated scan entries after channel switch
When associated BSS completes channel switch procedure, its channel
record needs to be updated. The existing mac80211 solution was
extended to cfg80211 in commit 5dc8cdce1d72 ("mac80211/cfg80211:
update bss channel on channel switch").
However that solution still appears to be incomplete as it may lead
to duplicated scan entries for associated BSS after channel switch.
The root cause of the problem is as follows. Each BSS entry is
included into the following data structures:
- bss list rdev->bss_list
- bss search tree rdev->bss_tree
Updating BSS channel record without rebuilding bss_tree may break
tree search since cmp_bss considers all of the following: channel,
bssid, ssid. When BSS channel is updated, but its location in bss_tree
is not updated, then subsequent search operations may fail to locate
this BSS since they will be traversing bss_tree in wrong direction.
As a result, for scan performed after associated BSS channel switch,
cfg80211_bss_update may add the second entry for the same BSS to both
bss_list and bss_tree, rather then update the existing one.
To summarize, if BSS channel needs to be updated, then bss_tree should
be rebuilt in order to put updated BSS entry into a proper location.
This commit suggests the following straightforward solution:
- if new entry has been already created for BSS after channel switch,
then use its IEs to update known BSS entry and then remove new
entry completely
- use rb_erase/rb_insert_bss reinstall updated BSS in bss_tree
- for nontransmit BSS entry, the whole transmit BSS hierarchy
is updated
Signed-off-by: Sergey Matyukevich <sergey.matyukevich.os@quantenna.com>
Link: https://lore.kernel.org/r/20190726163922.27509-3-sergey.matyukevich.os@quantenna.com
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2019-07-26 16:39:34 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-12-20 13:41:43 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
cfg80211: fix duplicated scan entries after channel switch
When associated BSS completes channel switch procedure, its channel
record needs to be updated. The existing mac80211 solution was
extended to cfg80211 in commit 5dc8cdce1d72 ("mac80211/cfg80211:
update bss channel on channel switch").
However that solution still appears to be incomplete as it may lead
to duplicated scan entries for associated BSS after channel switch.
The root cause of the problem is as follows. Each BSS entry is
included into the following data structures:
- bss list rdev->bss_list
- bss search tree rdev->bss_tree
Updating BSS channel record without rebuilding bss_tree may break
tree search since cmp_bss considers all of the following: channel,
bssid, ssid. When BSS channel is updated, but its location in bss_tree
is not updated, then subsequent search operations may fail to locate
this BSS since they will be traversing bss_tree in wrong direction.
As a result, for scan performed after associated BSS channel switch,
cfg80211_bss_update may add the second entry for the same BSS to both
bss_list and bss_tree, rather then update the existing one.
To summarize, if BSS channel needs to be updated, then bss_tree should
be rebuilt in order to put updated BSS entry into a proper location.
This commit suggests the following straightforward solution:
- if new entry has been already created for BSS after channel switch,
then use its IEs to update known BSS entry and then remove new
entry completely
- use rb_erase/rb_insert_bss reinstall updated BSS in bss_tree
- for nontransmit BSS entry, the whole transmit BSS hierarchy
is updated
Signed-off-by: Sergey Matyukevich <sergey.matyukevich.os@quantenna.com>
Link: https://lore.kernel.org/r/20190726163922.27509-3-sergey.matyukevich.os@quantenna.com
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2019-07-26 16:39:34 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-10-17 09:03:48 +02:00
|
|
|
|
cfg80211: fix duplicated scan entries after channel switch
When associated BSS completes channel switch procedure, its channel
record needs to be updated. The existing mac80211 solution was
extended to cfg80211 in commit 5dc8cdce1d72 ("mac80211/cfg80211:
update bss channel on channel switch").
However that solution still appears to be incomplete as it may lead
to duplicated scan entries for associated BSS after channel switch.
The root cause of the problem is as follows. Each BSS entry is
included into the following data structures:
- bss list rdev->bss_list
- bss search tree rdev->bss_tree
Updating BSS channel record without rebuilding bss_tree may break
tree search since cmp_bss considers all of the following: channel,
bssid, ssid. When BSS channel is updated, but its location in bss_tree
is not updated, then subsequent search operations may fail to locate
this BSS since they will be traversing bss_tree in wrong direction.
As a result, for scan performed after associated BSS channel switch,
cfg80211_bss_update may add the second entry for the same BSS to both
bss_list and bss_tree, rather then update the existing one.
To summarize, if BSS channel needs to be updated, then bss_tree should
be rebuilt in order to put updated BSS entry into a proper location.
This commit suggests the following straightforward solution:
- if new entry has been already created for BSS after channel switch,
then use its IEs to update known BSS entry and then remove new
entry completely
- use rb_erase/rb_insert_bss reinstall updated BSS in bss_tree
- for nontransmit BSS entry, the whole transmit BSS hierarchy
is updated
Signed-off-by: Sergey Matyukevich <sergey.matyukevich.os@quantenna.com>
Link: https://lore.kernel.org/r/20190726163922.27509-3-sergey.matyukevich.os@quantenna.com
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2019-07-26 16:39:34 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-06-07 20:17:17 +02:00
|
|
|
|
cfg80211: fix duplicated scan entries after channel switch
When associated BSS completes channel switch procedure, its channel
record needs to be updated. The existing mac80211 solution was
extended to cfg80211 in commit 5dc8cdce1d72 ("mac80211/cfg80211:
update bss channel on channel switch").
However that solution still appears to be incomplete as it may lead
to duplicated scan entries for associated BSS after channel switch.
The root cause of the problem is as follows. Each BSS entry is
included into the following data structures:
- bss list rdev->bss_list
- bss search tree rdev->bss_tree
Updating BSS channel record without rebuilding bss_tree may break
tree search since cmp_bss considers all of the following: channel,
bssid, ssid. When BSS channel is updated, but its location in bss_tree
is not updated, then subsequent search operations may fail to locate
this BSS since they will be traversing bss_tree in wrong direction.
As a result, for scan performed after associated BSS channel switch,
cfg80211_bss_update may add the second entry for the same BSS to both
bss_list and bss_tree, rather then update the existing one.
To summarize, if BSS channel needs to be updated, then bss_tree should
be rebuilt in order to put updated BSS entry into a proper location.
This commit suggests the following straightforward solution:
- if new entry has been already created for BSS after channel switch,
then use its IEs to update known BSS entry and then remove new
entry completely
- use rb_erase/rb_insert_bss reinstall updated BSS in bss_tree
- for nontransmit BSS entry, the whole transmit BSS hierarchy
is updated
Signed-off-by: Sergey Matyukevich <sergey.matyukevich.os@quantenna.com>
Link: https://lore.kernel.org/r/20190726163922.27509-3-sergey.matyukevich.os@quantenna.com
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2019-07-26 16:39:34 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-10-17 09:03:48 +02:00
|
|
|
|
cfg80211: fix duplicated scan entries after channel switch
When associated BSS completes channel switch procedure, its channel
record needs to be updated. The existing mac80211 solution was
extended to cfg80211 in commit 5dc8cdce1d72 ("mac80211/cfg80211:
update bss channel on channel switch").
However that solution still appears to be incomplete as it may lead
to duplicated scan entries for associated BSS after channel switch.
The root cause of the problem is as follows. Each BSS entry is
included into the following data structures:
- bss list rdev->bss_list
- bss search tree rdev->bss_tree
Updating BSS channel record without rebuilding bss_tree may break
tree search since cmp_bss considers all of the following: channel,
bssid, ssid. When BSS channel is updated, but its location in bss_tree
is not updated, then subsequent search operations may fail to locate
this BSS since they will be traversing bss_tree in wrong direction.
As a result, for scan performed after associated BSS channel switch,
cfg80211_bss_update may add the second entry for the same BSS to both
bss_list and bss_tree, rather then update the existing one.
To summarize, if BSS channel needs to be updated, then bss_tree should
be rebuilt in order to put updated BSS entry into a proper location.
This commit suggests the following straightforward solution:
- if new entry has been already created for BSS after channel switch,
then use its IEs to update known BSS entry and then remove new
entry completely
- use rb_erase/rb_insert_bss reinstall updated BSS in bss_tree
- for nontransmit BSS entry, the whole transmit BSS hierarchy
is updated
Signed-off-by: Sergey Matyukevich <sergey.matyukevich.os@quantenna.com>
Link: https://lore.kernel.org/r/20190726163922.27509-3-sergey.matyukevich.os@quantenna.com
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2019-07-26 16:39:34 +00:00
|
|
|
|
2024-06-07 20:17:17 +02:00
|
|
|
|
cfg80211: fix duplicated scan entries after channel switch
When associated BSS completes channel switch procedure, its channel
record needs to be updated. The existing mac80211 solution was
extended to cfg80211 in commit 5dc8cdce1d72 ("mac80211/cfg80211:
update bss channel on channel switch").
However that solution still appears to be incomplete as it may lead
to duplicated scan entries for associated BSS after channel switch.
The root cause of the problem is as follows. Each BSS entry is
included into the following data structures:
- bss list rdev->bss_list
- bss search tree rdev->bss_tree
Updating BSS channel record without rebuilding bss_tree may break
tree search since cmp_bss considers all of the following: channel,
bssid, ssid. When BSS channel is updated, but its location in bss_tree
is not updated, then subsequent search operations may fail to locate
this BSS since they will be traversing bss_tree in wrong direction.
As a result, for scan performed after associated BSS channel switch,
cfg80211_bss_update may add the second entry for the same BSS to both
bss_list and bss_tree, rather then update the existing one.
To summarize, if BSS channel needs to be updated, then bss_tree should
be rebuilt in order to put updated BSS entry into a proper location.
This commit suggests the following straightforward solution:
- if new entry has been already created for BSS after channel switch,
then use its IEs to update known BSS entry and then remove new
entry completely
- use rb_erase/rb_insert_bss reinstall updated BSS in bss_tree
- for nontransmit BSS entry, the whole transmit BSS hierarchy
is updated
Signed-off-by: Sergey Matyukevich <sergey.matyukevich.os@quantenna.com>
Link: https://lore.kernel.org/r/20190726163922.27509-3-sergey.matyukevich.os@quantenna.com
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2019-07-26 16:39:34 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-09-29 23:27:28 +02:00
|
|
|
|
2013-05-08 21:34:22 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-05-08 21:45:15 +02:00
|
|
|
|
2013-05-08 21:34:22 +02:00
|
|
|
|
|
|
|
|
|
2013-05-08 21:45:15 +02:00
|
|
|
|
|
|
|
|
|
2013-05-08 21:34:22 +02:00
|
|
|
|
|
|
|
|
|
2013-05-08 21:45:15 +02:00
|
|
|
|
|
|
|
|
|
2014-04-21 12:53:03 +08:00
|
|
|
|
2013-05-08 21:45:15 +02:00
|
|
|
|
2013-05-08 21:34:22 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-06-09 21:35:19 +03:00
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
2016-04-12 15:56:15 +02:00
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-09-09 13:09:54 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-07-14 00:33:35 +02:00
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-11-15 17:21:39 +08:00
|
|
|
|
|
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-09-09 13:09:54 +02:00
|
|
|
|
2024-05-31 06:20:10 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-09-09 13:09:54 +02:00
|
|
|
|
2024-05-31 06:20:10 +03:00
|
|
|
|
2014-01-09 11:37:23 +02:00
|
|
|
|
2024-05-31 06:20:10 +03:00
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
2025-06-09 21:35:19 +03:00
|
|
|
|
2024-09-05 18:04:00 +03:00
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
2021-11-15 17:21:39 +08:00
|
|
|
|
|
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
2025-06-09 21:35:19 +03:00
|
|
|
|
|
|
|
|
|
2009-08-07 17:54:07 +02:00
|
|
|
|
2025-06-09 21:35:19 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
2009-09-09 13:09:54 +02:00
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
2016-04-12 15:56:15 +02:00
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
2009-11-02 13:32:03 +01:00
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
|
|
|
|
|
2009-11-02 13:32:03 +01:00
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
2024-10-09 10:25:42 +02:00
|
|
|
|
|
|
|
|
|
2009-11-02 13:32:03 +01:00
|
|
|
|
2024-10-09 10:25:42 +02:00
|
|
|
|
|
|
|
|
|
2025-06-09 21:35:19 +03:00
|
|
|
|
2009-11-02 13:32:03 +01:00
|
|
|
|
2009-09-09 13:09:54 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-04-09 09:28:06 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-09-09 13:09:54 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-06-09 21:35:19 +03:00
|
|
|
|
|
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
2009-09-09 13:09:54 +02:00
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
|
|
|
|
|
2009-09-11 10:13:55 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
2025-06-09 21:35:19 +03:00
|
|
|
|
|
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
2009-09-09 13:09:54 +02:00
|
|
|
|
|
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
2026-06-20 21:48:56 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-06-09 21:35:19 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
2024-06-11 18:58:16 +02:00
|
|
|
|
2025-06-09 21:35:19 +03:00
|
|
|
|
|
|
|
|
|
2024-06-11 18:58:16 +02:00
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
|
|
|
|
|
2016-04-12 15:56:15 +02:00
|
|
|
|
2011-07-20 00:52:16 +02:00
|
|
|
|
2025-06-09 21:35:19 +03:00
|
|
|
|
|
|
|
|
|
2011-07-18 18:08:35 +02:00
|
|
|
|
2025-06-09 21:35:19 +03:00
|
|
|
|
2016-02-26 22:12:47 +02:00
|
|
|
|
2024-11-22 09:42:25 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-07-14 00:33:35 +02:00
|
|
|
|
2024-11-22 09:42:25 +01:00
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
2009-12-23 15:33:35 +01:00
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-02-24 12:58:20 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
2012-11-29 01:25:20 +01:00
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
|
|
|
|
|
2012-11-29 01:25:20 +01:00
|
|
|
|
2015-02-24 12:58:20 -06:00
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-11-29 01:25:20 +01:00
|
|
|
|
|
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-02-24 12:58:20 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-02-24 12:58:20 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
2015-02-24 12:58:20 -06:00
|
|
|
|
|
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-02-18 18:45:06 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
2012-11-29 01:25:20 +01:00
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
2012-11-29 01:25:20 +01:00
|
|
|
|
2015-02-24 12:58:20 -06:00
|
|
|
|
|
|
|
|
|
2012-11-29 01:25:20 +01:00
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-02-24 12:58:20 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-02-24 12:58:20 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-02-24 12:58:20 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
2009-02-18 18:45:06 +01:00
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-02-18 18:27:22 +01:00
|
|
|
|
2009-02-18 18:45:06 +01:00
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
2009-02-18 18:27:22 +01:00
|
|
|
|
|
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
2009-02-18 18:27:22 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-02-18 18:27:22 +01:00
|
|
|
|
|
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-02-24 12:58:20 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-02-24 12:58:20 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
2012-11-29 01:25:20 +01:00
|
|
|
|
|
|
|
|
|
2013-02-05 16:51:29 +01:00
|
|
|
|
|
|
|
|
|
2012-11-29 01:25:20 +01:00
|
|
|
|
2013-02-05 16:51:29 +01:00
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-02-24 12:58:20 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-02-24 12:58:20 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-11-18 18:40:00 +00:00
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
2012-11-29 01:25:20 +01:00
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
|
|
|
|
|
2023-09-12 06:55:16 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-02-24 12:58:20 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-09-12 06:55:16 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-02-24 12:58:20 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-09-12 06:55:16 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-02-24 12:58:20 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-09-12 06:55:16 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-02-24 12:58:20 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-09-12 06:55:16 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-02-24 12:58:20 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-09-12 06:55:16 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-02-24 12:58:20 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-09-12 06:55:16 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-02-24 12:58:20 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-02-24 12:58:20 -06:00
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
2015-02-24 12:58:20 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-11-29 16:55:45 -08:00
|
|
|
|
|
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-02-24 12:58:20 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
|
|
|
|
|
2015-02-24 12:58:20 -06:00
|
|
|
|
|
|
|
|
|
2023-09-12 06:55:16 +03:00
|
|
|
|
|
|
|
|
|
2015-02-24 12:58:20 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-09-12 06:55:16 +03:00
|
|
|
|
|
|
|
|
|
2015-02-24 12:58:20 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
2015-02-24 12:58:20 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-11-29 01:25:20 +01:00
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-04-21 12:53:02 +08:00
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-02-24 12:58:20 -06:00
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
2014-04-21 12:53:02 +08:00
|
|
|
|
|
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
2014-04-21 12:53:02 +08:00
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
2015-02-24 12:58:20 -06:00
|
|
|
|
|
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
2014-04-21 12:53:02 +08:00
|
|
|
|
2009-02-18 18:45:06 +01:00
|
|
|
|
2015-02-24 12:58:20 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
2014-04-21 12:53:02 +08:00
|
|
|
|
2015-02-24 12:58:20 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
wifi: cfg80211: Avoid clashing function prototypes
When built with Control Flow Integrity, function prototypes between
caller and function declaration must match. These mismatches are visible
at compile time with the new -Wcast-function-type-strict in Clang[1].
Fix a total of 73 warnings like these:
drivers/net/wireless/intersil/orinoco/wext.c:1379:27: warning: cast from 'int (*)(struct net_device *, struct iw_request_info *, struct iw_param *, char *)' to 'iw_handler' (aka 'int (*)(struct net_device *, struct iw_request_info *, union iwreq_data *, char *)') converts to incompatible function type [-Wcast-function-type-strict]
IW_HANDLER(SIOCGIWPOWER, (iw_handler)orinoco_ioctl_getpower),
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../net/wireless/wext-compat.c:1607:33: warning: cast from 'int (*)(struct net_device *, struct iw_request_info *, struct iw_point *, char *)' to 'iw_handler' (aka 'int (*)(struct net_device *, struct iw_request_info *, union iwreq_data *, char *)') converts to incompatible function type [-Wcast-function-type-strict]
[IW_IOCTL_IDX(SIOCSIWGENIE)] = (iw_handler) cfg80211_wext_siwgenie,
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../drivers/net/wireless/intersil/orinoco/wext.c:1390:27: error: incompatible function pointer types initializing 'const iw_handler' (aka 'int (*const)(struct net_device *, struct iw_request_info *, union iwreq_data *, char *)') with an expression of type 'int (struct net_device *, struct iw_request_info *, struct iw_param *, char *)' [-Wincompatible-function-pointer-types]
IW_HANDLER(SIOCGIWRETRY, cfg80211_wext_giwretry),
^~~~~~~~~~~~~~~~~~~~~~
The cfg80211 Wireless Extension handler callbacks (iw_handler) use a
union for the data argument. Actually use the union and perform explicit
member selection in the function body instead of having a function
prototype mismatch. There are no resulting binary differences
before/after changes.
These changes were made partly manually and partly with the help of
Coccinelle.
Link: https://github.com/KSPP/linux/issues/234
Link: https://reviews.llvm.org/D134831 [1]
Signed-off-by: Gustavo A. R. Silva <gustavoars@kernel.org>
Reviewed-by: Kees Cook <keescook@chromium.org>
Signed-off-by: Kalle Valo <kvalo@kernel.org>
Link: https://lore.kernel.org/r/a68822bf8dd587988131bb6a295280cb4293f05d.1667934775.git.gustavoars@kernel.org
2022-11-08 14:23:55 -06:00
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
wifi: cfg80211: Avoid clashing function prototypes
When built with Control Flow Integrity, function prototypes between
caller and function declaration must match. These mismatches are visible
at compile time with the new -Wcast-function-type-strict in Clang[1].
Fix a total of 73 warnings like these:
drivers/net/wireless/intersil/orinoco/wext.c:1379:27: warning: cast from 'int (*)(struct net_device *, struct iw_request_info *, struct iw_param *, char *)' to 'iw_handler' (aka 'int (*)(struct net_device *, struct iw_request_info *, union iwreq_data *, char *)') converts to incompatible function type [-Wcast-function-type-strict]
IW_HANDLER(SIOCGIWPOWER, (iw_handler)orinoco_ioctl_getpower),
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../net/wireless/wext-compat.c:1607:33: warning: cast from 'int (*)(struct net_device *, struct iw_request_info *, struct iw_point *, char *)' to 'iw_handler' (aka 'int (*)(struct net_device *, struct iw_request_info *, union iwreq_data *, char *)') converts to incompatible function type [-Wcast-function-type-strict]
[IW_IOCTL_IDX(SIOCSIWGENIE)] = (iw_handler) cfg80211_wext_siwgenie,
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../drivers/net/wireless/intersil/orinoco/wext.c:1390:27: error: incompatible function pointer types initializing 'const iw_handler' (aka 'int (*const)(struct net_device *, struct iw_request_info *, union iwreq_data *, char *)') with an expression of type 'int (struct net_device *, struct iw_request_info *, struct iw_param *, char *)' [-Wincompatible-function-pointer-types]
IW_HANDLER(SIOCGIWRETRY, cfg80211_wext_giwretry),
^~~~~~~~~~~~~~~~~~~~~~
The cfg80211 Wireless Extension handler callbacks (iw_handler) use a
union for the data argument. Actually use the union and perform explicit
member selection in the function body instead of having a function
prototype mismatch. There are no resulting binary differences
before/after changes.
These changes were made partly manually and partly with the help of
Coccinelle.
Link: https://github.com/KSPP/linux/issues/234
Link: https://reviews.llvm.org/D134831 [1]
Signed-off-by: Gustavo A. R. Silva <gustavoars@kernel.org>
Reviewed-by: Kees Cook <keescook@chromium.org>
Signed-off-by: Kalle Valo <kvalo@kernel.org>
Link: https://lore.kernel.org/r/a68822bf8dd587988131bb6a295280cb4293f05d.1667934775.git.gustavoars@kernel.org
2022-11-08 14:23:55 -06:00
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-07-14 00:33:35 +02:00
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
cfg80211: send scan results from work queue
Due to the previous commit, when a scan finishes, it is in theory
possible to hit the following sequence:
1. interface starts being removed
2. scan is cancelled by driver and cfg80211 is notified
3. scan done work is scheduled
4. interface is removed completely, rdev->scan_req is freed,
event sent to userspace but scan done work remains pending
5. new scan is requested on another virtual interface
6. scan done work runs, freeing the still-running scan
To fix this situation, hang on to the scan done message and block
new scans while that is the case, and only send the message from
the work function, regardless of whether the scan_req is already
freed from interface removal. This makes step 5 above impossible
and changes step 6 to be
5. scan done work runs, sending the scan done message
As this can't work for wext, so we send the message immediately,
but this shouldn't be an issue since we still return -EBUSY.
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2014-01-22 11:14:19 +02:00
|
|
|
|
2013-05-08 21:45:15 +02:00
|
|
|
|
2009-02-10 21:25:55 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
