[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 12 Dec 2017 17:55:00 +0100
From: "Rafael J. Wysocki" <rafael@...nel.org>
To: shrikant.maurya@...hveda.org
Cc: "Rafael J. Wysocki" <rjw@...ysocki.net>,
Pavel Machek <pavel@....cz>, Len Brown <len.brown@...el.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Linux PM <linux-pm@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
sunil.m@...hveda.org, karthik@...hveda.org, raghu@...hveda.org
Subject: Re: [PATCH] drivers: base: power: Fix GFP_KERNEL in spinlock context
On Tue, Dec 12, 2017 at 2:45 PM, <shrikant.maurya@...hveda.org> wrote:
> From: Shrikant Maurya <shrikant.maurya@...hveda.org>
>
> As reported by Jia-Ju Bai (https://lkml.org/lkml/2017/12/11/872):
> API's are using GFP_KERNEL to allocate memory which may sleep.
>
> To ensure atomicity such allocations must be avoided in critical
> sections under spinlock.
That's right.
Which is why wakeup_source_create() should never be called under a spinlock.
Are you aware of any place that happens in the mainline kernel?
Thanks,
Rafael
Powered by blists - more mailing lists