From: Simon Horman <horms@verge.net.au>
To: Brian W Hart <hartb@linux.vnet.ibm.com>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Viresh Kumar <viresh.kumar@linaro.org>,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
linux-sh@vger.kernel.org,
Stratos Karafotis <stratosk@semaphore.gr>,
Magnus Damm <magnus.damm@gmail.com>
Subject: Re: [PATCH] cpufreq: make table sentinal macros unsigned to match use
Date: Sat, 28 Jun 2014 00:18:50 +0000 [thread overview]
Message-ID: <20140628001850.GF27128@verge.net.au> (raw)
In-Reply-To: <20140627210939.GB24604@oc3347516403.ibm.com>
On Fri, Jun 27, 2014 at 04:09:39PM -0500, Brian W Hart wrote:
> Commit 5eeaf1f18973 (cpufreq: Fix build error on some platforms that
> use cpufreq_for_each_*) moved function cpufreq_next_valid() to a public
> header. Warnings are now generated when objects including that header
> are built with -Wsign-compare (as an out-of-tree module might be):
>
> .../include/linux/cpufreq.h: In function ‘cpufreq_next_valid’:
> .../include/linux/cpufreq.h:519:27: warning: comparison between signed
> and unsigned integer expressions [-Wsign-compare]
> while ((*pos)->frequency != CPUFREQ_TABLE_END)
> ^
> .../include/linux/cpufreq.h:520:25: warning: comparison between signed
> and unsigned integer expressions [-Wsign-compare]
> if ((*pos)->frequency != CPUFREQ_ENTRY_INVALID)
> ^
>
> Constants CPUFREQ_ENTRY_INVALID and CPUFREQ_TABLE_END are signed, but
> are used with unsigned member 'frequency' of cpufreq_frequency_table.
> Update the macro definitions to be explicitly unsigned to match their
> use.
>
> This also corrects potentially wrong behavior of clk_rate_table_iter()
> if unsigned long is wider than usigned int.
>
> Signed-off-by: Brian W Hart <hartb@linux.vnet.ibm.com>
Reviewed-by: Simon Horman <horms+renesas@verge.net.au>
> ---
> These macros are fairly broadly used in the kernel so I was bit leery
> of changing them, but after inspection I think it's fine. I found 102
> uses of the macros, of which:
>
> 99 are uses with cpufreq_frequency_table.frequency (95) or with local
> variables of the same type as frequency (4). These should be just
> fine with this change--we're just making explicit a conversion that
> was previously implicit.
>
> 2 are uses with a local variable of different type (unsigned long) than
> 'frequency' (in drivers/sh/clk/core.c). One of these uses is safe;
> the other (in clk_rate_table_iter()) is broken if unsigned long
> is wider than unsigned int. As a side-effect, this patch corrects
> the potential misbehavior there.
>
> 1 is a use in macro cpufreq_for_each_entry() with what _should_ be the
> frequency member of a cpufreq_frequency_table, provided the caller it
> well-behaved. There are 18 callers of this macro; all are well-behaved.
> So these should also be safe.
>
> include/linux/cpufreq.h | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/include/linux/cpufreq.h b/include/linux/cpufreq.h
> index ec4112d..8f8ae95 100644
> --- a/include/linux/cpufreq.h
> +++ b/include/linux/cpufreq.h
> @@ -482,8 +482,8 @@ extern struct cpufreq_governor cpufreq_gov_conservative;
> *********************************************************************/
>
> /* Special Values of .frequency field */
> -#define CPUFREQ_ENTRY_INVALID ~0
> -#define CPUFREQ_TABLE_END ~1
> +#define CPUFREQ_ENTRY_INVALID ~0u
> +#define CPUFREQ_TABLE_END ~1u
> /* Special Values of .flags field */
> #define CPUFREQ_BOOST_FREQ (1 << 0)
>
> --
> 1.7.1
>
next prev parent reply other threads:[~2014-06-28 0:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-27 21:09 [PATCH] cpufreq: make table sentinal macros unsigned to match use Brian W Hart
2014-06-28 0:18 ` Simon Horman [this message]
2014-06-30 4:55 ` Viresh Kumar
2014-07-11 22:06 ` Brian W Hart
2014-07-18 1:20 ` Rafael J. Wysocki
2014-07-21 20:01 ` Brian W Hart
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=20140628001850.GF27128@verge.net.au \
--to=horms@verge.net.au \
--cc=hartb@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=rjw@rjwysocki.net \
--cc=stratosk@semaphore.gr \
--cc=viresh.kumar@linaro.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