[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJZ5v0gRtkBf7uu4C_k7ivNGo=JM0bB1PAdr_6Nbbs39OPevHw@mail.gmail.com>
Date: Fri, 16 Feb 2018 10:14:53 +0100
From: "Rafael J. Wysocki" <rafael@...nel.org>
To: Andy Shevchenko <andy.shevchenko@...il.com>
Cc: Tony Lindgren <tony@...mide.com>,
"Rafael J . Wysocki" <rafael.j.wysocki@...el.com>,
Alan Stern <stern@...land.harvard.edu>,
Linux PM <linux-pm@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Brian Norris <briannorris@...omium.org>,
Grygorii Strashko <grygorii.strashko@...com>,
Ulf Hansson <ulf.hansson@...aro.org>
Subject: Re: [PATCH] PM / wakeirq: Add wakeup name to dedicated wake irqs
On Wed, Feb 14, 2018 at 12:23 PM, Andy Shevchenko
<andy.shevchenko@...il.com> wrote:
> On Fri, Feb 9, 2018 at 6:14 PM, Tony Lindgren <tony@...mide.com> wrote:
>> This makes it easy to grep :wakeup /proc/interrupts.
>
> I used to have another patch (not published) to provide this
> information via /sys/kernel/irq.
>
> OK, here we are:
>
>
>> + namelen = strlen(dev_name(dev)) + strlen(postfix) + 1;
>> + wirq->name = kzalloc(namelen, GFP_KERNEL);
>
> kasprintf()
It's a bit hard to comment patches sent as attachments, but I'll try anyway. :-)
IMO it is somewhat excessive to put the entire sprintf() under a raw
spinlock and it's not even necessary.
The value can change any time after you've dropped the lock and in
particular before the function returns, so why bother with locking?
desc will not go away from under you at that point anyway.
Powered by blists - more mailing lists