✓ CI.checkpatch: success for drm/xe: Add devcoredump locking and reason string (rev3)
Patchwork
patchwork at emeril.freedesktop.org
Fri Nov 22 04:13:46 UTC 2024
== Series Details ==
Series: drm/xe: Add devcoredump locking and reason string (rev3)
URL : https://patchwork.freedesktop.org/series/141628/
State : success
== Summary ==
+ KERNEL=/kernel
+ git clone https://gitlab.freedesktop.org/drm/maintainer-tools mt
Cloning into 'mt'...
warning: redirecting to https://gitlab.freedesktop.org/drm/maintainer-tools.git/
+ git -C mt rev-list -n1 origin/master
30ab6715fc09baee6cc14cb3c89ad8858688d474
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit bf02b61757b8756796fbb28c9a184677be89b7e7
Author: John Harrison <John.C.Harrison at Intel.com>
Date: Thu Nov 21 18:53:57 2024 -0800
drm/xe: Add mutex locking to devcoredump
There are now multiple places that can trigger a coredump. Some of
which can happen in parallel. There is already a check against
capturing multiple dumps sequentially, but without locking it doesn't
guarantee to work against concurrent dumps. And if two dumps do happen
in parallel, they can end up doing Bad Things such as one call stack
freeing the data the other call stack is still processing. Which leads
to a crashed kernel.
Further, it is possible for the DRM timeout to expire and trigger a
free of the capture while a user is still reading that capture out
through sysfs. Again leading to dodgy pointer problems.
So, add a mutext lock around the capture, read and free functions to
prevent inteference.
v2: Swap tiny scope spin_lock for larger scope mutex and fix
kernel-doc comment (review feedback from Matthew Brost)
v3: Move mutex locks to exclude worker thread and add reclaim
annotation (review feedback from Matthew Brost)
Signed-off-by: John Harrison <John.C.Harrison at Intel.com>
+ /mt/dim checkpatch bb17c42521f57b592e9ad49daca1f9f9045d3199 drm-intel
b67615bc7436 drm/xe: Add a reason string to the devcoredump
bf02b61757b8 drm/xe: Add mutex locking to devcoredump
More information about the Intel-xe
mailing list