From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Dan Carpenter <dan.carpenter@linaro.org>
Cc: Tero Kristo <tero.kristo@linux.intel.com>,
Hans de Goede <hdegoede@redhat.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
platform-driver-x86@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH v2] platform/x86/intel/tpmi/plr: Fix output in plr_print_bits()
Date: Tue, 16 Jul 2024 13:05:57 +0300 (EEST) [thread overview]
Message-ID: <9c74d6ac-56e4-a79b-6d05-705a17561a3d@linux.intel.com> (raw)
In-Reply-To: <b0084e70-4144-445a-9b89-fb19f6b8336a@stanley.mountain>
On Mon, 15 Jul 2024, Dan Carpenter wrote:
> Smatch complains that 'str' can be used without being initialized:
>
> drivers/platform/x86/intel/intel_plr_tpmi.c:178 plr_print_bits()
> error: uninitialized symbol 'str'.
>
> In this loop, we iterate over all the set bits and print the name of the
> bit. The intention is that if there is a bit which is between 0-31 we
> look for the name in the first array plr_coarse_reasons[] which has 10
> elements. If the bit is in the 32-63 range we look for it in the
> plr_fine_reasons[] array which has 30 elements. If the bit is in the
> invalid ranges, 10-31 or 62-63, then we should print "UNKNOWN(%d)".
>
> The problem is that 'str' needs to be initialized at the start of each
> iteration, otherwise if we can't find the string then instead of printing
> "UNKNOWN(%d)", we will re-print whatever the previous bit was.
>
> Fixes: 9e9397a41b7b ("platform/x86/intel/tpmi/plr: Add support for the plr mailbox")
> Signed-off-by: Dan Carpenter <dan.carpenter@linaro.org>
> ---
> v2: initialize str at the start of each iteration
Thanks for the update, I've applied this fix now (will go along with the
for-next PR to Linus).
--
i.
>
> drivers/platform/x86/intel/intel_plr_tpmi.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/platform/x86/intel/intel_plr_tpmi.c b/drivers/platform/x86/intel/intel_plr_tpmi.c
> index c1aa52c23d25..69ace6a629bc 100644
> --- a/drivers/platform/x86/intel/intel_plr_tpmi.c
> +++ b/drivers/platform/x86/intel/intel_plr_tpmi.c
> @@ -162,10 +162,11 @@ static int plr_clear_cpu_status(struct tpmi_plr_die *plr_die, int cpu)
> static void plr_print_bits(struct seq_file *s, u64 val, int bits)
> {
> const unsigned long mask[] = { BITMAP_FROM_U64(val) };
> - const char *str;
> int bit, index;
>
> for_each_set_bit(bit, mask, bits) {
> + const char *str = NULL;
> +
> if (bit < PLR_COARSE_REASON_BITS) {
> if (bit < ARRAY_SIZE(plr_coarse_reasons))
> str = plr_coarse_reasons[bit];
>
prev parent reply other threads:[~2024-07-16 10:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-15 20:22 Dan Carpenter
2024-07-16 10:05 ` Ilpo Järvinen [this message]
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=9c74d6ac-56e4-a79b-6d05-705a17561a3d@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=dan.carpenter@linaro.org \
--cc=hdegoede@redhat.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=tero.kristo@linux.intel.com \
/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®