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
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
2007-05-10 15:46:00 +02:00
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
2016-04-14 09:00:27 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2006-07-03 00:25:02 -07:00
|
|
|
|
2007-05-10 15:46:00 +02:00
|
|
|
|
2006-07-03 00:25:02 -07:00
|
|
|
|
2006-07-03 00:24:41 -07:00
|
|
|
|
2007-05-10 15:46:00 +02:00
|
|
|
|
2006-07-03 00:24:41 -07:00
|
|
|
|
2006-12-08 02:37:49 -08:00
|
|
|
|
2011-01-05 12:47:15 +01:00
|
|
|
|
2006-12-08 02:37:49 -08:00
|
|
|
|
|
|
|
|
|
2011-01-05 12:47:15 +01:00
|
|
|
|
2006-12-08 02:37:49 -08:00
|
|
|
|
2024-02-20 14:35:43 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2006-03-26 01:39:34 -08:00
|
|
|
|
2024-06-09 21:02:19 +02:00
|
|
|
|
2006-03-26 01:39:34 -08:00
|
|
|
|
2007-04-27 16:01:42 +02:00
|
|
|
|
2011-01-05 12:47:15 +01:00
|
|
|
|
2007-04-27 16:01:42 +02:00
|
|
|
|
2010-02-26 22:37:44 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-02-05 16:50:42 +01:00
|
|
|
|
2020-08-25 03:59:39 +02:00
|
|
|
|
2008-02-05 16:50:42 +01:00
|
|
|
|
2012-08-27 10:55:18 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-04-07 15:39:19 -07:00
|
|
|
|
2012-11-29 14:38:46 +01:00
|
|
|
|
|
|
|
|
|
2014-09-22 16:39:06 +02:00
|
|
|
|
2015-02-12 13:08:27 +01:00
|
|
|
|
2014-09-22 16:39:06 +02:00
|
|
|
|
2017-11-19 11:39:39 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-10-14 13:53:54 +02:00
|
|
|
|
2017-11-19 11:39:39 +01:00
|
|
|
|
2025-09-22 13:40:20 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-01-13 13:36:55 +01:00
|
|
|
|
2024-11-07 16:11:32 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-01-13 13:36:56 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-01-09 16:31:36 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-11-17 15:09:53 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2006-01-06 00:19:28 -08:00
|
|
|
|
2007-05-10 15:46:00 +02:00
|
|
|
|
2020-12-28 09:51:57 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
uaccess: generalize access_ok()
There are many different ways that access_ok() is defined across
architectures, but in the end, they all just compare against the
user_addr_max() value or they accept anything.
Provide one definition that works for most architectures, checking
against TASK_SIZE_MAX for user processes or skipping the check inside
of uaccess_kernel() sections.
For architectures without CONFIG_SET_FS(), this should be the fastest
check, as it comes down to a single comparison of a pointer against a
compile-time constant, while the architecture specific versions tend to
do something more complex for historic reasons or get something wrong.
Type checking for __user annotations is handled inconsistently across
architectures, but this is easily simplified as well by using an inline
function that takes a 'const void __user *' argument. A handful of
callers need an extra __user annotation for this.
Some architectures had trick to use 33-bit or 65-bit arithmetic on the
addresses to calculate the overflow, however this simpler version uses
fewer registers, which means it can produce better object code in the
end despite needing a second (statically predicted) branch.
Reviewed-by: Christoph Hellwig <hch@lst.de>
Acked-by: Mark Rutland <mark.rutland@arm.com> [arm64, asm-generic]
Acked-by: Geert Uytterhoeven <geert@linux-m68k.org>
Acked-by: Stafford Horne <shorne@gmail.com>
Acked-by: Dinh Nguyen <dinguyen@kernel.org>
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
2022-02-15 17:55:04 +01:00
|
|
|
|
2021-02-10 21:51:02 +01:00
|
|
|
|
2022-03-05 13:16:07 +01:00
|
|
|
|
2021-05-04 18:38:17 -07:00
|
|
|
|
2021-06-30 18:51:58 -07:00
|
|
|
|
s390/mm: Enable THP_SWAP and THP_MIGRATION
After hugetlbfs PTE_MARKER support for s390 introduced region-third and
segment table swap entries, it is now possible to also enable THP_SWAP
and THP_MIGRATION for s390.
s390 has different layout for PTE and region / segment table entries
(RSTE). This is also true for swap entries, and their swap type and offset
encoding. For hugetlbfs PTE_MARKER support, s390 has internal
__swp_type_rste() and __swp_offset_rste() helpers to correctly handle RSTE
swap entries.
But common swap code does not know about this difference, and only uses
__swp_type(), __swp_offset() and __swp_entry() helpers for conversion
between arch-dependent and arch-independent representation of swp_entry_t
for all pagetable levels. On s390, those helpers only work for PTE swap
entries.
Therefore, implement __pmd_to_swp_entry() to build a fake PTE swap entry
and return the arch-dependent representation of that. Correspondingly,
implement __swp_entry_to_pmd() to convert that into a proper PMD swap
entry again. With this, the arch-dependent swp_entry_t representation will
always look like a PTE swap entry in common code.
This is somewhat similar to fake PTEs in hugetlbfs code for s390, but only
requires conversion of the swap type and offset, and not all the possible
PTE bits.
For PMD swap entry SOFT_DIRTY handling, use the same helpers as for normal
PMDs. Similar to PTEs, the SOFT_DIRTY bit location is the same for swap
and normal entries.
Reviewed-by: Heiko Carstens <hca@linux.ibm.com>
Signed-off-by: Gerald Schaefer <gerald.schaefer@linux.ibm.com>
Signed-off-by: Alexander Gordeev <agordeev@linux.ibm.com>
2025-07-29 13:16:19 +02:00
|
|
|
|
2025-12-22 09:28:17 +01:00
|
|
|
|
2025-01-20 11:53:42 +01:00
|
|
|
|
2022-02-16 12:05:28 -08:00
|
|
|
|
2024-03-07 13:28:27 +01:00
|
|
|
|
mm/debug: add tests validating architecture page table helpers
This adds tests which will validate architecture page table helpers and
other accessors in their compliance with expected generic MM semantics.
This will help various architectures in validating changes to existing
page table helpers or addition of new ones.
This test covers basic page table entry transformations including but not
limited to old, young, dirty, clean, write, write protect etc at various
level along with populating intermediate entries with next page table page
and validating them.
Test page table pages are allocated from system memory with required size
and alignments. The mapped pfns at page table levels are derived from a
real pfn representing a valid kernel text symbol. This test gets called
via late_initcall().
This test gets built and run when CONFIG_DEBUG_VM_PGTABLE is selected.
Any architecture, which is willing to subscribe this test will need to
select ARCH_HAS_DEBUG_VM_PGTABLE. For now this is limited to arc, arm64,
x86, s390 and powerpc platforms where the test is known to build and run
successfully Going forward, other architectures too can subscribe the test
after fixing any build or runtime problems with their page table helpers.
Folks interested in making sure that a given platform's page table helpers
conform to expected generic MM semantics should enable the above config
which will just trigger this test during boot. Any non conformity here
will be reported as an warning which would need to be fixed. This test
will help catch any changes to the agreed upon semantics expected from
generic MM and enable platforms to accommodate it thereafter.
[anshuman.khandual@arm.com: v17]
Link: http://lkml.kernel.org/r/1587436495-22033-3-git-send-email-anshuman.khandual@arm.com
[anshuman.khandual@arm.com: v18]
Link: http://lkml.kernel.org/r/1588564865-31160-3-git-send-email-anshuman.khandual@arm.com
Suggested-by: Catalin Marinas <catalin.marinas@arm.com>
Signed-off-by: Anshuman Khandual <anshuman.khandual@arm.com>
Signed-off-by: Christophe Leroy <christophe.leroy@c-s.fr>
Signed-off-by: Qian Cai <cai@lca.pw>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Tested-by: Gerald Schaefer <gerald.schaefer@de.ibm.com> [s390]
Tested-by: Christophe Leroy <christophe.leroy@c-s.fr> [ppc32]
Reviewed-by: Ingo Molnar <mingo@kernel.org>
Cc: Mike Rapoport <rppt@linux.ibm.com>
Cc: Vineet Gupta <vgupta@synopsys.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>
Cc: Will Deacon <will@kernel.org>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Paul Mackerras <paulus@samba.org>
Cc: Michael Ellerman <mpe@ellerman.id.au>
Cc: Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: Vasily Gorbik <gor@linux.ibm.com>
Cc: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: Borislav Petkov <bp@alien8.de>
Cc: "H. Peter Anvin" <hpa@zytor.com>
Cc: Kirill A. Shutemov <kirill@shutemov.name>
Cc: Paul Walmsley <paul.walmsley@sifive.com>
Cc: Palmer Dabbelt <palmer@dabbelt.com>
Link: http://lkml.kernel.org/r/1583919272-24178-1-git-send-email-anshuman.khandual@arm.com
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2020-06-04 16:47:15 -07:00
|
|
|
|
2020-09-09 17:10:29 +02:00
|
|
|
|
2015-11-19 18:19:29 -08:00
|
|
|
|
2024-08-28 09:02:47 +03:00
|
|
|
|
2015-04-14 15:48:00 -07:00
|
|
|
|
2020-12-28 09:51:57 +01:00
|
|
|
|
2017-09-12 13:49:57 +02:00
|
|
|
|
2014-12-12 16:57:44 -08:00
|
|
|
|
2019-05-13 17:19:04 -07:00
|
|
|
|
2016-06-20 14:08:32 +02:00
|
|
|
|
2023-03-17 10:31:40 +01:00
|
|
|
|
2019-08-06 01:49:14 -03:00
|
|
|
|
2022-09-28 11:25:20 -07:00
|
|
|
|
2024-11-21 12:41:08 +01:00
|
|
|
|
2025-02-26 17:54:04 +05:30
|
|
|
|
2018-06-07 17:06:08 -07:00
|
|
|
|
2020-12-28 09:51:57 +01:00
|
|
|
|
2023-04-14 14:30:44 +02:00
|
|
|
|
2017-02-21 16:09:33 +01:00
|
|
|
|
2017-02-06 16:31:57 -08:00
|
|
|
|
|
|
|
|
|
s390: autogenerate compat syscall wrappers
Any system call that takes a pointer argument on s390 requires
a wrapper function to do a 31-to-64 zero-extension, these are
currently generated in arch/s390/kernel/compat_wrapper.c.
On arm64 and x86, we already generate similar wrappers for all
system calls in the place of their definition, just for a different
purpose (they load the arguments from pt_regs).
We can do the same thing here, by adding an asm/syscall_wrapper.h
file with a copy of all the relevant macros to override the generic
version. Besides the addition of the compat entry point, these also
rename the entry points with a __s390_ or __s390x_ prefix, similar
to what we do on arm64 and x86. This in turn requires renaming
a few things, and adding a proper ni_syscall() entry point.
In order to still compile system call definitions that pass an
loff_t argument, the __SC_COMPAT_CAST() macro checks for that
and forces an -ENOSYS error, which was the best I could come up
with. Those functions must obviously not get called from user
space, but instead require hand-written compat_sys_*() handlers,
which fortunately already exist.
Link: https://lore.kernel.org/lkml/20190116131527.2071570-5-arnd@arndb.de
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Reviewed-by: Heiko Carstens <heiko.carstens@de.ibm.com>
[heiko.carstens@de.ibm.com: compile fix for !CONFIG_COMPAT]
Signed-off-by: Heiko Carstens <heiko.carstens@de.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
2019-01-16 14:15:22 +01:00
|
|
|
|
2024-01-28 10:45:29 -08:00
|
|
|
|
2024-10-10 09:01:30 +02:00
|
|
|
|
2013-02-06 10:15:55 +01:00
|
|
|
|
2025-07-10 17:05:22 +02:00
|
|
|
|
2009-11-09 15:21:34 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-02-06 10:15:55 +01:00
|
|
|
|
2009-11-09 15:21:34 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-02-06 10:15:55 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-11-09 15:21:34 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-02-06 10:15:55 +01:00
|
|
|
|
2009-11-09 15:21:34 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-01-08 14:27:47 +01:00
|
|
|
|
2019-08-14 14:27:44 +02:00
|
|
|
|
2014-08-05 09:57:51 +02:00
|
|
|
|
2020-12-14 19:10:30 -08:00
|
|
|
|
2021-09-08 17:45:06 +02:00
|
|
|
|
2023-04-25 13:42:11 +02:00
|
|
|
|
2025-03-11 13:33:26 +01:00
|
|
|
|
2015-05-08 17:40:44 +02:00
|
|
|
|
2026-03-06 17:16:32 +01:00
|
|
|
|
2023-03-14 14:28:08 +01:00
|
|
|
|
2015-10-29 01:16:04 +01:00
|
|
|
|
2013-09-05 13:26:17 +02:00
|
|
|
|
2023-04-19 15:17:02 +02:00
|
|
|
|
2021-06-21 16:18:22 -07:00
|
|
|
|
2020-03-05 15:01:21 +01:00
|
|
|
|
2023-03-01 09:41:06 +01:00
|
|
|
|
2025-04-09 15:01:51 +02:00
|
|
|
|
2023-06-12 17:10:27 -07:00
|
|
|
|
2024-02-07 17:15:02 -07:00
|
|
|
|
s390/mm: Enable THP_SWAP and THP_MIGRATION
After hugetlbfs PTE_MARKER support for s390 introduced region-third and
segment table swap entries, it is now possible to also enable THP_SWAP
and THP_MIGRATION for s390.
s390 has different layout for PTE and region / segment table entries
(RSTE). This is also true for swap entries, and their swap type and offset
encoding. For hugetlbfs PTE_MARKER support, s390 has internal
__swp_type_rste() and __swp_offset_rste() helpers to correctly handle RSTE
swap entries.
But common swap code does not know about this difference, and only uses
__swp_type(), __swp_offset() and __swp_entry() helpers for conversion
between arch-dependent and arch-independent representation of swp_entry_t
for all pagetable levels. On s390, those helpers only work for PTE swap
entries.
Therefore, implement __pmd_to_swp_entry() to build a fake PTE swap entry
and return the arch-dependent representation of that. Correspondingly,
implement __swp_entry_to_pmd() to convert that into a proper PMD swap
entry again. With this, the arch-dependent swp_entry_t representation will
always look like a PTE swap entry in common code.
This is somewhat similar to fake PTEs in hugetlbfs code for s390, but only
requires conversion of the swap type and offset, and not all the possible
PTE bits.
For PMD swap entry SOFT_DIRTY handling, use the same helpers as for normal
PMDs. Similar to PTEs, the SOFT_DIRTY bit location is the same for swap
and normal entries.
Reviewed-by: Heiko Carstens <hca@linux.ibm.com>
Signed-off-by: Gerald Schaefer <gerald.schaefer@linux.ibm.com>
Signed-off-by: Alexander Gordeev <agordeev@linux.ibm.com>
2025-07-29 13:16:19 +02:00
|
|
|
|
2019-12-04 08:46:31 +08:00
|
|
|
|
2013-02-06 10:15:55 +01:00
|
|
|
|
2023-10-06 15:42:42 +02:00
|
|
|
|
2014-08-15 13:16:09 +02:00
|
|
|
|
2023-03-13 13:50:35 +01:00
|
|
|
|
|
|
|
|
|
2020-12-28 09:51:57 +01:00
|
|
|
|
2024-07-03 10:11:59 +02:00
|
|
|
|
2015-02-19 12:22:02 +01:00
|
|
|
|
2018-03-21 09:38:21 +01:00
|
|
|
|
2020-11-21 11:14:56 +01:00
|
|
|
|
2020-04-28 09:52:23 +02:00
|
|
|
|
2012-04-20 13:05:52 +00:00
|
|
|
|
2013-11-22 10:04:53 +01:00
|
|
|
|
2023-07-06 23:45:11 +08:00
|
|
|
|
2023-10-02 15:43:03 +02:00
|
|
|
|
2014-02-25 18:16:24 +09:00
|
|
|
|
2026-03-09 13:37:02 -07:00
|
|
|
|
2015-02-12 13:08:27 +01:00
|
|
|
|
2018-09-18 23:51:44 -07:00
|
|
|
|
2017-11-17 14:29:13 +01:00
|
|
|
|
2019-08-02 12:42:59 +02:00
|
|
|
|
2021-07-28 13:59:04 +02:00
|
|
|
|
2024-06-21 13:35:22 +02:00
|
|
|
|
2021-07-28 21:02:53 +02:00
|
|
|
|
2025-07-17 16:25:06 -07:00
|
|
|
|
2021-04-29 11:14:51 +02:00
|
|
|
|
2012-07-31 15:37:13 +02:00
|
|
|
|
2015-04-22 14:47:42 +02:00
|
|
|
|
2013-02-06 10:15:55 +01:00
|
|
|
|
2015-02-12 13:08:27 +01:00
|
|
|
|
2017-09-12 16:37:33 +02:00
|
|
|
|
2019-08-19 14:54:20 +09:00
|
|
|
|
2025-02-13 13:57:33 +01:00
|
|
|
|
2013-02-06 10:15:55 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-11-14 13:57:03 +01:00
|
|
|
|
2015-02-12 13:08:27 +01:00
|
|
|
|
2021-10-04 16:10:24 +02:00
|
|
|
|
2024-12-26 14:12:31 +09:00
|
|
|
|
2021-10-12 15:37:59 +02:00
|
|
|
|
2015-02-12 13:08:27 +01:00
|
|
|
|
2022-01-29 00:34:13 +01:00
|
|
|
|
2016-09-12 13:13:38 +02:00
|
|
|
|
2025-09-08 23:32:34 +02:00
|
|
|
|
2024-04-02 14:55:15 +02:00
|
|
|
|
2018-08-06 15:17:47 +02:00
|
|
|
|
2024-12-26 14:13:48 +09:00
|
|
|
|
2021-10-06 11:59:29 +02:00
|
|
|
|
2020-07-22 23:58:54 +02:00
|
|
|
|
2024-12-26 14:11:55 +09:00
|
|
|
|
2015-02-12 13:08:27 +01:00
|
|
|
|
|
|
|
|
|
2018-08-14 13:29:11 +02:00
|
|
|
|
2020-04-28 09:52:23 +02:00
|
|
|
|
2021-02-19 12:00:52 +01:00
|
|
|
|
2013-02-06 10:15:55 +01:00
|
|
|
|
|
|
|
|
|
2013-07-18 15:18:24 +02:00
|
|
|
|
2013-02-06 10:15:55 +01:00
|
|
|
|
|
|
|
|
|
2018-06-13 00:00:25 +02:00
|
|
|
|
2013-02-06 10:15:55 +01:00
|
|
|
|
2021-06-15 12:41:50 +01:00
|
|
|
|
2013-02-06 10:15:55 +01:00
|
|
|
|
2020-01-21 12:31:47 +01:00
|
|
|
|
2013-02-06 10:15:55 +01:00
|
|
|
|
2015-03-26 10:10:17 +01:00
|
|
|
|
2014-01-29 18:16:01 +01:00
|
|
|
|
2012-09-28 14:31:03 +09:30
|
|
|
|
2020-12-28 09:51:57 +01:00
|
|
|
|
2018-08-06 15:17:47 +02:00
|
|
|
|
2024-02-26 17:14:13 +01:00
|
|
|
|
2018-11-15 20:05:32 +01:00
|
|
|
|
2013-02-06 10:15:55 +01:00
|
|
|
|
2020-12-28 09:51:57 +01:00
|
|
|
|
|
|
|
|
|
2025-11-28 10:25:29 +01:00
|
|
|
|
2024-11-27 17:17:12 +01:00
|
|
|
|
2013-02-06 10:15:55 +01:00
|
|
|
|
s390/livepatch: Implement reliable stack tracing for the consistency model
The livepatch consistency model requires reliable stack tracing
architecture support in order to work properly. In order to achieve
this, two main issues have to be solved. First, reliable and consistent
call chain backtracing has to be ensured. Second, the unwinder needs to
be able to detect stack corruptions and return errors.
The "zSeries ELF Application Binary Interface Supplement" says:
"The stack pointer points to the first word of the lowest allocated
stack frame. If the "back chain" is implemented this word will point to
the previously allocated stack frame (towards higher addresses), except
for the first stack frame, which shall have a back chain of zero (NULL).
The stack shall grow downwards, in other words towards lower addresses."
"back chain" is optional. GCC option -mbackchain enables it. Quoting
Martin Schwidefsky [1]:
"The compiler is called with the -mbackchain option, all normal C
function will store the backchain in the function prologue. All
functions written in assembler code should do the same, if you find one
that does not we should fix that. The end result is that a task that
*voluntarily* called schedule() should have a proper backchain at all
times.
Dependent on the use case this may or may not be enough. Asynchronous
interrupts may stop the CPU at the beginning of a function, if kernel
preemption is enabled we can end up with a broken backchain. The
production kernels for IBM Z are all compiled *without* kernel
preemption. So yes, we might get away without the objtool support.
On a side-note, we do have a line item to implement the ORC unwinder for
the kernel, that includes the objtool support. Once we have that we can
drop the -mbackchain option for the kernel build. That gives us a nice
little performance benefit. I hope that the change from backchain to the
ORC unwinder will not be too hard to implement in the livepatch tools."
Since -mbackchain is enabled by default when the kernel is compiled, the
call chain backtracing should be currently ensured and objtool should
not be necessary for livepatch purposes.
Regarding the second issue, stack corruptions and non-reliable states
have to be recognized by the unwinder. Mainly it means to detect
preemption or page faults, the end of the task stack must be reached,
return addresses must be valid text addresses and hacks like function
graph tracing and kretprobes must be properly detected.
Unwinding a running task's stack is not a problem, because there is a
livepatch requirement that every checked task is blocked, except for the
current task. Due to that, the implementation can be much simpler
compared to the existing non-reliable infrastructure. We can consider a
task's kernel/thread stack only and skip the other stacks.
[1] 20180912121106.31ffa97c@mschwideX1 [not archived on lore.kernel.org]
Link: https://lkml.kernel.org/r/20191106095601.29986-5-mbenes@suse.cz
Reviewed-by: Heiko Carstens <heiko.carstens@de.ibm.com>
Tested-by: Miroslav Benes <mbenes@suse.cz>
Signed-off-by: Miroslav Benes <mbenes@suse.cz>
Signed-off-by: Vasily Gorbik <gor@linux.ibm.com>
2019-11-06 10:56:01 +01:00
|
|
|
|
2023-03-01 09:41:06 +01:00
|
|
|
|
2018-06-30 10:54:15 +02:00
|
|
|
|
2021-10-12 15:38:02 +02:00
|
|
|
|
2021-11-15 20:56:14 +01:00
|
|
|
|
2022-10-31 14:11:57 +01:00
|
|
|
|
2021-02-10 00:40:52 +01:00
|
|
|
|
2025-11-17 15:09:53 +01:00
|
|
|
|
2013-02-06 10:15:55 +01:00
|
|
|
|
|
|
|
|
|
2020-12-02 12:57:29 +01:00
|
|
|
|
2025-03-27 10:14:43 +01:00
|
|
|
|
2018-11-15 20:05:32 +01:00
|
|
|
|
|
|
|
|
|
2025-12-04 06:05:02 +01:00
|
|
|
|
2024-12-02 12:56:37 +01:00
|
|
|
|
2024-10-22 14:06:01 +02:00
|
|
|
|
2023-03-01 09:41:06 +01:00
|
|
|
|
2020-12-28 09:51:57 +01:00
|
|
|
|
|
|
|
|
|
2012-09-28 14:31:03 +09:30
|
|
|
|
2018-11-15 20:05:32 +01:00
|
|
|
|
2022-10-31 14:11:57 +01:00
|
|
|
|
2024-12-04 13:54:43 +01:00
|
|
|
|
2018-11-15 20:05:32 +01:00
|
|
|
|
2012-12-25 19:26:12 -05:00
|
|
|
|
2013-09-06 10:03:30 +02:00
|
|
|
|
2018-11-15 20:05:33 +01:00
|
|
|
|
2018-11-15 20:05:32 +01:00
|
|
|
|
2020-09-28 12:13:07 +02:00
|
|
|
|
2025-02-26 13:07:47 +01:00
|
|
|
|
2016-06-02 14:57:17 +02:00
|
|
|
|
2020-12-28 09:51:57 +01:00
|
|
|
|
2013-02-06 10:15:55 +01:00
|
|
|
|
2026-02-16 07:29:16 +01:00
|
|
|
|
2016-11-08 11:08:26 +01:00
|
|
|
|
2021-07-31 14:22:32 +09:00
|
|
|
|
2014-02-26 18:13:06 -08:00
|
|
|
|
2023-10-30 16:50:47 +01:00
|
|
|
|
2024-09-13 15:05:43 +02:00
|
|
|
|
2013-02-06 10:15:55 +01:00
|
|
|
|
2024-12-02 12:56:38 +01:00
|
|
|
|
2021-06-30 18:52:20 -07:00
|
|
|
|
2020-12-28 09:51:57 +01:00
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
2009-07-07 16:37:10 +02:00
|
|
|
|
2011-01-05 12:47:15 +01:00
|
|
|
|
2009-07-07 16:37:10 +02:00
|
|
|
|
2015-04-14 15:46:00 -07:00
|
|
|
|
|
|
|
|
|
2017-04-24 18:19:10 +02:00
|
|
|
|
2015-04-14 15:46:00 -07:00
|
|
|
|
2015-03-26 10:10:17 +01:00
|
|
|
|
|
|
|
|
|
2025-12-22 09:28:17 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-07-12 12:15:43 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
kexec: fix KEXEC_FILE dependencies
The cleanup for the CONFIG_KEXEC Kconfig logic accidentally changed the
'depends on CRYPTO=y' dependency to a plain 'depends on CRYPTO', which
causes a link failure when all the crypto support is in a loadable module
and kexec_file support is built-in:
x86_64-linux-ld: vmlinux.o: in function `__x64_sys_kexec_file_load':
(.text+0x32e30a): undefined reference to `crypto_alloc_shash'
x86_64-linux-ld: (.text+0x32e58e): undefined reference to `crypto_shash_update'
x86_64-linux-ld: (.text+0x32e6ee): undefined reference to `crypto_shash_final'
Both s390 and x86 have this problem, while ppc64 and riscv have the
correct dependency already. On riscv, the dependency is only used for the
purgatory, not for the kexec_file code itself, which may be a bit
surprising as it means that with CONFIG_CRYPTO=m, it is possible to enable
KEXEC_FILE but then the purgatory code is silently left out.
Move this into the common Kconfig.kexec file in a way that is correct
everywhere, using the dependency on CRYPTO_SHA256=y only when the
purgatory code is available. This requires reversing the dependency
between ARCH_SUPPORTS_KEXEC_PURGATORY and KEXEC_FILE, but the effect
remains the same, other than making riscv behave like the other ones.
On s390, there is an additional dependency on CRYPTO_SHA256_S390, which
should technically not be required but gives better performance. Remove
this dependency here, noting that it was not present in the initial
Kconfig code but was brought in without an explanation in commit
71406883fd357 ("s390/kexec_file: Add kexec_file_load system call").
[arnd@arndb.de: fix riscv build]
Link: https://lkml.kernel.org/r/67ddd260-d424-4229-a815-e3fcfb864a77@app.fastmail.com
Link: https://lkml.kernel.org/r/20231023110308.1202042-1-arnd@kernel.org
Fixes: 6af5138083005 ("x86/kexec: refactor for kernel/Kconfig.kexec")
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Reviewed-by: Eric DeVolder <eric_devolder@yahoo.com>
Tested-by: Eric DeVolder <eric_devolder@yahoo.com>
Cc: Albert Ou <aou@eecs.berkeley.edu>
Cc: Alexander Gordeev <agordeev@linux.ibm.com>
Cc: Ard Biesheuvel <ardb@kernel.org>
Cc: Borislav Petkov <bp@alien8.de>
Cc: Christian Borntraeger <borntraeger@linux.ibm.com>
Cc: Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: Conor Dooley <conor@kernel.org>
Cc: Dave Hansen <dave.hansen@linux.intel.com>
Cc: David S. Miller <davem@davemloft.net>
Cc: Heiko Carstens <hca@linux.ibm.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>
Cc: "H. Peter Anvin" <hpa@zytor.com>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: Nicholas Piggin <npiggin@gmail.com>
Cc: Palmer Dabbelt <palmer@dabbelt.com>
Cc: Paul Walmsley <paul.walmsley@sifive.com>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Sven Schnelle <svens@linux.ibm.com>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Vasily Gorbik <gor@linux.ibm.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
2023-10-23 13:01:54 +02:00
|
|
|
|
2023-07-12 12:15:43 -04:00
|
|
|
|
|
|
|
|
|
2026-02-16 07:29:16 +01:00
|
|
|
|
2023-07-12 12:15:43 -04:00
|
|
|
|
2023-07-12 12:15:45 -04:00
|
|
|
|
kexec: fix KEXEC_FILE dependencies
The cleanup for the CONFIG_KEXEC Kconfig logic accidentally changed the
'depends on CRYPTO=y' dependency to a plain 'depends on CRYPTO', which
causes a link failure when all the crypto support is in a loadable module
and kexec_file support is built-in:
x86_64-linux-ld: vmlinux.o: in function `__x64_sys_kexec_file_load':
(.text+0x32e30a): undefined reference to `crypto_alloc_shash'
x86_64-linux-ld: (.text+0x32e58e): undefined reference to `crypto_shash_update'
x86_64-linux-ld: (.text+0x32e6ee): undefined reference to `crypto_shash_final'
Both s390 and x86 have this problem, while ppc64 and riscv have the
correct dependency already. On riscv, the dependency is only used for the
purgatory, not for the kexec_file code itself, which may be a bit
surprising as it means that with CONFIG_CRYPTO=m, it is possible to enable
KEXEC_FILE but then the purgatory code is silently left out.
Move this into the common Kconfig.kexec file in a way that is correct
everywhere, using the dependency on CRYPTO_SHA256=y only when the
purgatory code is available. This requires reversing the dependency
between ARCH_SUPPORTS_KEXEC_PURGATORY and KEXEC_FILE, but the effect
remains the same, other than making riscv behave like the other ones.
On s390, there is an additional dependency on CRYPTO_SHA256_S390, which
should technically not be required but gives better performance. Remove
this dependency here, noting that it was not present in the initial
Kconfig code but was brought in without an explanation in commit
71406883fd357 ("s390/kexec_file: Add kexec_file_load system call").
[arnd@arndb.de: fix riscv build]
Link: https://lkml.kernel.org/r/67ddd260-d424-4229-a815-e3fcfb864a77@app.fastmail.com
Link: https://lkml.kernel.org/r/20231023110308.1202042-1-arnd@kernel.org
Fixes: 6af5138083005 ("x86/kexec: refactor for kernel/Kconfig.kexec")
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Reviewed-by: Eric DeVolder <eric_devolder@yahoo.com>
Tested-by: Eric DeVolder <eric_devolder@yahoo.com>
Cc: Albert Ou <aou@eecs.berkeley.edu>
Cc: Alexander Gordeev <agordeev@linux.ibm.com>
Cc: Ard Biesheuvel <ardb@kernel.org>
Cc: Borislav Petkov <bp@alien8.de>
Cc: Christian Borntraeger <borntraeger@linux.ibm.com>
Cc: Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: Conor Dooley <conor@kernel.org>
Cc: Dave Hansen <dave.hansen@linux.intel.com>
Cc: David S. Miller <davem@davemloft.net>
Cc: Heiko Carstens <hca@linux.ibm.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>
Cc: "H. Peter Anvin" <hpa@zytor.com>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: Nicholas Piggin <npiggin@gmail.com>
Cc: Palmer Dabbelt <palmer@dabbelt.com>
Cc: Paul Walmsley <paul.walmsley@sifive.com>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Sven Schnelle <svens@linux.ibm.com>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Vasily Gorbik <gor@linux.ibm.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
2023-10-23 13:01:54 +02:00
|
|
|
|
2023-07-12 12:15:43 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-08-29 14:53:51 -07:00
|
|
|
|
2023-07-12 12:15:43 -04:00
|
|
|
|
2023-08-29 14:53:51 -07:00
|
|
|
|
2023-07-12 12:15:43 -04:00
|
|
|
|
2024-09-17 12:37:20 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-08-27 10:55:18 +02:00
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
2012-08-27 10:55:18 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-11-13 10:26:37 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-01-14 17:50:19 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-04-12 14:17:25 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-02-06 08:22:11 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-07-20 14:28:08 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-08-26 22:13:47 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-08-27 10:55:18 +02:00
|
|
|
|
|
|
|
|
|
2016-04-18 17:10:16 +02:00
|
|
|
|
2012-08-27 10:55:18 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-02-12 13:08:27 +01:00
|
|
|
|
2019-10-06 16:55:53 +02:00
|
|
|
|
2012-08-27 10:55:18 +02:00
|
|
|
|
2022-02-24 22:43:31 +01:00
|
|
|
|
|
|
|
|
|
2012-08-27 10:55:18 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-02-12 13:08:27 +01:00
|
|
|
|
2019-10-06 16:55:53 +02:00
|
|
|
|
2012-08-27 10:55:18 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-11-13 10:26:37 +02:00
|
|
|
|
2013-07-24 10:35:33 +02:00
|
|
|
|
2015-02-12 13:08:27 +01:00
|
|
|
|
2019-10-06 16:55:53 +02:00
|
|
|
|
2012-11-13 10:26:37 +02:00
|
|
|
|
2013-07-24 10:35:33 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-11-13 10:26:37 +02:00
|
|
|
|
2015-01-14 17:50:19 +01:00
|
|
|
|
2016-02-19 10:46:08 +01:00
|
|
|
|
2015-02-12 13:08:27 +01:00
|
|
|
|
2019-10-06 16:55:53 +02:00
|
|
|
|
2015-01-14 17:50:19 +01:00
|
|
|
|
2016-02-19 10:46:08 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-01-14 17:50:19 +01:00
|
|
|
|
2017-04-12 14:17:25 +02:00
|
|
|
|
2018-04-13 14:04:24 +02:00
|
|
|
|
2017-04-12 14:17:25 +02:00
|
|
|
|
2019-10-06 16:55:53 +02:00
|
|
|
|
2017-04-12 14:17:25 +02:00
|
|
|
|
2018-04-13 14:04:24 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-04-12 14:17:25 +02:00
|
|
|
|
2019-02-06 08:22:11 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-10-06 16:55:53 +02:00
|
|
|
|
2019-02-06 08:22:11 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-07-20 14:28:08 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-08-26 22:13:47 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-08-27 10:55:18 +02:00
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
2013-10-30 12:12:50 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-01-14 17:50:19 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-04-12 14:17:25 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-02-06 08:22:11 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-07-20 14:28:08 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-08-26 22:13:47 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-10-30 12:12:50 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-10-06 16:55:53 +02:00
|
|
|
|
2013-10-30 12:12:50 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-10-06 16:55:53 +02:00
|
|
|
|
2013-10-30 12:12:50 +01:00
|
|
|
|
2015-01-14 17:50:19 +01:00
|
|
|
|
2019-10-06 17:02:07 +02:00
|
|
|
|
2019-10-06 16:55:53 +02:00
|
|
|
|
2015-01-14 17:50:19 +01:00
|
|
|
|
2017-04-12 14:17:25 +02:00
|
|
|
|
2019-10-06 17:02:07 +02:00
|
|
|
|
2019-10-06 16:55:53 +02:00
|
|
|
|
2017-04-12 14:17:25 +02:00
|
|
|
|
2019-02-06 08:22:11 +01:00
|
|
|
|
|
|
|
|
|
2019-10-06 16:55:53 +02:00
|
|
|
|
2019-02-06 08:22:11 +01:00
|
|
|
|
2021-07-20 14:28:08 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-08-26 22:13:47 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-10-30 12:12:50 +01:00
|
|
|
|
|
|
|
|
|
2006-01-06 00:19:28 -08:00
|
|
|
|
2011-01-05 12:47:15 +01:00
|
|
|
|
2006-09-28 16:55:39 +02:00
|
|
|
|
2021-09-29 09:09:34 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
2011-01-05 12:47:15 +01:00
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
|
|
|
|
|
2015-01-28 16:52:01 +01:00
|
|
|
|
|
|
|
|
|
2015-02-12 13:08:27 +01:00
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
|
|
|
|
|
2015-01-28 16:52:01 +01:00
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-01-05 12:47:15 +01:00
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
2014-03-06 18:25:13 +01:00
|
|
|
|
|
|
|
|
|
2019-06-03 14:25:18 +02:00
|
|
|
|
2014-03-06 18:25:13 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-02-19 13:29:15 +01:00
|
|
|
|
2021-06-28 19:43:01 -07:00
|
|
|
|
2020-02-19 13:29:15 +01:00
|
|
|
|
2015-12-28 13:20:43 +01:00
|
|
|
|
2015-01-14 17:52:10 +01:00
|
|
|
|
2011-01-05 12:47:15 +01:00
|
|
|
|
2015-01-14 17:52:10 +01:00
|
|
|
|
2025-08-26 11:08:57 +02:00
|
|
|
|
|
|
|
|
|
2015-01-14 17:52:10 +01:00
|
|
|
|
2011-12-27 11:27:09 +01:00
|
|
|
|
2010-08-31 10:28:18 +02:00
|
|
|
|
2015-01-14 17:52:10 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-08-31 10:28:18 +02:00
|
|
|
|
2024-08-12 13:39:32 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-08-12 13:39:37 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-12-11 20:01:04 +09:00
|
|
|
|
2012-08-27 10:55:18 +02:00
|
|
|
|
2023-04-28 06:42:42 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-07-28 12:04:30 +02:00
|
|
|
|
2023-04-28 06:42:42 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-01-16 07:11:45 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-01-26 12:46:47 +01:00
|
|
|
|
|
|
|
|
|
2022-03-06 20:56:07 +01:00
|
|
|
|
2018-01-26 12:46:47 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-03-06 20:56:07 +01:00
|
|
|
|
2024-08-26 23:16:06 +02:00
|
|
|
|
|
|
|
|
|
2022-03-06 20:56:07 +01:00
|
|
|
|
2024-08-26 23:16:06 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-01-26 12:46:47 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-03-23 13:04:49 +01:00
|
|
|
|
2018-01-26 12:46:47 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-02-03 21:35:45 +01:00
|
|
|
|
2022-10-30 19:22:02 +01:00
|
|
|
|
2025-03-11 12:06:19 +01:00
|
|
|
|
2019-02-03 21:35:45 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-10-30 19:22:02 +01:00
|
|
|
|
|
|
|
|
|
2019-02-03 21:35:45 +01:00
|
|
|
|
2019-02-03 21:37:20 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-08-09 08:47:16 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-09-26 15:58:51 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-08-27 10:55:18 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-01-05 12:47:15 +01:00
|
|
|
|
2012-08-27 10:55:18 +02:00
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
2012-08-27 10:55:18 +02:00
|
|
|
|
2011-01-05 12:47:15 +01:00
|
|
|
|
2006-09-12 03:04:40 -04:00
|
|
|
|
2026-01-16 16:02:42 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-03-27 15:36:20 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-08-27 10:55:18 +02:00
|
|
|
|
2007-05-10 15:46:00 +02:00
|
|
|
|
2012-08-27 10:55:18 +02:00
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
|
|
|
|
|
2011-01-05 12:47:15 +01:00
|
|
|
|
|
|
|
|
|
2020-06-14 01:50:22 +09:00
|
|
|
|
2006-01-06 00:19:20 -08:00
|
|
|
|
2008-04-17 07:46:19 +02:00
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-11-29 14:38:46 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-11-19 11:38:46 +01:00
|
|
|
|
2012-11-29 14:38:46 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-03-06 21:32:01 +01:00
|
|
|
|
2012-11-29 14:38:46 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-07-14 09:59:05 +02:00
|
|
|
|
2011-01-31 11:30:09 +01:00
|
|
|
|
2011-01-05 12:47:15 +01:00
|
|
|
|
2008-07-14 09:59:05 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-08-28 16:46:26 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-08-28 16:48:16 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-02-19 18:10:19 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-02-27 16:49:33 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-03-17 04:17:31 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-01-26 22:08:31 +01:00
|
|
|
|
2023-01-10 10:10:07 +01:00
|
|
|
|
2017-03-17 04:17:31 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-09-25 19:16:19 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-05-01 14:11:28 -03:00
|
|
|
|
2023-01-26 22:08:31 +01:00
|
|
|
|
2024-02-19 18:10:19 +01:00
|
|
|
|
2023-01-26 22:08:31 +01:00
|
|
|
|
2018-09-25 19:16:19 -04:00
|
|
|
|
2022-05-25 14:01:40 +02:00
|
|
|
|
|
|
|
|
|
2018-09-25 19:16:19 -04:00
|
|
|
|
2022-05-25 14:01:40 +02:00
|
|
|
|
|
|
|
|
|
2018-09-25 19:16:19 -04:00
|
|
|
|
2012-08-27 10:55:18 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-05-22 12:42:57 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-08-27 10:55:18 +02:00
|
|
|
|
2008-03-05 12:37:14 +01:00
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
2011-01-05 12:47:15 +01:00
|
|
|
|
|
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-01-05 12:47:15 +01:00
|
|
|
|
|
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-01-05 12:47:15 +01:00
|
|
|
|
|
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-01-05 12:47:15 +01:00
|
|
|
|
|
|
|
|
|
2021-05-27 17:24:20 -07:00
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-01-05 12:47:15 +01:00
|
|
|
|
|
|
|
|
|
2006-12-13 00:34:59 -08:00
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-01-05 12:47:15 +01:00
|
|
|
|
|
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-01-05 12:47:15 +01:00
|
|
|
|
|
|
|
|
|
2009-03-26 15:24:00 +01:00
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-07-04 15:47:13 +02:00
|
|
|
|
2011-01-05 12:47:15 +01:00
|
|
|
|
2023-07-04 15:47:13 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-01-05 12:47:15 +01:00
|
|
|
|
2006-06-23 02:05:06 -07:00
|
|
|
|
2023-07-04 15:47:13 +02:00
|
|
|
|
2006-06-23 02:05:06 -07:00
|
|
|
|
|
|
|
|
|
2023-07-04 15:47:13 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2006-06-23 02:05:06 -07:00
|
|
|
|
2012-08-27 10:55:18 +02:00
|
|
|
|
2007-04-27 16:01:49 +02:00
|
|
|
|
2008-03-25 18:47:44 +01:00
|
|
|
|
2011-01-05 12:47:15 +01:00
|
|
|
|
2012-10-02 11:16:42 -07:00
|
|
|
|
2013-07-23 16:26:08 +08:00
|
|
|
|
2011-06-22 16:24:07 +02:00
|
|
|
|
2008-03-25 18:47:44 +01:00
|
|
|
|
|
|
|
|
|
2012-08-27 12:56:48 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-08-29 13:30:56 +02:00
|
|
|
|
2012-08-27 12:56:48 +02:00
|
|
|
|
2009-06-12 10:26:26 +02:00
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
2019-10-17 15:09:08 +02:00
|
|
|
|
2022-01-19 19:26:38 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-10-17 15:09:08 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-10-01 15:52:00 +02:00
|
|
|
|
|
|
|
|
|
2019-10-17 15:09:08 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-09-09 20:59:17 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-01-19 19:26:38 +01:00
|
|
|
|
|
|
|
|
|
2026-02-25 10:30:25 +01:00
|
|
|
|
2022-01-19 19:26:38 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-10-17 15:09:08 +02:00
|
|
|
|