igt@dumb_buffer@create-clear - abort - WARNING: possible circular locking dependency detected
<4> [207.461389]
<4> [207.461395] ======================================================
<4> [207.461397] WARNING: possible circular locking dependency detected
<4> [207.461399] 6.2.0-rc8-drmtip_1315-gffa7027c353c+ #1 Not tainted
<4> [207.461401] ------------------------------------------------------
<4> [207.461403] kworker/10:2H/1129 is trying to acquire lock:
<4> [207.461405] ffffffff8275f660 (fs_reclaim){+.+.}-{0:0}, at: __kmem_cache_alloc_node+0x30/0x1b0
<4> [207.461413]
but task is already holding lock:
<4> [207.461415] ffffc90001fafe60 ((work_completion)(&(&guc->timestamp.work)->work)){+.+.}-{0:0}, at: process_one_work+0x1cc/0x570
<4> [207.461421]
which lock already depends on the new lock.
<4> [207.461423]
the existing dependency chain (in reverse order) is:
<4> [207.461425]
-> #2 ((work_completion)(&(&guc->timestamp.work)->work)){+.+.}-{0:0}:
<4> [207.461429] lock_acquire+0xd6/0x310
<4> [207.461432] __flush_work+0x74/0x4f0
<4> [207.461435] __cancel_work_timer+0x14f/0x1f0
<4> [207.461437] intel_guc_submission_reset_prepare+0x81/0x4b0 [i915]
<4> [207.461569] intel_uc_reset_prepare+0x7e/0x90 [i915]
<4> [207.461664] reset_prepare+0x21/0x60 [i915]
<4> [207.461735] intel_gt_reset+0x15c/0x330 [i915]
<4> [207.461810] intel_gt_reset_global+0xfb/0x170 [i915]