✓ CI.checkpatch: success for drm/xe: Protect devcoredump access after unbind

[Patchwork]

== Series Details ==

Series: drm/xe: Protect devcoredump access after unbind
URL   : https://patchwork.freedesktop.org/series/132005/
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
10b531c2aeb176a1a539b4a77216232f97719cec
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit 7ecf971db740db305962a6983c1cec8a501ebb59
Author: Rodrigo Vivi <rodrigo.vivi at intel.com>
Date:   Wed Apr 3 15:50:44 2024 -0400

    drm/xe: Protect devcoredump access after unbind
    
    While we don't have the full flow protection when devcoredump
    is accessed after device unbind. Let's at least for now
    protect against null dereference:
    
    [  422.766508] KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007]
    [  423.119584] RIP: 0010:xe_vm_snapshot_free+0x30/0x180 [xe]
    
    While at it, I also fixed a non-standard code-declaration block
    on the similar function of xe_guc_submit.
    
    v2: - Use IS_ERR_OR_NULL (Nirmoy)
        - Expand to other functions
    
    Cc: José Roberto de Souza <jose.souza at intel.com>
    Cc: Nirmoy Das <nirmoy.das at intel.com>
    Signed-off-by: Rodrigo Vivi <rodrigo.vivi at intel.com>
+ /mt/dim checkpatch 406e10d886a22211d2866bfa9322aec1727171f8 drm-intel
7ecf971db740 drm/xe: Protect devcoredump access after unbind