Groups > linux.kernel > #1712012

Re: drm/mtrr: possible deadlock

From	Dmitry Vyukov <dvyukov@google.com>
Newsgroups	linux.kernel
Subject	Re: drm/mtrr: possible deadlock
Date	2017-08-15 11:40 +0200
Message-ID	<ueGul-80m-13@gated-at.bofh.it> (permalink)
References	<ueEiR-6If-9@gated-at.bofh.it> <ueGkG-7Xk-19@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On Tue, Aug 15, 2017 at 11:20 AM, Dou Liyang <douly.fnst@cn.fujitsu.com> wrote:
> Hi Dmitry,
>
> At 08/15/2017 03:18 PM, Dmitry Vyukov wrote:
>>
>> Hello,
>>
>> I am getting the following deadlock report while booting linux-next on
>> 91dfed74eabcdae9378131546c446442c29bf769 in qemu. Config is attached.
>>
>>
>> WARNING: possible recursive locking detected
>> 4.13.0-rc4-next-20170811 #2 Not tainted
>> --------------------------------------------
>> swapper/0/1 is trying to acquire lock:
>>  (cpu_hotplug_lock.rw_sem){++++}, at: [<ffffffff816a19fc>]
>> stop_machine+0x1c/0x40 kernel/stop_machine.c:596
>>
>> but task is already holding lock:
>>  (cpu_hotplug_lock.rw_sem){++++}, at: [<ffffffff812aad6d>]
>> get_online_cpus include/linux/cpu.h:126 [inline]
>>  (cpu_hotplug_lock.rw_sem){++++}, at: [<ffffffff812aad6d>]
>> mtrr_add_page+0x1bd/0xe80 arch/x86/kernel/cpu/mtrr/main.c:328
>>
>
> I guess you may want this.
>
> https://lkml.org/lkml/2017/8/14/7
>
> and the solution by Thomas
>
> https://lkml.org/lkml/2017/8/14/64


Will try that. Thanks!

Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

Re: drm/mtrr: possible deadlock Dou Liyang <douly.fnst@cn.fujitsu.com> - 2017-08-15 11:30 +0200
  Re: drm/mtrr: possible deadlock Dmitry Vyukov <dvyukov@google.com> - 2017-08-15 11:40 +0200

csiph-web