From: shrikant <shrikant.maurya@techveda.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Pavel Machek <pavel@ucw.cz>, Len Brown <len.brown@intel.com>,
Greg KH <gregkh@linuxfoundation.org>,
Linux PM list <linux-pm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Suniel Mahesh <sunil.m@techveda.org>,
Karthik Tummala <karthik@techveda.org>,
raghu@techveda.org
Subject: Re: [PATCH] drivers: base: power: Fix GFP_KERNEL in spinlock context
Date: Sat, 16 Dec 2017 13:44:57 +0530 [thread overview]
Message-ID: <0c191b75-9072-28f1-5f7b-550ddcf3a706@techveda.org> (raw)
In-Reply-To: <CAMuHMdUrhV9RkUnXkTbSWaRY33iQrANwbKBE5KAPQseNgxOofg@mail.gmail.com>
On Tuesday 12 December 2017 08:28 PM, Geert Uytterhoeven wrote:
> Hi Shrikant,
>
> On Tue, Dec 12, 2017 at 2:45 PM, <shrikant.maurya@techveda.org> wrote:
>> From: Shrikant Maurya <shrikant.maurya@techveda.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.
>> Fixed by replacing GFP_KERNEL to GFP_ATOMIC.
>>
>> Reported-by: Jia-Ju Bai <baijiaju1990@gmail.com>
>> Signed-off-by: Shrikant Maurya <shrikant.maurya@techveda.org>
>> Signed-off-by: Suniel Mahesh <sunil.m@techveda.org>
>> Signed-off-by: Raghu Bharadwaj <raghu@techveda.org>
>> Signed-off-by: Karthik Tummala <karthik@techveda.org>
>
> Can't the call to device_init_wakeup() in isp116x_start() just be moved
> below the spinlock release?
Can't move it below the spinlock.
Value going to be written into HcRhStatus register depends on it:
isp116x_write_reg32(isp116x, HCRHSTATUS, val);
Instead we can move it before the spinlock.
>
>> --- a/drivers/base/power/wakeup.c
>> +++ b/drivers/base/power/wakeup.c
>> @@ -92,11 +92,11 @@ struct wakeup_source *wakeup_source_create(const char *name)
>> {
>> struct wakeup_source *ws;
>>
>> - ws = kmalloc(sizeof(*ws), GFP_KERNEL);
>> + ws = kmalloc(sizeof(*ws), GFP_ATOMIC);
>
> With GFP_ATOMIC, allocation failure is much more likely to occur.
> So IMHO it's better to fix the isp116x, than to impose this burden on
> every user.
Absolutely. Thanks for pointing it out, it's not the right solution.
>
>> if (!ws)
>> return NULL;
>>
>> - wakeup_source_prepare(ws, name ? kstrdup_const(name, GFP_KERNEL) : NULL);
>> + wakeup_source_prepare(ws, name ? kstrdup_const(name, GFP_ATOMIC) : NULL);
>> return ws;
>> }
>> EXPORT_SYMBOL_GPL(wakeup_source_create);
>
> Gr{oetje,eeting}s,
>
> Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
>
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
> -- Linus Torvalds
>
Thank you Geert.
--
Shrikant
techveda.org
next prev parent reply other threads:[~2017-12-16 8:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-12 13:45 shrikant.maurya
2017-12-12 14:58 ` Geert Uytterhoeven
2017-12-15 8:45 ` Pavel Machek
2017-12-16 8:15 ` shrikant
2017-12-16 8:14 ` shrikant [this message]
2017-12-12 16:55 ` Rafael J. Wysocki
2017-12-16 8:21 ` shrikant
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0c191b75-9072-28f1-5f7b-550ddcf3a706@techveda.org \
--to=shrikant.maurya@techveda.org \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=karthik@techveda.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=raghu@techveda.org \
--cc=rjw@rjwysocki.net \
--cc=sunil.m@techveda.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®