[Bug 111626] [CI][SHARDS] igt at perf_pmu@busy-idle-no-semaphores-bcs0 - dmesg-warn - WARNING: possible irq lock inversion dependency detected

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=111626

--- Comment #23 from Chris Wilson <chris at chris-wilson.co.uk> ---
Sigh,

The following commit has been merged into the locking/core branch of tip:

  Commit-ID:     a0855d24fc22d49cdc25664fb224caee16998683
  Gitweb:       
https://git.kernel.org/tip/a0855d24fc22d49cdc25664fb224caee16998683
  Author:        Davidlohr Bueso <dave at stgolabs.net>
  AuthorDate:    Thu, 24 Oct 2019 20:36:34 -07:00
  Committer:     Ingo Molnar <mingo at kernel.org>
  CommitterDate: Tue, 29 Oct 2019 12:22:52 +01:00

  locking/mutex: Complain upon mutex API misuse in IRQ contexts

  Add warning checks if mutex_trylock() or mutex_unlock() are used in
  IRQ contexts, under CONFIG_DEBUG_MUTEXES=y.

  While the mutex rules and semantics are explicitly documented, this allows
  to expose any abusers and robustifies the whole thing.

  While trylock and unlock are non-blocking, calling from IRQ context
  is still forbidden (lock must be within the same context as unlock).

  Signed-off-by: Davidlohr Bueso <dbueso at suse.de>
  Signed-off-by: Peter Zijlstra (Intel) <peterz at infradead.org>
  Cc: Linus Torvalds <torvalds at linux-foundation.org>
  Cc: Peter Zijlstra <peterz at infradead.org>
  Cc: Thomas Gleixner <tglx at linutronix.de>
  Cc: dave at stgolabs.net
  Link: https://lkml.kernel.org/r/20191025033634.3330-1-dave@stgolabs.net
  Signed-off-by: Ingo Molnar <mingo at kernel.org>

next kernel this warning will get louder.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20191030/0d0fe134/attachment-0001.html>