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
|
|
|
|
2017-01-09 16:55:25 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-02-02 08:35:14 +01:00
|
|
|
|
|
|
|
|
|
2017-01-09 16:55:25 +01:00
|
|
|
|
2019-10-21 16:13:12 +02:00
|
|
|
|
2017-01-09 16:55:25 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-04-11 11:17:30 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-01-09 16:55:25 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-03-28 14:10:36 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-01-09 16:55:25 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-05-09 18:29:48 +00:00
|
|
|
|
|
|
|
|
|
2019-10-21 16:13:08 +02:00
|
|
|
|
2017-01-09 16:55:25 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-10-21 16:13:08 +02:00
|
|
|
|
|
|
|
|
|
2017-01-09 16:55:25 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-10-21 16:13:12 +02:00
|
|
|
|
2017-01-09 16:55:25 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-11-14 13:02:41 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-11-03 14:07:40 +08:00
|
|
|
|
|
|
|
|
|
2019-11-14 13:02:41 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-01-09 16:55:25 +01:00
|
|
|
|
2018-01-25 11:15:35 +01:00
|
|
|
|
2017-01-09 16:55:25 +01:00
|
|
|
|
2019-10-21 16:13:15 +02:00
|
|
|
|
2017-01-09 16:55:25 +01:00
|
|
|
|
2018-01-24 10:28:12 +01:00
|
|
|
|
2019-10-21 16:13:15 +02:00
|
|
|
|
2018-01-24 10:28:12 +01:00
|
|
|
|
2018-09-18 15:46:36 +02:00
|
|
|
|
|
|
|
|
|
2019-10-21 16:13:12 +02:00
|
|
|
|
|
|
|
|
|
2017-01-09 16:55:25 +01:00
|
|
|
|
2018-01-24 10:28:12 +01:00
|
|
|
|
2017-04-10 14:58:01 +02:00
|
|
|
|
2017-01-09 16:55:25 +01:00
|
|
|
|
|
|
|
|
|
2020-09-03 21:53:18 +02:00
|
|
|
|
2019-11-14 13:02:41 +01:00
|
|
|
|
2020-09-03 21:53:18 +02:00
|
|
|
|
|
|
|
|
|
2019-10-09 10:07:47 +02:00
|
|
|
|
2020-09-03 21:53:18 +02:00
|
|
|
|
2017-01-09 16:55:25 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-10-09 10:07:47 +02:00
|
|
|
|
2019-11-14 13:02:41 +01:00
|
|
|
|
|
|
|
|
|
2020-09-03 21:53:18 +02:00
|
|
|
|
|
|
|
|
|
2019-10-09 10:07:47 +02:00
|
|
|
|
2019-10-21 16:13:15 +02:00
|
|
|
|
|
|
|
|
|
2018-01-26 09:28:48 +01:00
|
|
|
|
2017-01-09 16:55:25 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-11-14 13:02:41 +01:00
|
|
|
|
|
|
|
|
|
2020-09-03 21:53:18 +02:00
|
|
|
|
|
|
|
|
|
2018-01-24 10:28:12 +01:00
|
|
|
|
2019-11-14 13:02:41 +01:00
|
|
|
|
|
|
|
|
|
2017-01-09 16:55:25 +01:00
|
|
|
|
2018-09-18 15:46:36 +02:00
|
|
|
|
2017-01-09 16:55:25 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-11-03 14:07:38 +08:00
|
|
|
|
2018-01-24 10:28:12 +01:00
|
|
|
|
2019-10-21 16:13:15 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-01-09 16:55:25 +01:00
|
|
|
|
|
|
|
|
|
2017-04-10 14:58:02 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-01-09 16:55:25 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-09-21 09:16:34 +02:00
|
|
|
|
2017-01-09 16:55:25 +01:00
|
|
|
|
2021-12-01 14:42:16 +08:00
|
|
|
|
2017-01-09 16:55:25 +01:00
|
|
|
|
2017-09-21 09:16:34 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-01-09 16:55:25 +01:00
|
|
|
|
|
|
|
|
|
2018-01-24 10:28:16 +01:00
|
|
|
|
|
|
|
|
|
2017-01-09 16:55:25 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-09-15 22:57:09 +02:00
|
|
|
|
2022-04-22 15:56:19 +08:00
|
|
|
|
2022-04-22 15:56:18 +08:00
|
|
|
|
|
|
|
|
|
net/smc: fix NULL dereference and UAF in smc_tcp_syn_recv_sock()
Syzkaller reported a panic in smc_tcp_syn_recv_sock() [1].
smc_tcp_syn_recv_sock() is called in the TCP receive path
(softirq) via icsk_af_ops->syn_recv_sock on the clcsock (TCP
listening socket). It reads sk_user_data to get the smc_sock
pointer. However, when the SMC listen socket is being closed
concurrently, smc_close_active() sets clcsock->sk_user_data
to NULL under sk_callback_lock, and then the smc_sock itself
can be freed via sock_put() in smc_release().
This leads to two issues:
1) NULL pointer dereference: sk_user_data is NULL when
accessed.
2) Use-after-free: sk_user_data is read as non-NULL, but the
smc_sock is freed before its fields (e.g., queued_smc_hs,
ori_af_ops) are accessed.
The race window looks like this (the syzkaller crash [1]
triggers via the SYN cookie path: tcp_get_cookie_sock() ->
smc_tcp_syn_recv_sock(), but the normal tcp_check_req() path
has the same race):
CPU A (softirq) CPU B (process ctx)
tcp_v4_rcv()
TCP_NEW_SYN_RECV:
sk = req->rsk_listener
sock_hold(sk)
/* No lock on listener */
smc_close_active():
write_lock_bh(cb_lock)
sk_user_data = NULL
write_unlock_bh(cb_lock)
...
smc_clcsock_release()
sock_put(smc->sk) x2
-> smc_sock freed!
tcp_check_req()
smc_tcp_syn_recv_sock():
smc = user_data(sk)
-> NULL or dangling
smc->queued_smc_hs
-> crash!
Note that the clcsock and smc_sock are two independent objects
with separate refcounts. TCP stack holds a reference on the
clcsock, which keeps it alive, but this does NOT prevent the
smc_sock from being freed.
Fix this by using RCU and refcount_inc_not_zero() to safely
access smc_sock. Since smc_tcp_syn_recv_sock() is called in
the TCP three-way handshake path, taking read_lock_bh on
sk_callback_lock is too heavy and would not survive a SYN
flood attack. Using rcu_read_lock() is much more lightweight.
- Set SOCK_RCU_FREE on the SMC listen socket so that
smc_sock freeing is deferred until after the RCU grace
period. This guarantees the memory is still valid when
accessed inside rcu_read_lock().
- Use rcu_read_lock() to protect reading sk_user_data.
- Use refcount_inc_not_zero(&smc->sk.sk_refcnt) to pin the
smc_sock. If the refcount has already reached zero (close
path completed), it returns false and we bail out safely.
Note: smc_hs_congested() has a similar lockless read of
sk_user_data without rcu_read_lock(), but it only checks for
NULL and accesses the global smc_hs_wq, never dereferencing
any smc_sock field, so it is not affected.
Reproducer was verified with mdelay injection and smc_run,
the issue no longer occurs with this patch applied.
[1] https://syzkaller.appspot.com/bug?extid=827ae2bfb3a3529333e9
Fixes: 8270d9c21041 ("net/smc: Limit backlog connections")
Reported-by: syzbot+827ae2bfb3a3529333e9@syzkaller.appspotmail.com
Closes: https://lore.kernel.org/all/67eaf9b8.050a0220.3c3d88.004a.GAE@google.com/T/
Suggested-by: Eric Dumazet <edumazet@google.com>
Reviewed-by: Eric Dumazet <edumazet@google.com>
Signed-off-by: Jiayuan Chen <jiayuan.chen@shopee.com>
Link: https://patch.msgid.link/20260312092909.48325-1-jiayuan.chen@linux.dev
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
2026-03-12 17:29:07 +08:00
|
|
|
|
2022-04-22 15:56:19 +08:00
|
|
|
|
2017-01-09 16:55:25 +01:00
|
|
|
|
2020-09-15 22:57:09 +02:00
|
|
|
|
2017-01-09 16:55:25 +01:00
|
|
|
|
2018-03-13 10:41:54 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-01-09 16:55:25 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-09-21 09:16:33 +02:00
|
|
|
|
2017-01-09 16:55:25 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
net/smc: Ensure the active closing peer first closes clcsock
The side that actively closed socket, it's clcsock doesn't enter
TIME_WAIT state, but the passive side does it. It should show the same
behavior as TCP sockets.
Consider this, when client actively closes the socket, the clcsock in
server enters TIME_WAIT state, which means the address is occupied and
won't be reused before TIME_WAIT dismissing. If we restarted server, the
service would be unavailable for a long time.
To solve this issue, shutdown the clcsock in [A], perform the TCP active
close progress first, before the passive closed side closing it. So that
the actively closed side enters TIME_WAIT, not the passive one.
Client | Server
close() // client actively close |
smc_release() |
smc_close_active() // PEERCLOSEWAIT1 |
smc_close_final() // abort or closed = 1|
smc_cdc_get_slot_and_msg_send() |
[A] |
|smc_cdc_msg_recv_action() // ACTIVE
| queue_work(smc_close_wq, &conn->close_work)
| smc_close_passive_work() // PROCESSABORT or APPCLOSEWAIT1
| smc_close_passive_abort_received() // only in abort
|
|close() // server recv zero, close
| smc_release() // PROCESSABORT or APPCLOSEWAIT1
| smc_close_active()
| smc_close_abort() or smc_close_final() // CLOSED
| smc_cdc_get_slot_and_msg_send() // abort or closed = 1
smc_cdc_msg_recv_action() | smc_clcsock_release()
queue_work(smc_close_wq, &conn->close_work) | sock_release(tcp) // actively close clc, enter TIME_WAIT
smc_close_passive_work() // PEERCLOSEWAIT1 | smc_conn_free()
smc_close_passive_abort_received() // CLOSED|
smc_conn_free() |
smc_clcsock_release() |
sock_release(tcp) // passive close clc |
Link: https://www.spinics.net/lists/netdev/msg780407.html
Fixes: b38d732477e4 ("smc: socket closing and linkgroup cleanup")
Signed-off-by: Tony Lu <tonylu@linux.alibaba.com>
Reviewed-by: Wen Gu <guwen@linux.alibaba.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2021-11-23 16:25:18 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-12-01 14:42:16 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-01-09 16:55:25 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-04-10 14:58:02 +02:00
|
|
|
|
2017-01-09 16:55:25 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-09-21 09:16:33 +02:00
|
|
|
|
2017-01-09 16:55:25 +01:00
|
|
|
|
2018-01-24 10:28:16 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-01-26 09:28:48 +01:00
|
|
|
|
2017-01-09 16:55:25 +01:00
|
|
|
|
|
|
|
|
|
2018-01-26 09:28:48 +01:00
|
|
|
|
|
|
|
|
|
2017-01-09 16:55:25 +01:00
|
|
|
|
|
|
|
|
|
2018-01-26 09:28:48 +01:00
|
|
|
|
2017-01-09 16:55:25 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-04-10 14:58:02 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-01-09 16:55:25 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-10-09 10:07:47 +02:00
|
|
|
|
2017-01-09 16:55:25 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-10-09 10:07:47 +02:00
|
|
|
|
|
|
|
|
|
2017-01-09 16:55:25 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-01-24 10:28:12 +01:00
|
|
|
|
2017-01-09 16:55:25 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-01-26 09:28:48 +01:00
|
|
|
|
2017-01-09 16:55:25 +01:00
|
|
|
|
|
|
|
|
|
2018-01-26 09:28:48 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-01-09 16:55:25 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-01-26 09:28:48 +01:00
|
|
|
|
2017-01-09 16:55:25 +01:00
|
|
|
|
|
|
|
|
|
2018-01-26 09:28:48 +01:00
|
|
|
|
2017-01-09 16:55:25 +01:00
|
|
|
|
2018-01-26 09:28:48 +01:00
|
|
|
|
2017-01-09 16:55:25 +01:00
|
|
|
|
2018-01-26 09:28:48 +01:00
|
|
|
|
2017-01-09 16:55:25 +01:00
|
|
|
|
2018-01-26 09:28:48 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-01-09 16:55:25 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-01-25 11:15:35 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-01-09 16:55:25 +01:00
|
|
|
|
2017-04-10 14:58:01 +02:00
|
|
|
|
2017-01-09 16:55:25 +01:00
|
|
|
|
2017-04-10 14:58:01 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-04-11 11:17:30 +02:00
|
|
|
|
2017-01-09 16:55:25 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-01-24 10:28:12 +01:00
|
|
|
|
2017-01-09 16:55:25 +01:00
|
|
|
|
|
|
|
|
|
2018-01-24 10:28:12 +01:00
|
|
|
|
2017-01-09 16:55:25 +01:00
|
|
|
|
2018-01-25 11:15:35 +01:00
|
|
|
|
2017-01-09 16:55:25 +01:00
|
|
|
|
2021-11-23 16:25:16 +08:00
|
|
|
|
2018-01-25 11:15:31 +01:00
|
|
|
|
2021-11-23 16:25:16 +08:00
|
|
|
|
2017-01-09 16:55:25 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-02-04 13:44:47 +01:00
|
|
|
|
2017-01-09 16:55:25 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-01-26 09:28:48 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-01-09 16:55:25 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-08-23 17:36:59 -05:00
|
|
|
|
2017-10-21 20:35:30 -05:00
|
|
|
|
2017-01-09 16:55:25 +01:00
|
|
|
|
2018-01-24 10:28:12 +01:00
|
|
|
|
2017-01-09 16:55:25 +01:00
|
|
|
|
|
|
|
|
|
2017-04-10 14:58:02 +02:00
|
|
|
|
2017-01-09 16:55:25 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-01-26 09:28:48 +01:00
|
|
|
|
2017-01-09 16:55:25 +01:00
|
|
|
|
2018-01-25 11:15:32 +01:00
|
|
|
|
2018-01-26 09:28:48 +01:00
|
|
|
|
2018-01-25 11:15:32 +01:00
|
|
|
|
2018-01-26 09:28:48 +01:00
|
|
|
|
|
|
|
|
|
2018-01-25 11:15:32 +01:00
|
|
|
|
2017-01-09 16:55:25 +01:00
|
|
|
|
|
|
|
|
|
2018-01-26 09:28:48 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-01-09 16:55:25 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-04-10 14:58:02 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-02-07 15:56:15 +01:00
|
|
|
|
2018-01-24 10:28:12 +01:00
|
|
|
|
2019-04-11 11:17:30 +02:00
|
|
|
|
|
|
|
|
|
2019-02-07 15:56:15 +01:00
|
|
|
|
2017-01-09 16:55:25 +01:00
|
|
|
|
2018-01-24 10:28:12 +01:00
|
|
|
|
2019-04-11 11:17:30 +02:00
|
|
|
|
|
|
|
|
|
2018-01-26 09:28:48 +01:00
|
|
|
|
2017-01-09 16:55:25 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-09-21 09:16:34 +02:00
|
|
|
|
2017-01-09 16:55:25 +01:00
|
|
|
|
|
|
|
|
|
2017-09-21 09:16:34 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-01-09 16:55:25 +01:00
|
|
|
|
|
|
|
|
|
2018-01-24 10:28:16 +01:00
|
|
|
|
|
|
|
|
|
2017-01-09 16:55:25 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-09-21 09:16:33 +02:00
|
|
|
|
2017-01-09 16:55:25 +01:00
|
|
|
|
2018-01-24 10:28:16 +01:00
|
|
|
|
|
|
|
|
|
2017-01-09 16:55:25 +01:00
|
|
|
|
|
|
|
|
|
2018-01-24 10:28:16 +01:00
|
|
|
|
2017-01-09 16:55:25 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-09-21 09:16:33 +02:00
|
|
|
|
2017-01-09 16:55:25 +01:00
|
|
|
|
2018-01-24 10:28:16 +01:00
|
|
|
|
|
|
|
|
|
2017-01-09 16:55:25 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-01-24 10:28:12 +01:00
|
|
|
|
2017-01-09 16:55:25 +01:00
|
|
|
|
|
|
|
|
|
2017-04-10 14:58:01 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|