From: kbuild test robot <lkp@intel.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: kbuild-all@01.org, Viresh Kumar <vireshk@kernel.org>,
Nishanth Menon <nm@ti.com>, Stephen Boyd <sboyd@codeaurora.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
Guenter Roeck <linux@roeck-us.net>,
Viresh Kumar <viresh.kumar@linaro.org>
Subject: Re: [PATCH -next] PM / OPP: Fix crash seen if CPU clock has no voltage regulator
Date: Tue, 16 Feb 2016 08:17:55 +0800 [thread overview]
Message-ID: <201602160831.dcRmh5Py%fengguang.wu@intel.com> (raw)
In-Reply-To: <1455564893-25455-1-git-send-email-linux@roeck-us.net>
[-- Attachment #1: Type: text/plain, Size: 3400 bytes --]
Hi Jon,
[auto build test WARNING on next-20160215]
url: https://github.com/0day-ci/linux/commits/Jon-Hunter/PM-OPP-Fix-NULL-pointer-dereference-crash-when-setting-the-OPP/20160215-220238
config: x86_64-randconfig-s0-02160737 (attached as .config)
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
Note: it may well be a FALSE warning. FWIW you are at least aware of it now.
http://gcc.gnu.org/wiki/Better_Uninitialized_Warnings
All warnings (new ones prefixed by >>):
drivers/base/power/opp/core.c: In function 'dev_pm_opp_set_rate':
>> drivers/base/power/opp/core.c:603:38: warning: 'ou_volt_max' may be used uninitialized in this function [-Wmaybe-uninitialized]
unsigned long ou_volt, ou_volt_min, ou_volt_max;
^
>> drivers/base/power/opp/core.c:603:25: warning: 'ou_volt_min' may be used uninitialized in this function [-Wmaybe-uninitialized]
unsigned long ou_volt, ou_volt_min, ou_volt_max;
^
>> drivers/base/power/opp/core.c:603:16: warning: 'ou_volt' may be used uninitialized in this function [-Wmaybe-uninitialized]
unsigned long ou_volt, ou_volt_min, ou_volt_max;
^
vim +/ou_volt_max +603 drivers/base/power/opp/core.c
6a0712f6 Viresh Kumar 2016-02-09 587 * @dev: device for which we do this operation
6a0712f6 Viresh Kumar 2016-02-09 588 * @target_freq: frequency to achieve
6a0712f6 Viresh Kumar 2016-02-09 589 *
6a0712f6 Viresh Kumar 2016-02-09 590 * This configures the power-supplies and clock source to the levels specified
6a0712f6 Viresh Kumar 2016-02-09 591 * by the OPP corresponding to the target_freq.
6a0712f6 Viresh Kumar 2016-02-09 592 *
6a0712f6 Viresh Kumar 2016-02-09 593 * Locking: This function takes rcu_read_lock().
6a0712f6 Viresh Kumar 2016-02-09 594 */
6a0712f6 Viresh Kumar 2016-02-09 595 int dev_pm_opp_set_rate(struct device *dev, unsigned long target_freq)
6a0712f6 Viresh Kumar 2016-02-09 596 {
6a0712f6 Viresh Kumar 2016-02-09 597 struct device_opp *dev_opp;
6a0712f6 Viresh Kumar 2016-02-09 598 struct dev_pm_opp *old_opp, *opp;
6a0712f6 Viresh Kumar 2016-02-09 599 struct regulator *reg;
6a0712f6 Viresh Kumar 2016-02-09 600 struct clk *clk;
6a0712f6 Viresh Kumar 2016-02-09 601 unsigned long freq, old_freq;
6a0712f6 Viresh Kumar 2016-02-09 602 unsigned long u_volt, u_volt_min, u_volt_max;
6a0712f6 Viresh Kumar 2016-02-09 @603 unsigned long ou_volt, ou_volt_min, ou_volt_max;
6a0712f6 Viresh Kumar 2016-02-09 604 int ret;
6a0712f6 Viresh Kumar 2016-02-09 605
6a0712f6 Viresh Kumar 2016-02-09 606 if (unlikely(!target_freq)) {
6a0712f6 Viresh Kumar 2016-02-09 607 dev_err(dev, "%s: Invalid target frequency %lu\n", __func__,
6a0712f6 Viresh Kumar 2016-02-09 608 target_freq);
6a0712f6 Viresh Kumar 2016-02-09 609 return -EINVAL;
6a0712f6 Viresh Kumar 2016-02-09 610 }
6a0712f6 Viresh Kumar 2016-02-09 611
:::::: The code at line 603 was first introduced by commit
:::::: 6a0712f6f199e737aa5913d28ec4bd3a25de9660 PM / OPP: Add dev_pm_opp_set_rate()
:::::: TO: Viresh Kumar <viresh.kumar@linaro.org>
:::::: CC: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 23003 bytes --]
next prev parent reply other threads:[~2016-02-16 0:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-15 19:34 Guenter Roeck
2016-02-16 0:17 ` kbuild test robot [this message]
2016-02-16 0:46 ` Viresh Kumar
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=201602160831.dcRmh5Py%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=nm@ti.com \
--cc=rjw@rjwysocki.net \
--cc=sboyd@codeaurora.org \
--cc=viresh.kumar@linaro.org \
--cc=vireshk@kernel.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®