2008-07-30 12:06:12 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-01-26 01:39:48 -08:00
|
|
|
|
2025-06-12 14:10:00 +02:00
|
|
|
|
2022-01-26 01:39:48 -08:00
|
|
|
|
|
|
|
|
|
2025-12-05 19:22:25 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-02-04 09:05:41 -08:00
|
|
|
|
2017-07-17 16:10:26 -05:00
|
|
|
|
2022-01-26 01:39:48 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-02-25 18:44:27 -05:00
|
|
|
|
2025-12-05 19:22:24 +01:00
|
|
|
|
2022-01-26 01:39:48 -08:00
|
|
|
|
|
|
|
|
|
2022-01-26 01:39:49 -08:00
|
|
|
|
2022-01-26 01:39:48 -08:00
|
|
|
|
|
|
|
|
|
2019-05-26 19:35:35 +02:00
|
|
|
|
2019-07-18 18:15:02 +02:00
|
|
|
|
2019-05-26 19:35:35 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-09-23 15:46:53 +02:00
|
|
|
|
2020-03-23 15:49:22 +01:00
|
|
|
|
2017-11-07 20:13:40 +01:00
|
|
|
|
2019-05-26 19:35:35 +02:00
|
|
|
|
|
|
|
|
|
2014-09-10 12:43:53 +02:00
|
|
|
|
2008-07-30 12:06:12 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-12-05 19:22:25 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-03-23 15:49:22 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-07-30 12:06:12 -07:00
|
|
|
|
2014-01-21 12:39:00 +01:00
|
|
|
|
|
|
|
|
|
2008-07-30 12:06:12 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-12-11 14:24:46 +01:00
|
|
|
|
2008-11-05 10:31:53 -08:00
|
|
|
|
2013-08-15 00:02:44 +02:00
|
|
|
|
2018-02-12 14:55:33 +00:00
|
|
|
|
2008-11-05 10:31:53 -08:00
|
|
|
|
2020-03-23 15:49:22 +01:00
|
|
|
|
|
|
|
|
|
2025-09-02 23:40:20 +05:30
|
|
|
|
2008-11-05 10:31:53 -08:00
|
|
|
|
|
|
|
|
|
2013-12-11 14:24:46 +01:00
|
|
|
|
|
|
|
|
|
2013-07-24 21:07:52 +02:00
|
|
|
|
|
|
|
|
|
2008-11-05 10:31:53 -08:00
|
|
|
|
2020-03-23 15:49:22 +01:00
|
|
|
|
2008-11-05 10:31:53 -08:00
|
|
|
|
|
|
|
|
|
2024-09-23 10:55:08 -03:00
|
|
|
|
2025-12-05 19:22:28 +01:00
|
|
|
|
2024-09-23 10:55:08 -03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-12-05 19:22:28 +01:00
|
|
|
|
|
|
|
|
|
2024-09-23 10:55:08 -03:00
|
|
|
|
2025-12-05 19:22:28 +01:00
|
|
|
|
|
|
|
|
|
2024-09-23 10:55:08 -03:00
|
|
|
|
2025-12-05 19:22:28 +01:00
|
|
|
|
2024-09-23 10:55:08 -03:00
|
|
|
|
2026-01-22 16:06:17 +00:00
|
|
|
|
2024-09-23 10:55:08 -03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-12-05 19:22:28 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-02-18 20:50:32 -08:00
|
|
|
|
2024-09-23 10:55:08 -03:00
|
|
|
|
2026-01-22 16:06:17 +00:00
|
|
|
|
2024-09-23 10:55:08 -03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-04-09 19:05:04 +00:00
|
|
|
|
|
|
|
|
|
2011-06-07 14:17:51 +01:00
|
|
|
|
2014-08-28 14:34:36 +02:00
|
|
|
|
2014-01-21 12:39:00 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-06-07 14:17:51 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-07-11 11:56:32 +02:00
|
|
|
|
|
|
|
|
|
2011-06-07 14:17:51 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-08-15 00:02:37 +02:00
|
|
|
|
2011-06-07 14:17:51 +01:00
|
|
|
|
drm_gem: add mutex to drm_gem_object.gpuva
There are two main ways that GPUVM might be used:
* staged mode, where VM_BIND ioctls update the GPUVM immediately so that
the GPUVM reflects the state of the VM *including* staged changes that
are not yet applied to the GPU's virtual address space.
* immediate mode, where the GPUVM state is updated during run_job(),
i.e., in the DMA fence signalling critical path, to ensure that the
GPUVM and the GPU's virtual address space has the same state at all
times.
Currently, only Panthor uses GPUVM in immediate mode, but the Rust
drivers Tyr and Nova will also use GPUVM in immediate mode, so it is
worth to support both staged and immediate mode well in GPUVM. To use
immediate mode, the GEMs gpuva list must be modified during the fence
signalling path, which means that it must be protected by a lock that is
fence signalling safe.
For this reason, a mutex is added to struct drm_gem_object that is
intended to achieve this purpose. Adding it directly in the GEM object
both makes it easier to use GPUVM in immediate mode, but also makes it
possible to take the gpuva lock from core drm code.
As a follow-up, another change that should probably be made to support
immediate mode is a mechanism to postpone cleanup of vm_bo objects, as
dropping a vm_bo object in the fence signalling path is problematic for
two reasons:
* When using DRM_GPUVM_RESV_PROTECTED, you cannot remove the vm_bo from
the extobj/evicted lists during the fence signalling path.
* Dropping a vm_bo could lead to the GEM object getting destroyed.
The requirement that GEM object cleanup is fence signalling safe is
dubious and likely to be violated in practice.
Panthor already has its own custom implementation of postponing vm_bo
cleanup.
Reviewed-by: Boris Brezillon <boris.brezillon@collabora.com>
Signed-off-by: Alice Ryhl <aliceryhl@google.com>
Link: https://lore.kernel.org/r/20250827-gpuva-mutex-in-gem-v3-1-bd89f5a82c0d@google.com
Signed-off-by: Danilo Krummrich <dakr@kernel.org>
2025-08-27 13:38:37 +00:00
|
|
|
|
2019-08-11 10:06:32 +02:00
|
|
|
|
2019-02-02 09:41:54 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-07-20 02:14:22 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-08-25 18:28:57 +02:00
|
|
|
|
2022-08-02 08:51:42 -07:00
|
|
|
|
2011-06-07 14:17:51 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-11-19 14:41:31 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
drm_gem: add mutex to drm_gem_object.gpuva
There are two main ways that GPUVM might be used:
* staged mode, where VM_BIND ioctls update the GPUVM immediately so that
the GPUVM reflects the state of the VM *including* staged changes that
are not yet applied to the GPU's virtual address space.
* immediate mode, where the GPUVM state is updated during run_job(),
i.e., in the DMA fence signalling critical path, to ensure that the
GPUVM and the GPU's virtual address space has the same state at all
times.
Currently, only Panthor uses GPUVM in immediate mode, but the Rust
drivers Tyr and Nova will also use GPUVM in immediate mode, so it is
worth to support both staged and immediate mode well in GPUVM. To use
immediate mode, the GEMs gpuva list must be modified during the fence
signalling path, which means that it must be protected by a lock that is
fence signalling safe.
For this reason, a mutex is added to struct drm_gem_object that is
intended to achieve this purpose. Adding it directly in the GEM object
both makes it easier to use GPUVM in immediate mode, but also makes it
possible to take the gpuva lock from core drm code.
As a follow-up, another change that should probably be made to support
immediate mode is a mechanism to postpone cleanup of vm_bo objects, as
dropping a vm_bo object in the fence signalling path is problematic for
two reasons:
* When using DRM_GPUVM_RESV_PROTECTED, you cannot remove the vm_bo from
the extobj/evicted lists during the fence signalling path.
* Dropping a vm_bo could lead to the GEM object getting destroyed.
The requirement that GEM object cleanup is fence signalling safe is
dubious and likely to be violated in practice.
Panthor already has its own custom implementation of postponing vm_bo
cleanup.
Reviewed-by: Boris Brezillon <boris.brezillon@collabora.com>
Signed-off-by: Alice Ryhl <aliceryhl@google.com>
Link: https://lore.kernel.org/r/20250827-gpuva-mutex-in-gem-v3-1-bd89f5a82c0d@google.com
Signed-off-by: Danilo Krummrich <dakr@kernel.org>
2025-08-27 13:38:37 +00:00
|
|
|
|
2022-11-19 14:41:31 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-06-30 10:36:47 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-07-07 15:11:55 +02:00
|
|
|
|
2025-06-30 10:36:47 +02:00
|
|
|
|
|
|
|
|
|
2025-07-07 15:11:55 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-06-30 10:36:47 +02:00
|
|
|
|
2025-07-07 15:11:55 +02:00
|
|
|
|
2025-06-30 10:36:47 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-07-07 15:11:55 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-06-30 10:36:47 +02:00
|
|
|
|
2025-07-07 15:11:55 +02:00
|
|
|
|
|
|
|
|
|
2025-06-30 10:36:47 +02:00
|
|
|
|
|
|
|
|
|
2013-08-15 00:02:34 +02:00
|
|
|
|
2014-10-02 14:45:55 +02:00
|
|
|
|
2014-01-21 12:39:00 +01:00
|
|
|
|
|
|
|
|
|
2013-08-15 00:02:34 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-08-15 00:02:37 +02:00
|
|
|
|
2013-08-15 00:02:34 +02:00
|
|
|
|
|
|
|
|
|
2013-08-15 00:02:46 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-06-30 10:36:47 +02:00
|
|
|
|
2025-07-07 15:11:55 +02:00
|
|
|
|
2025-06-30 10:36:47 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-08-15 00:02:34 +02:00
|
|
|
|
2016-01-04 10:11:00 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-07-07 15:11:55 +02:00
|
|
|
|
2013-08-15 00:02:34 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-07-07 15:11:55 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-08-15 00:02:34 +02:00
|
|
|
|
2016-01-04 10:11:00 +00:00
|
|
|
|
2013-08-15 00:02:46 +02:00
|
|
|
|
2013-08-15 00:02:34 +02:00
|
|
|
|
2013-08-15 00:02:46 +02:00
|
|
|
|
2016-01-04 10:11:00 +00:00
|
|
|
|
2013-08-15 00:02:46 +02:00
|
|
|
|
2016-01-04 10:11:00 +00:00
|
|
|
|
2013-08-15 00:02:37 +02:00
|
|
|
|
2016-01-04 10:11:00 +00:00
|
|
|
|
2020-05-15 10:50:53 +01:00
|
|
|
|
2013-08-15 00:02:34 +02:00
|
|
|
|
|
|
|
|
|
2016-01-05 09:42:31 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
drm/gem: Fix race in drm_gem_handle_create_tail()
Object creation is a careful dance where we must guarantee that the
object is fully constructed before it is visible to other threads, and
GEM buffer objects are no difference.
Final publishing happens by calling drm_gem_handle_create(). After
that the only allowed thing to do is call drm_gem_object_put() because
a concurrent call to the GEM_CLOSE ioctl with a correctly guessed id
(which is trivial since we have a linear allocator) can already tear
down the object again.
Luckily most drivers get this right, the very few exceptions I've
pinged the relevant maintainers for. Unfortunately we also need
drm_gem_handle_create() when creating additional handles for an
already existing object (e.g. GETFB ioctl or the various bo import
ioctl), and hence we cannot have a drm_gem_handle_create_and_put() as
the only exported function to stop these issues from happening.
Now unfortunately the implementation of drm_gem_handle_create() isn't
living up to standards: It does correctly finishe object
initialization at the global level, and hence is safe against a
concurrent tear down. But it also sets up the file-private aspects of
the handle, and that part goes wrong: We fully register the object in
the drm_file.object_idr before calling drm_vma_node_allow() or
obj->funcs->open, which opens up races against concurrent removal of
that handle in drm_gem_handle_delete().
Fix this with the usual two-stage approach of first reserving the
handle id, and then only registering the object after we've completed
the file-private setup.
Jacek reported this with a testcase of concurrently calling GEM_CLOSE
on a freshly-created object (which also destroys the object), but it
should be possible to hit this with just additional handles created
through import or GETFB without completed destroying the underlying
object with the concurrent GEM_CLOSE ioctl calls.
Note that the close-side of this race was fixed in f6cd7daecff5 ("drm:
Release driver references to handle before making it available
again"), which means a cool 9 years have passed until someone noticed
that we need to make this symmetry or there's still gaps left :-/
Without the 2-stage close approach we'd still have a race, therefore
that's an integral part of this bugfix.
More importantly, this means we can have NULL pointers behind
allocated id in our drm_file.object_idr. We need to check for that
now:
- drm_gem_handle_delete() checks for ERR_OR_NULL already
- drm_gem.c:object_lookup() also chekcs for NULL
- drm_gem_release() should never be called if there's another thread
still existing that could call into an IOCTL that creates a new
handle, so cannot race. For paranoia I added a NULL check to
drm_gem_object_release_handle() though.
- most drivers (etnaviv, i915, msm) are find because they use
idr_find(), which maps both ENOENT and NULL to NULL.
- drivers using idr_for_each_entry() should also be fine, because
idr_get_next does filter out NULL entries and continues the
iteration.
- The same holds for drm_show_memory_stats().
v2: Use drm_WARN_ON (Thomas)
Reported-by: Jacek Lawrynowicz <jacek.lawrynowicz@linux.intel.com>
Tested-by: Jacek Lawrynowicz <jacek.lawrynowicz@linux.intel.com>
Reviewed-by: Thomas Zimmermann <tzimmermann@suse.de>
Cc: stable@vger.kernel.org
Cc: Jacek Lawrynowicz <jacek.lawrynowicz@linux.intel.com>
Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Cc: Maxime Ripard <mripard@kernel.org>
Cc: Thomas Zimmermann <tzimmermann@suse.de>
Cc: David Airlie <airlied@gmail.com>
Cc: Simona Vetter <simona@ffwll.ch>
Signed-off-by: Simona Vetter <simona.vetter@intel.com>
Signed-off-by: Simona Vetter <simona.vetter@ffwll.ch>
Link: https://patchwork.freedesktop.org/patch/msgid/20250707151814.603897-1-simona.vetter@ffwll.ch
2025-07-07 17:18:13 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-09-23 12:21:59 +02:00
|
|
|
|
2018-11-10 15:56:45 +01:00
|
|
|
|
2017-08-19 13:05:58 +01:00
|
|
|
|
2025-07-17 10:35:55 -04:00
|
|
|
|
|
|
|
|
|
2025-06-13 15:50:41 +02:00
|
|
|
|
2025-07-17 10:35:55 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-09-01 14:48:33 +02:00
|
|
|
|
2016-01-05 09:42:31 +00:00
|
|
|
|
2017-02-28 15:46:41 +01:00
|
|
|
|
2016-01-05 09:42:31 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-07-30 12:06:12 -07:00
|
|
|
|
2014-01-21 12:39:00 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-10-22 19:11:29 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-07-30 12:06:12 -07:00
|
|
|
|
2011-02-07 12:16:14 +10:00
|
|
|
|
2009-08-23 12:40:55 +03:00
|
|
|
|
2008-07-30 12:06:12 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
drm: Release driver references to handle before making it available again
When userspace closes a handle, we remove it from the file->object_idr
and then tell the driver to drop its references to that file/handle.
However, as the file/handle is already available again for reuse, it may
be reallocated back to userspace and active on a new object before the
driver has had a chance to drop the old file/handle references.
Whilst calling back into the driver, we have to drop the
file->table_lock spinlock and so to prevent reusing the closed handle we
mark that handle as stale in the idr, perform the callback and then
remove the handle. We set the stale handle to point to the NULL object,
then any idr_find() whilst the driver is removing the handle will return
NULL, just as if the handle is already removed from idr.
Note: This will be used to have a direct handle -> vma lookup table,
instead of first a handle -> obj lookup, and then an (obj, vm) -> vma
lookup.
v2: Use NULL rather than an ERR_PTR to avoid having to adjust callers.
idr_alloc() tracks existing handles using an internal bitmap, so we are
free to use the NULL object as our stale identifier.
v3: Needed to update the return value check after changing from using
the stale error pointer to NULL.
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Cc: dri-devel@lists.freedesktop.org
Cc: David Airlie <airlied@linux.ie>
Cc: Daniel Vetter <daniel.vetter@intel.com>
Cc: Rob Clark <robdclark@gmail.com>
Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
Cc: Thierry Reding <treding@nvidia.com>
[danvet: Add note about the use-case.]
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Link: http://patchwork.freedesktop.org/patch/msgid/1460721308-32405-1-git-send-email-chris@chris-wilson.co.uk
2016-04-15 12:55:08 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-07-30 12:06:12 -07:00
|
|
|
|
|
|
|
|
|
drm: Release driver references to handle before making it available again
When userspace closes a handle, we remove it from the file->object_idr
and then tell the driver to drop its references to that file/handle.
However, as the file/handle is already available again for reuse, it may
be reallocated back to userspace and active on a new object before the
driver has had a chance to drop the old file/handle references.
Whilst calling back into the driver, we have to drop the
file->table_lock spinlock and so to prevent reusing the closed handle we
mark that handle as stale in the idr, perform the callback and then
remove the handle. We set the stale handle to point to the NULL object,
then any idr_find() whilst the driver is removing the handle will return
NULL, just as if the handle is already removed from idr.
Note: This will be used to have a direct handle -> vma lookup table,
instead of first a handle -> obj lookup, and then an (obj, vm) -> vma
lookup.
v2: Use NULL rather than an ERR_PTR to avoid having to adjust callers.
idr_alloc() tracks existing handles using an internal bitmap, so we are
free to use the NULL object as our stale identifier.
v3: Needed to update the return value check after changing from using
the stale error pointer to NULL.
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Cc: dri-devel@lists.freedesktop.org
Cc: David Airlie <airlied@linux.ie>
Cc: Daniel Vetter <daniel.vetter@intel.com>
Cc: Rob Clark <robdclark@gmail.com>
Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
Cc: Thierry Reding <treding@nvidia.com>
[danvet: Add note about the use-case.]
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Link: http://patchwork.freedesktop.org/patch/msgid/1460721308-32405-1-git-send-email-chris@chris-wilson.co.uk
2016-04-15 12:55:08 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-07-30 12:06:12 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-02-07 12:16:14 +10:00
|
|
|
|
2008-07-30 12:06:12 -07:00
|
|
|
|
2017-07-23 21:16:17 +02:00
|
|
|
|
2019-08-07 10:52:47 -04:00
|
|
|
|
2017-07-23 21:16:17 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-08-07 10:52:47 -04:00
|
|
|
|
2017-07-23 21:16:17 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-08-17 18:21:30 +02:00
|
|
|
|
2025-02-26 18:03:04 +01:00
|
|
|
|
2017-08-17 18:21:30 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-07-23 21:16:17 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-05-15 10:50:53 +01:00
|
|
|
|
2017-07-23 21:16:17 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-08-07 10:52:47 -04:00
|
|
|
|
2017-07-23 21:16:17 +02:00
|
|
|
|
2008-07-30 12:06:12 -07:00
|
|
|
|
2013-08-15 00:02:45 +02:00
|
|
|
|
2014-01-21 12:39:00 +01:00
|
|
|
|
|
|
|
|
|
2014-11-03 13:20:52 +01:00
|
|
|
|
2017-10-26 18:57:26 +02:00
|
|
|
|
2017-01-25 07:26:46 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-10-22 19:11:29 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-07-30 12:06:12 -07:00
|
|
|
|
|
|
|
|
|
2013-08-15 00:02:45 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-07-30 12:06:12 -07:00
|
|
|
|
2011-06-09 00:24:59 +00:00
|
|
|
|
2016-01-05 09:42:30 +00:00
|
|
|
|
2011-06-09 00:24:59 +00:00
|
|
|
|
2008-07-30 12:06:12 -07:00
|
|
|
|
2013-08-15 00:02:45 +02:00
|
|
|
|
2025-06-30 10:36:47 +02:00
|
|
|
|
|
|
|
|
|
2013-08-15 00:02:45 +02:00
|
|
|
|
2008-07-30 12:06:12 -07:00
|
|
|
|
2013-02-27 17:04:08 -08:00
|
|
|
|
|
|
|
|
|
2008-07-30 12:06:12 -07:00
|
|
|
|
2013-02-27 17:04:08 -08:00
|
|
|
|
2008-07-30 12:06:12 -07:00
|
|
|
|
2013-02-27 17:04:08 -08:00
|
|
|
|
drm/gem: Fix race in drm_gem_handle_create_tail()
Object creation is a careful dance where we must guarantee that the
object is fully constructed before it is visible to other threads, and
GEM buffer objects are no difference.
Final publishing happens by calling drm_gem_handle_create(). After
that the only allowed thing to do is call drm_gem_object_put() because
a concurrent call to the GEM_CLOSE ioctl with a correctly guessed id
(which is trivial since we have a linear allocator) can already tear
down the object again.
Luckily most drivers get this right, the very few exceptions I've
pinged the relevant maintainers for. Unfortunately we also need
drm_gem_handle_create() when creating additional handles for an
already existing object (e.g. GETFB ioctl or the various bo import
ioctl), and hence we cannot have a drm_gem_handle_create_and_put() as
the only exported function to stop these issues from happening.
Now unfortunately the implementation of drm_gem_handle_create() isn't
living up to standards: It does correctly finishe object
initialization at the global level, and hence is safe against a
concurrent tear down. But it also sets up the file-private aspects of
the handle, and that part goes wrong: We fully register the object in
the drm_file.object_idr before calling drm_vma_node_allow() or
obj->funcs->open, which opens up races against concurrent removal of
that handle in drm_gem_handle_delete().
Fix this with the usual two-stage approach of first reserving the
handle id, and then only registering the object after we've completed
the file-private setup.
Jacek reported this with a testcase of concurrently calling GEM_CLOSE
on a freshly-created object (which also destroys the object), but it
should be possible to hit this with just additional handles created
through import or GETFB without completed destroying the underlying
object with the concurrent GEM_CLOSE ioctl calls.
Note that the close-side of this race was fixed in f6cd7daecff5 ("drm:
Release driver references to handle before making it available
again"), which means a cool 9 years have passed until someone noticed
that we need to make this symmetry or there's still gaps left :-/
Without the 2-stage close approach we'd still have a race, therefore
that's an integral part of this bugfix.
More importantly, this means we can have NULL pointers behind
allocated id in our drm_file.object_idr. We need to check for that
now:
- drm_gem_handle_delete() checks for ERR_OR_NULL already
- drm_gem.c:object_lookup() also chekcs for NULL
- drm_gem_release() should never be called if there's another thread
still existing that could call into an IOCTL that creates a new
handle, so cannot race. For paranoia I added a NULL check to
drm_gem_object_release_handle() though.
- most drivers (etnaviv, i915, msm) are find because they use
idr_find(), which maps both ENOENT and NULL to NULL.
- drivers using idr_for_each_entry() should also be fine, because
idr_get_next does filter out NULL entries and continues the
iteration.
- The same holds for drm_show_memory_stats().
v2: Use drm_WARN_ON (Thomas)
Reported-by: Jacek Lawrynowicz <jacek.lawrynowicz@linux.intel.com>
Tested-by: Jacek Lawrynowicz <jacek.lawrynowicz@linux.intel.com>
Reviewed-by: Thomas Zimmermann <tzimmermann@suse.de>
Cc: stable@vger.kernel.org
Cc: Jacek Lawrynowicz <jacek.lawrynowicz@linux.intel.com>
Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Cc: Maxime Ripard <mripard@kernel.org>
Cc: Thomas Zimmermann <tzimmermann@suse.de>
Cc: David Airlie <airlied@gmail.com>
Cc: Simona Vetter <simona@ffwll.ch>
Signed-off-by: Simona Vetter <simona.vetter@intel.com>
Signed-off-by: Simona Vetter <simona.vetter@ffwll.ch>
Link: https://patchwork.freedesktop.org/patch/msgid/20250707151814.603897-1-simona.vetter@ffwll.ch
2025-07-07 17:18:13 +02:00
|
|
|
|
2016-01-04 10:11:00 +00:00
|
|
|
|
2008-07-30 12:06:12 -07:00
|
|
|
|
2013-02-27 17:04:08 -08:00
|
|
|
|
2016-01-04 10:11:00 +00:00
|
|
|
|
2013-08-15 00:02:44 +02:00
|
|
|
|
2016-01-04 10:10:59 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-01-05 09:42:30 +00:00
|
|
|
|
2008-07-30 12:06:12 -07:00
|
|
|
|
2016-09-01 14:48:33 +02:00
|
|
|
|
2016-01-04 10:10:59 +00:00
|
|
|
|
|
|
|
|
|
2011-06-09 00:24:59 +00:00
|
|
|
|
2020-09-23 12:21:59 +02:00
|
|
|
|
2018-11-10 15:56:45 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-06-09 00:24:59 +00:00
|
|
|
|
|
|
|
|
|
drm/gem: Fix race in drm_gem_handle_create_tail()
Object creation is a careful dance where we must guarantee that the
object is fully constructed before it is visible to other threads, and
GEM buffer objects are no difference.
Final publishing happens by calling drm_gem_handle_create(). After
that the only allowed thing to do is call drm_gem_object_put() because
a concurrent call to the GEM_CLOSE ioctl with a correctly guessed id
(which is trivial since we have a linear allocator) can already tear
down the object again.
Luckily most drivers get this right, the very few exceptions I've
pinged the relevant maintainers for. Unfortunately we also need
drm_gem_handle_create() when creating additional handles for an
already existing object (e.g. GETFB ioctl or the various bo import
ioctl), and hence we cannot have a drm_gem_handle_create_and_put() as
the only exported function to stop these issues from happening.
Now unfortunately the implementation of drm_gem_handle_create() isn't
living up to standards: It does correctly finishe object
initialization at the global level, and hence is safe against a
concurrent tear down. But it also sets up the file-private aspects of
the handle, and that part goes wrong: We fully register the object in
the drm_file.object_idr before calling drm_vma_node_allow() or
obj->funcs->open, which opens up races against concurrent removal of
that handle in drm_gem_handle_delete().
Fix this with the usual two-stage approach of first reserving the
handle id, and then only registering the object after we've completed
the file-private setup.
Jacek reported this with a testcase of concurrently calling GEM_CLOSE
on a freshly-created object (which also destroys the object), but it
should be possible to hit this with just additional handles created
through import or GETFB without completed destroying the underlying
object with the concurrent GEM_CLOSE ioctl calls.
Note that the close-side of this race was fixed in f6cd7daecff5 ("drm:
Release driver references to handle before making it available
again"), which means a cool 9 years have passed until someone noticed
that we need to make this symmetry or there's still gaps left :-/
Without the 2-stage close approach we'd still have a race, therefore
that's an integral part of this bugfix.
More importantly, this means we can have NULL pointers behind
allocated id in our drm_file.object_idr. We need to check for that
now:
- drm_gem_handle_delete() checks for ERR_OR_NULL already
- drm_gem.c:object_lookup() also chekcs for NULL
- drm_gem_release() should never be called if there's another thread
still existing that could call into an IOCTL that creates a new
handle, so cannot race. For paranoia I added a NULL check to
drm_gem_object_release_handle() though.
- most drivers (etnaviv, i915, msm) are find because they use
idr_find(), which maps both ENOENT and NULL to NULL.
- drivers using idr_for_each_entry() should also be fine, because
idr_get_next does filter out NULL entries and continues the
iteration.
- The same holds for drm_show_memory_stats().
v2: Use drm_WARN_ON (Thomas)
Reported-by: Jacek Lawrynowicz <jacek.lawrynowicz@linux.intel.com>
Tested-by: Jacek Lawrynowicz <jacek.lawrynowicz@linux.intel.com>
Reviewed-by: Thomas Zimmermann <tzimmermann@suse.de>
Cc: stable@vger.kernel.org
Cc: Jacek Lawrynowicz <jacek.lawrynowicz@linux.intel.com>
Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Cc: Maxime Ripard <mripard@kernel.org>
Cc: Thomas Zimmermann <tzimmermann@suse.de>
Cc: David Airlie <airlied@gmail.com>
Cc: Simona Vetter <simona@ffwll.ch>
Signed-off-by: Simona Vetter <simona.vetter@intel.com>
Signed-off-by: Simona Vetter <simona.vetter@ffwll.ch>
Link: https://patchwork.freedesktop.org/patch/msgid/20250707151814.603897-1-simona.vetter@ffwll.ch
2025-07-07 17:18:13 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-01-05 09:42:30 +00:00
|
|
|
|
2008-07-30 12:06:12 -07:00
|
|
|
|
2016-01-04 10:10:59 +00:00
|
|
|
|
|
|
|
|
|
2016-09-01 14:48:33 +02:00
|
|
|
|
2016-01-04 10:10:59 +00:00
|
|
|
|
|
|
|
|
|
2016-01-05 09:42:30 +00:00
|
|
|
|
2016-01-04 10:10:59 +00:00
|
|
|
|
|
|
|
|
|
2017-02-28 15:46:41 +01:00
|
|
|
|
2016-01-04 10:10:59 +00:00
|
|
|
|
2008-07-30 12:06:12 -07:00
|
|
|
|
2013-08-15 00:02:45 +02:00
|
|
|
|
|
|
|
|
|
2014-11-03 13:20:52 +01:00
|
|
|
|
2014-01-21 12:39:00 +01:00
|
|
|
|
|
|
|
|
|
2020-03-17 18:03:39 -03:00
|
|
|
|
2014-01-21 12:39:00 +01:00
|
|
|
|
2018-03-22 09:02:33 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-08-15 00:02:45 +02:00
|
|
|
|
2014-11-03 13:20:52 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-08-15 00:02:45 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-07-30 12:06:12 -07:00
|
|
|
|
|
|
|
|
|
2011-08-10 08:09:07 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-03-30 11:40:52 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-08-10 08:09:07 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-12-11 14:24:46 +01:00
|
|
|
|
2011-08-10 08:09:07 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-08-07 13:41:23 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-01-25 07:26:46 +01:00
|
|
|
|
|
|
|
|
|
2016-03-30 11:40:52 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-08-07 13:41:23 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-12-11 14:24:46 +01:00
|
|
|
|
2013-08-07 13:41:23 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-08-10 08:09:07 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-03-30 11:40:52 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-08-10 08:09:07 -05:00
|
|
|
|
2013-08-07 13:41:23 -04:00
|
|
|
|
2011-08-10 08:09:07 -05:00
|
|
|
|
2013-08-07 13:41:23 -04:00
|
|
|
|
2011-08-10 08:09:07 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-01-08 15:45:17 +08:00
|
|
|
|
2023-06-21 17:45:49 +01:00
|
|
|
|
|
|
|
|
|
2019-01-08 15:45:17 +08:00
|
|
|
|
2023-06-21 17:45:49 +01:00
|
|
|
|
2019-01-08 15:45:17 +08:00
|
|
|
|
2023-06-21 17:45:49 +01:00
|
|
|
|
|
|
|
|
|
2019-01-08 15:45:17 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-08-07 13:41:24 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
drm/gem: remove misleading gfp parameter to get_pages()
drm_gem_get_pages() currently allows passing a 'gfp' parameter that is
passed to shmem combined with mapping_gfp_mask(). Given that the default
mapping_gfp_mask() is GFP_HIGHUSER, it is _very_ unlikely that anyone will
ever make use of that parameter. In fact, all drivers currently pass
redundant flags or 0.
This patch removes the 'gfp' parameter. The only reason to keep it is to
remove flags like __GFP_WAIT. But in its current form, it can only be used
to add flags. So to remove __GFP_WAIT, you'd have to drop it from the
mapping_gfp_mask, which again is stupid as this mask is used by shmem-core
for other allocations, too.
If any driver ever requires that parameter, we can introduce a new helper
that takes the raw 'gfp' parameter. The caller'd be responsible to combine
it with mapping_gfp_mask() in a suitable way. The current
drm_gem_get_pages() helper would then simply use mapping_gfp_mask() and
call the new helper. This is what shmem_read_mapping_pages{_gfp,} does
right now.
Moreover, the gfp-zone flag-usage is not obvious: If you pass a modified
zone, shmem core will WARN() or even BUG(). In other words, the following
must be true for 'gfp' passed to shmem_read_mapping_pages_gfp():
gfp_zone(mapping_gfp_mask(mapping)) == gfp_zone(gfp)
Add a comment to drm_gem_read_pages() explaining that constraint.
Signed-off-by: David Herrmann <dh.herrmann@gmail.com>
2014-05-25 12:59:47 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-10-03 09:38:10 -06:00
|
|
|
|
drm/gem: remove misleading gfp parameter to get_pages()
drm_gem_get_pages() currently allows passing a 'gfp' parameter that is
passed to shmem combined with mapping_gfp_mask(). Given that the default
mapping_gfp_mask() is GFP_HIGHUSER, it is _very_ unlikely that anyone will
ever make use of that parameter. In fact, all drivers currently pass
redundant flags or 0.
This patch removes the 'gfp' parameter. The only reason to keep it is to
remove flags like __GFP_WAIT. But in its current form, it can only be used
to add flags. So to remove __GFP_WAIT, you'd have to drop it from the
mapping_gfp_mask, which again is stupid as this mask is used by shmem-core
for other allocations, too.
If any driver ever requires that parameter, we can introduce a new helper
that takes the raw 'gfp' parameter. The caller'd be responsible to combine
it with mapping_gfp_mask() in a suitable way. The current
drm_gem_get_pages() helper would then simply use mapping_gfp_mask() and
call the new helper. This is what shmem_read_mapping_pages{_gfp,} does
right now.
Moreover, the gfp-zone flag-usage is not obvious: If you pass a modified
zone, shmem core will WARN() or even BUG(). In other words, the following
must be true for 'gfp' passed to shmem_read_mapping_pages_gfp():
gfp_zone(mapping_gfp_mask(mapping)) == gfp_zone(gfp)
Add a comment to drm_gem_read_pages() explaining that constraint.
Signed-off-by: David Herrmann <dh.herrmann@gmail.com>
2014-05-25 12:59:47 +02:00
|
|
|
|
2020-05-11 11:35:47 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-08-07 13:41:24 -04:00
|
|
|
|
drm/gem: remove misleading gfp parameter to get_pages()
drm_gem_get_pages() currently allows passing a 'gfp' parameter that is
passed to shmem combined with mapping_gfp_mask(). Given that the default
mapping_gfp_mask() is GFP_HIGHUSER, it is _very_ unlikely that anyone will
ever make use of that parameter. In fact, all drivers currently pass
redundant flags or 0.
This patch removes the 'gfp' parameter. The only reason to keep it is to
remove flags like __GFP_WAIT. But in its current form, it can only be used
to add flags. So to remove __GFP_WAIT, you'd have to drop it from the
mapping_gfp_mask, which again is stupid as this mask is used by shmem-core
for other allocations, too.
If any driver ever requires that parameter, we can introduce a new helper
that takes the raw 'gfp' parameter. The caller'd be responsible to combine
it with mapping_gfp_mask() in a suitable way. The current
drm_gem_get_pages() helper would then simply use mapping_gfp_mask() and
call the new helper. This is what shmem_read_mapping_pages{_gfp,} does
right now.
Moreover, the gfp-zone flag-usage is not obvious: If you pass a modified
zone, shmem core will WARN() or even BUG(). In other words, the following
must be true for 'gfp' passed to shmem_read_mapping_pages_gfp():
gfp_zone(mapping_gfp_mask(mapping)) == gfp_zone(gfp)
Add a comment to drm_gem_read_pages() explaining that constraint.
Signed-off-by: David Herrmann <dh.herrmann@gmail.com>
2014-05-25 12:59:47 +02:00
|
|
|
|
2013-08-07 13:41:24 -04:00
|
|
|
|
|
|
|
|
|
2023-06-21 17:45:49 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-08-26 11:37:21 -04:00
|
|
|
|
2020-05-11 11:35:47 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-08-07 13:41:24 -04:00
|
|
|
|
2015-12-04 23:45:44 -05:00
|
|
|
|
2013-08-07 13:41:24 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-02-21 16:37:42 -08:00
|
|
|
|
2013-08-07 13:41:24 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-01-08 15:45:17 +08:00
|
|
|
|
|
|
|
|
|
2023-06-21 17:45:49 +01:00
|
|
|
|
|
|
|
|
|
2025-08-26 11:37:21 -04:00
|
|
|
|
2023-06-21 17:45:49 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-08-07 13:41:24 -04:00
|
|
|
|
2023-10-05 14:56:47 +01:00
|
|
|
|
|
|
|
|
|
2023-06-21 17:45:49 +01:00
|
|
|
|
2013-08-07 13:41:24 -04:00
|
|
|
|
2014-05-25 14:34:08 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-08-07 13:41:24 -04:00
|
|
|
|
2015-11-06 16:28:49 -08:00
|
|
|
|
2023-06-21 17:45:49 +01:00
|
|
|
|
2013-08-07 13:41:24 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-01-08 15:45:17 +08:00
|
|
|
|
2023-06-21 17:45:49 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-01-08 15:45:17 +08:00
|
|
|
|
2023-06-21 17:45:49 +01:00
|
|
|
|
|
|
|
|
|
2013-08-07 13:41:24 -04:00
|
|
|
|
2017-05-17 14:23:12 +02:00
|
|
|
|
2023-06-21 17:45:49 +01:00
|
|
|
|
2013-08-07 13:41:24 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-01-08 15:45:17 +08:00
|
|
|
|
2023-06-21 17:45:49 +01:00
|
|
|
|
2019-01-08 15:45:17 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-08-07 13:41:24 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-21 17:45:49 +01:00
|
|
|
|
2013-08-07 13:41:24 -04:00
|
|
|
|
2023-06-21 17:45:49 +01:00
|
|
|
|
|
|
|
|
|
2019-07-19 08:28:51 -06:00
|
|
|
|
|
|
|
|
|
2023-06-21 17:45:49 +01:00
|
|
|
|
2019-07-19 08:28:51 -06:00
|
|
|
|
2013-08-07 13:41:24 -04:00
|
|
|
|
2023-06-21 17:45:49 +01:00
|
|
|
|
2013-08-07 13:41:24 -04:00
|
|
|
|
|
|
|
|
|
2023-06-21 17:45:49 +01:00
|
|
|
|
2013-08-07 13:41:24 -04:00
|
|
|
|
|
|
|
|
|
2023-06-21 17:45:49 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-08-07 13:41:24 -04:00
|
|
|
|
2023-06-21 17:45:49 +01:00
|
|
|
|
|
|
|
|
|
2013-08-07 13:41:24 -04:00
|
|
|
|
2017-05-17 14:23:12 +02:00
|
|
|
|
2013-08-07 13:41:24 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-03-08 14:26:02 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-02-06 18:51:41 +05:30
|
|
|
|
2019-03-08 14:26:02 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-02-06 18:51:41 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-03-08 14:26:02 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-02-06 18:51:41 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-03-08 14:26:02 -06:00
|
|
|
|
|
|
|
|
|
2026-02-06 18:51:41 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-03-08 14:26:02 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-03-16 09:38:09 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-03-08 14:26:02 -06:00
|
|
|
|
|
|
|
|
|
2026-03-16 09:38:09 +00:00
|
|
|
|
|
|
|
|
|
2019-03-08 14:26:02 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-09-02 23:40:20 +05:30
|
|
|
|
|
|
|
|
|
2019-03-08 14:26:02 -06:00
|
|
|
|
2026-02-06 18:51:41 +05:30
|
|
|
|
|
|
|
|
|
2019-03-08 14:26:02 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-02-23 11:48:20 +01:00
|
|
|
|
2019-03-08 14:26:02 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-11-12 09:27:32 +00:00
|
|
|
|
2026-02-06 18:51:41 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-03-08 14:26:02 -06:00
|
|
|
|
|
|
|
|
|
2026-02-06 18:51:41 +05:30
|
|
|
|
|
|
|
|
|
2019-03-08 14:26:02 -06:00
|
|
|
|
2026-02-06 18:51:41 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-03-08 14:26:02 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-10-22 19:11:29 +02:00
|
|
|
|
2019-02-01 17:23:26 -08:00
|
|
|
|
2015-10-22 19:11:29 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-08-24 16:36:34 +08:00
|
|
|
|
2015-10-22 19:11:29 +02:00
|
|
|
|
2024-08-24 16:36:34 +08:00
|
|
|
|
2015-10-22 19:11:29 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-07-30 12:06:12 -07:00
|
|
|
|
2016-05-09 11:04:54 +01:00
|
|
|
|
2008-07-30 12:06:12 -07:00
|
|
|
|
2019-03-08 14:26:02 -06:00
|
|
|
|
2008-07-30 12:06:12 -07:00
|
|
|
|
2019-03-08 14:26:02 -06:00
|
|
|
|
2008-07-30 12:06:12 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-02-02 09:41:54 -06:00
|
|
|
|
2019-08-11 10:06:32 +02:00
|
|
|
|
2019-02-02 09:41:54 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-08-11 10:06:32 +02:00
|
|
|
|
2019-02-02 09:41:54 -06:00
|
|
|
|
|
|
|
|
|
2025-09-02 23:40:20 +05:30
|
|
|
|
2019-02-02 09:41:54 -06:00
|
|
|
|
2025-09-02 23:40:20 +05:30
|
|
|
|
2019-02-02 09:41:54 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-09-02 23:40:20 +05:30
|
|
|
|
2019-02-02 09:41:54 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-11-09 11:08:18 +01:00
|
|
|
|
|
|
|
|
|
2019-02-02 09:41:54 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-05-15 10:50:53 +01:00
|
|
|
|
2019-02-02 09:41:54 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-08-11 10:06:32 +02:00
|
|
|
|
2019-02-02 09:41:54 -06:00
|
|
|
|
2008-07-30 12:06:12 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-09-30 16:49:56 +02:00
|
|
|
|
2018-09-13 20:20:50 +01:00
|
|
|
|
2008-07-30 12:06:12 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-09-30 16:49:56 +02:00
|
|
|
|
2018-09-13 20:20:50 +01:00
|
|
|
|
2008-07-30 12:06:12 -07:00
|
|
|
|
2016-05-09 11:04:54 +01:00
|
|
|
|
2008-07-30 12:06:12 -07:00
|
|
|
|
2010-08-04 14:19:46 +01:00
|
|
|
|
2008-07-30 12:06:12 -07:00
|
|
|
|
2013-08-15 00:02:44 +02:00
|
|
|
|
2013-08-15 00:02:37 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-02-11 14:26:28 +00:00
|
|
|
|
2016-01-04 10:11:01 +00:00
|
|
|
|
2013-02-27 17:04:08 -08:00
|
|
|
|
2009-02-11 14:26:28 +00:00
|
|
|
|
2013-06-27 08:58:33 +09:00
|
|
|
|
|
|
|
|
|
2008-07-30 12:06:12 -07:00
|
|
|
|
2009-02-09 11:31:41 +00:00
|
|
|
|
2013-06-27 08:58:33 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-02-09 11:31:41 +00:00
|
|
|
|
2013-08-15 00:02:44 +02:00
|
|
|
|
2020-05-15 10:50:53 +01:00
|
|
|
|
2009-02-09 11:31:41 +00:00
|
|
|
|
2008-07-30 12:06:12 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-08-23 12:40:55 +03:00
|
|
|
|
2008-07-30 12:06:12 -07:00
|
|
|
|
2014-09-30 16:49:56 +02:00
|
|
|
|
2018-09-13 20:20:50 +01:00
|
|
|
|
2008-07-30 12:06:12 -07:00
|
|
|
|
2013-08-15 00:02:44 +02:00
|
|
|
|
2008-07-30 12:06:12 -07:00
|
|
|
|
2013-08-15 00:02:45 +02:00
|
|
|
|
2017-02-28 15:46:41 +01:00
|
|
|
|
2013-08-15 00:02:45 +02:00
|
|
|
|
|
|
|
|
|
2008-07-30 12:06:12 -07:00
|
|
|
|
2013-08-15 00:02:45 +02:00
|
|
|
|
2008-07-30 12:06:12 -07:00
|
|
|
|
2013-08-15 00:02:45 +02:00
|
|
|
|
|
|
|
|
|
2008-07-30 12:06:12 -07:00
|
|
|
|
2020-07-20 18:30:50 -04:00
|
|
|
|
2008-07-30 12:06:12 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-07-20 18:30:50 -04:00
|
|
|
|
2020-08-11 11:58:31 +10:00
|
|
|
|
2020-07-20 18:30:50 -04:00
|
|
|
|
2008-07-30 12:06:12 -07:00
|
|
|
|
|
|
|
|
|
2025-07-17 10:35:55 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-01-23 14:15:40 +00:00
|
|
|
|
2025-07-17 10:35:55 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-01-23 14:15:40 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-07-17 10:35:55 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-01-23 14:15:40 +00:00
|
|
|
|
2025-12-12 14:41:33 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-07-17 10:35:55 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-01-23 14:15:40 +00:00
|
|
|
|
|
|
|
|
|
2025-07-17 10:35:55 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-01-23 14:15:40 +00:00
|
|
|
|
|
|
|
|
|
2025-07-17 10:35:55 -04:00
|
|
|
|
|
|
|
|
|
2026-01-23 14:15:40 +00:00
|
|
|
|
2025-07-17 10:35:55 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-12-12 14:41:33 +01:00
|
|
|
|
|
|
|
|
|
2025-07-17 10:35:55 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-07-30 12:06:12 -07:00
|
|
|
|
2021-07-30 21:27:29 +08:00
|
|
|
|
2014-01-21 12:39:00 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-07-30 12:06:12 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-02-12 14:55:33 +00:00
|
|
|
|
2008-07-30 12:06:12 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-01-21 12:39:00 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-07-30 12:06:12 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-06-09 00:24:59 +00:00
|
|
|
|
2008-07-30 12:06:12 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-03-30 11:40:52 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-07-30 21:27:29 +08:00
|
|
|
|
2016-03-30 11:40:52 +02:00
|
|
|
|
|
|
|
|
|
2010-04-09 19:05:05 +00:00
|
|
|
|
|
|
|
|
|
2010-02-09 05:49:11 +00:00
|
|
|
|
2011-06-07 14:17:51 +01:00
|
|
|
|
2014-01-20 20:07:49 +01:00
|
|
|
|
2014-01-20 20:05:43 +01:00
|
|
|
|
2022-11-19 14:41:31 +08:00
|
|
|
|
|
|
|
|
|
2014-01-20 20:05:43 +01:00
|
|
|
|
2022-08-02 08:51:42 -07:00
|
|
|
|
2010-02-09 05:49:11 +00:00
|
|
|
|
2010-04-09 19:05:05 +00:00
|
|
|
|
2010-02-09 05:49:11 +00:00
|
|
|
|
2008-07-30 12:06:12 -07:00
|
|
|
|
2014-01-21 12:39:00 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-07-30 12:06:12 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-10-15 09:36:26 +02:00
|
|
|
|
|
|
|
|
|
2008-07-30 12:06:12 -07:00
|
|
|
|
2020-09-23 12:21:59 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-07-30 12:06:12 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-10-22 19:11:29 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-02-11 14:01:46 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-02-28 15:46:41 +01:00
|
|
|
|
2009-02-11 14:01:46 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-10-22 19:11:29 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-02-11 14:01:46 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-05-15 10:50:53 +01:00
|
|
|
|
2009-02-11 14:01:46 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-04-16 14:14:52 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-09-23 12:21:59 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-04-16 14:14:52 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-08-25 18:28:58 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-04-16 14:14:52 +02:00
|
|
|
|
2020-09-23 12:21:59 +02:00
|
|
|
|
2013-04-16 14:14:52 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-10-16 13:51:53 +02:00
|
|
|
|
2013-04-16 14:14:52 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-02-28 15:46:41 +01:00
|
|
|
|
2013-04-16 14:14:52 +02:00
|
|
|
|
2020-10-27 22:49:22 +01:00
|
|
|
|
2021-01-15 10:30:38 +01:00
|
|
|
|
2020-10-27 22:49:22 +01:00
|
|
|
|
2020-09-23 12:21:59 +02:00
|
|
|
|
2019-11-13 14:56:12 +01:00
|
|
|
|
2021-01-15 10:30:38 +01:00
|
|
|
|
|
|
|
|
|
2019-11-13 14:56:12 +01:00
|
|
|
|
|
|
|
|
|
2021-01-15 10:30:38 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-11-13 14:56:12 +01:00
|
|
|
|
|
|
|
|
|
2023-01-26 11:37:49 -08:00
|
|
|
|
2019-11-13 14:56:12 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-04-16 14:14:52 +02:00
|
|
|
|
2021-01-15 10:30:38 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-04-16 14:14:52 +02:00
|
|
|
|
|
|
|
|
|
2009-02-11 14:01:46 -08:00
|
|
|
|
2025-12-05 19:22:24 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-11-05 10:31:53 -08:00
|
|
|
|
2025-12-05 19:22:24 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-11-05 10:31:53 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-10-15 11:33:43 +02:00
|
|
|
|
2013-07-24 21:07:52 +02:00
|
|
|
|
2008-11-05 10:31:53 -08:00
|
|
|
|
2017-08-02 13:56:02 +02:00
|
|
|
|
2025-12-05 19:22:24 +01:00
|
|
|
|
2012-02-20 14:18:07 +00:00
|
|
|
|
2015-10-15 11:33:43 +02:00
|
|
|
|
|
|
|
|
|
2025-12-05 19:22:24 +01:00
|
|
|
|
2015-10-15 11:33:43 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-11-05 10:31:53 -08:00
|
|
|
|
2015-10-15 11:33:43 +02:00
|
|
|
|
2025-12-05 19:22:24 +01:00
|
|
|
|
2015-10-15 11:33:43 +02:00
|
|
|
|
2016-09-01 14:48:33 +02:00
|
|
|
|
2020-05-15 10:50:53 +01:00
|
|
|
|
2025-12-05 19:22:24 +01:00
|
|
|
|
2008-11-05 10:31:53 -08:00
|
|
|
|
|
|
|
|
|
2025-12-05 19:22:24 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-12-09 18:11:51 +01:00
|
|
|
|
2025-12-05 19:22:24 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-01-06 17:49:35 +01:00
|
|
|
|
|
|
|
|
|
2025-12-05 19:22:24 +01:00
|
|
|
|
2026-01-06 17:49:35 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-12-05 19:22:24 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-12-09 18:11:51 +01:00
|
|
|
|
2025-12-05 19:22:24 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-10-15 11:33:43 +02:00
|
|
|
|
2008-11-05 10:31:53 -08:00
|
|
|
|
2020-05-15 10:50:53 +01:00
|
|
|
|
2008-11-05 10:31:53 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-11-07 20:13:40 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-02-26 18:03:04 +01:00
|
|
|
|
2017-11-07 20:13:40 +01:00
|
|
|
|
2020-09-23 12:21:59 +02:00
|
|
|
|
2018-11-10 15:56:45 +01:00
|
|
|
|
2017-11-07 20:13:40 +01:00
|
|
|
|
2018-11-10 15:56:45 +01:00
|
|
|
|
2025-03-23 00:25:59 +03:00
|
|
|
|
2018-11-10 15:56:45 +01:00
|
|
|
|
2020-11-03 10:30:11 +01:00
|
|
|
|
2018-11-10 15:56:45 +01:00
|
|
|
|
2022-10-17 20:22:11 +03:00
|
|
|
|
|
|
|
|
|
2020-11-03 10:30:11 +01:00
|
|
|
|
2020-11-03 10:30:12 +01:00
|
|
|
|
2018-11-10 15:56:45 +01:00
|
|
|
|
2020-11-03 10:30:12 +01:00
|
|
|
|
2020-11-03 10:30:11 +01:00
|
|
|
|
2020-11-03 10:30:12 +01:00
|
|
|
|
2022-02-04 09:05:41 -08:00
|
|
|
|
2020-11-03 10:30:12 +01:00
|
|
|
|
2018-11-10 15:56:45 +01:00
|
|
|
|
2020-11-03 10:30:12 +01:00
|
|
|
|
2018-11-10 15:56:45 +01:00
|
|
|
|
2025-03-23 00:25:59 +03:00
|
|
|
|
2018-11-10 15:56:45 +01:00
|
|
|
|
2025-03-23 00:25:59 +03:00
|
|
|
|
2018-11-10 15:56:45 +01:00
|
|
|
|
2022-10-17 20:22:11 +03:00
|
|
|
|
|
|
|
|
|
2022-02-04 09:05:41 -08:00
|
|
|
|
2018-11-10 15:56:45 +01:00
|
|
|
|
|
|
|
|
|
2020-09-23 12:21:59 +02:00
|
|
|
|
2020-11-03 10:30:12 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-02-04 09:05:41 -08:00
|
|
|
|
2018-11-10 15:56:45 +01:00
|
|
|
|
2025-03-23 00:25:59 +03:00
|
|
|
|
2019-03-08 08:17:13 -08:00
|
|
|
|
2024-02-27 11:14:57 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-03-23 00:25:59 +03:00
|
|
|
|
2022-10-17 20:22:11 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-03-23 00:25:59 +03:00
|
|
|
|
2022-10-17 20:22:11 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-03-23 00:25:59 +03:00
|
|
|
|
2022-10-17 20:22:11 +03:00
|
|
|
|
2025-03-23 00:25:59 +03:00
|
|
|
|
2022-10-17 20:22:11 +03:00
|
|
|
|
|
|
|
|
|
2025-03-23 00:25:59 +03:00
|
|
|
|
2022-10-17 20:22:11 +03:00
|
|
|
|
|
|
|
|
|
2025-03-23 00:25:59 +03:00
|
|
|
|
2022-10-17 20:22:11 +03:00
|
|
|
|
2019-03-08 08:17:13 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-08-11 10:06:32 +02:00
|
|
|
|
2019-07-31 09:41:50 +02:00
|
|
|
|
2019-03-08 08:17:13 -08:00
|
|
|
|
2022-06-30 23:04:04 +03:00
|
|
|
|
2019-03-08 08:17:13 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-08-11 10:06:32 +02:00
|
|
|
|
2019-07-31 09:41:50 +02:00
|
|
|
|
2019-03-08 08:17:13 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-08-11 10:06:32 +02:00
|
|
|
|
2019-03-08 08:17:13 -08:00
|
|
|
|
|
|
|
|
|
2019-08-11 10:06:32 +02:00
|
|
|
|
2019-03-08 08:17:13 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-06-30 23:04:04 +03:00
|
|
|
|
2019-03-08 08:17:13 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-08-11 10:06:32 +02:00
|
|
|
|
2019-03-08 08:17:13 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-08-02 08:51:42 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-03-20 07:43:28 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-08-02 08:51:42 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-03-20 07:43:28 -07:00
|
|
|
|
2022-08-02 08:51:42 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-11-04 19:04:59 +03:00
|
|
|
|
2022-08-02 08:51:42 -07:00
|
|
|
|
2025-06-29 13:12:46 -07:00
|
|
|
|
2022-08-02 08:51:42 -07:00
|
|
|
|
|
|
|
|
|
2022-11-04 19:04:59 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-06-29 13:12:46 -07:00
|
|
|
|
|
|
|
|
|
2022-08-02 08:51:42 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-06-29 13:12:46 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-08-02 08:51:42 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-06-29 13:12:46 -07:00
|
|
|
|
2022-11-04 19:04:59 +03:00
|
|
|
|
2022-08-02 08:51:42 -07:00
|
|
|
|
2022-11-04 19:04:59 +03:00
|
|
|
|
2022-08-02 08:51:42 -07:00
|
|
|
|
2025-06-29 13:12:46 -07:00
|
|
|
|
2022-08-02 08:51:42 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-06-29 13:12:46 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-08-02 08:51:42 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-11-16 17:07:50 +03:00
|
|
|
|
|
|
|
|
|
2025-03-23 00:26:00 +03:00
|
|
|
|
2022-11-16 17:07:50 +03:00
|
|
|
|
|
|
|
|
|
2025-03-23 00:26:00 +03:00
|
|
|
|
2022-11-16 17:07:50 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-03-23 00:26:00 +03:00
|
|
|
|