From: Frederic Weisbecker <fweisbec@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
Mark Gross <mgross@linux.intel.com>
Subject: Re: [PATCH 1/2] pm_qos: remove BKL
Date: Fri, 7 Aug 2009 04:03:32 +0200 [thread overview]
Message-ID: <20090807020330.GA5425@nowhere> (raw)
In-Reply-To: <20090806135953.7706e57d@bike.lwn.net>
On Thu, Aug 06, 2009 at 01:59:53PM -0600, Jonathan Corbet wrote:
> pm_qos_power_open got its lock_kernel() calls from the open() pushdown. A
> look at the code shows that the only global resources accessed are
> pm_qos_array and "name". pm_qos_array doesn't change (things pointed to
> therein do change, but they are atomics and/or are protected by
> pm_qos_lock). Accesses to "name" are totally unprotected with or without
> the BKL; that will be fixed shortly. The BKL is not helpful here; take it
> out.
>
> Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Is there a 2/2 missing patch in the series, or may be I missed it.
I guess it fixes the racy "name"...
> ---
> kernel/pm_qos_params.c | 8 +-------
> 1 files changed, 1 insertions(+), 7 deletions(-)
>
> diff --git a/kernel/pm_qos_params.c b/kernel/pm_qos_params.c
> index dfdec52..d96b83e 100644
> --- a/kernel/pm_qos_params.c
> +++ b/kernel/pm_qos_params.c
> @@ -29,7 +29,6 @@
>
> #include <linux/pm_qos_params.h>
> #include <linux/sched.h>
> -#include <linux/smp_lock.h>
> #include <linux/spinlock.h>
> #include <linux/slab.h>
> #include <linux/time.h>
> @@ -352,20 +351,15 @@ static int pm_qos_power_open(struct inode *inode, struct file *filp)
> int ret;
> long pm_qos_class;
>
> - lock_kernel();
> pm_qos_class = find_pm_qos_object_by_minor(iminor(inode));
> if (pm_qos_class >= 0) {
> filp->private_data = (void *)pm_qos_class;
> sprintf(name, "process_%d", current->pid);
> ret = pm_qos_add_requirement(pm_qos_class, name,
> PM_QOS_DEFAULT_VALUE);
> - if (ret >= 0) {
> - unlock_kernel();
> + if (ret >= 0)
> return 0;
> - }
> }
> - unlock_kernel();
> -
> return -EPERM;
> }
>
> --
> 1.6.2.5
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2009-08-07 2:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-06 19:58 [PATCH 0/2] pm_qos: BKL removal and cleanup Jonathan Corbet
2009-08-06 19:59 ` [PATCH 1/2] pm_qos: remove BKL Jonathan Corbet
2009-08-07 2:03 ` Frederic Weisbecker [this message]
2009-08-07 5:54 ` Frederic Weisbecker
2009-08-07 15:08 ` Jonathan Corbet
2009-08-08 0:31 ` Frederic Weisbecker
2009-08-06 20:01 ` [PATCH 2/2] pm_qos: clean up racy "name" variable Jonathan Corbet
2009-08-07 2:05 ` Jonathan Corbet
2009-08-07 6:03 ` Frederic Weisbecker
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=20090807020330.GA5425@nowhere \
--to=fweisbec@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mgross@linux.intel.com \
--cc=mingo@elte.hu \
/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