<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED NOTOURBUG - [CI][BAT] igt@pm_rpm@module-reload - dmesg-warn - WARNING: possible circular locking dependency detected" href="https://bugs.freedesktop.org/show_bug.cgi?id=108676#c2">Comment # 2</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED NOTOURBUG - [CI][BAT] igt@pm_rpm@module-reload - dmesg-warn - WARNING: possible circular locking dependency detected" href="https://bugs.freedesktop.org/show_bug.cgi?id=108676">bug 108676</a> from <a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> Chris Wilson</a> <pre>Caused by commit 9dbbedaa6171247c4c7c40b83f05b200a117c2e0 Author: Sai Praneeth <<a href="mailto:sai.praneeth.prakhya@intel.com">sai.praneeth.prakhya@intel.com</a>> Date: Tue Sep 11 12:15:21 2018 -0700 efi: Make efi_rts_work accessible to efi page fault handler After the kernel has booted, if any accesses by firmware causes a page fault, the efi page fault handler would freeze efi_rts_wq and schedules a new process. To do this, the efi page fault handler needs efi_rts_work. Hence, make it accessible. There will be no race conditions in accessing this structure, because all the calls to efi runtime services are already serialized. Tested-by: Bhupesh Sharma <<a href="mailto:bhsharma@redhat.com">bhsharma@redhat.com</a>> Suggested-by: Matt Fleming <<a href="mailto:matt@codeblueprint.co.uk">matt@codeblueprint.co.uk</a>> Based-on-code-from: Ricardo Neri <<a href="mailto:ricardo.neri@intel.com">ricardo.neri@intel.com</a>> Signed-off-by: Sai Praneeth Prakhya <<a href="mailto:sai.praneeth.prakhya@intel.com">sai.praneeth.prakhya@intel.com</a>> Signed-off-by: Ard Biesheuvel <<a href="mailto:ard.biesheuvel@linaro.org">ard.biesheuvel@linaro.org</a>></pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> <li>You are on the CC list for the bug.</li> </ul> </body> </html>