From: "Colin King (gmail)" <colin.i.king@gmail.com>
To: Alexander Antonov <alexander.antonov@linux.intel.com>
Cc: linux-perf-users@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: potential return of uninitialized variable ret in function skx_upi_topology_cb
Date: Thu, 27 Jul 2023 14:55:00 +0100 [thread overview]
Message-ID: <21e2ea66-9524-8e34-a2f0-8e16b9617d68@gmail.com> (raw)
Hi,
Static analysis with cppcheck has detected a potential return of an
uninitialized variable in function skx_upi_topology_cb. The issue was
introduced with commit:
commit 4cfce57fa42d277497cd2c425021312eae2f223c
Author: Alexander Antonov <alexander.antonov@linux.intel.com>
Date: Thu Nov 17 12:28:28 2022 +0000
perf/x86/intel/uncore: Enable UPI topology discovery for Skylake Server
static int skx_upi_topology_cb(struct intel_uncore_type *type, int segment,
int die, u64 cpu_bus_msr)
{
int idx, ret;
^^ ret is not initialized
struct intel_uncore_topology *upi;
unsigned int devfn;
struct pci_dev *dev = NULL;
u8 bus = cpu_bus_msr >> (3 * BUS_NUM_STRIDE);
for (idx = 0; idx < type->num_boxes; idx++) {
upi = &type->topology[die][idx];
devfn = PCI_DEVFN(SKX_UPI_REGS_ADDR_DEVICE_LINK0 + idx,
SKX_UPI_REGS_ADDR_FUNCTION);
dev = pci_get_domain_bus_and_slot(segment, bus, devfn);
^^ dev may be null, so ret is never assigned
if (dev) {
ret = upi_fill_topology(dev, upi, idx);
if (ret)
break;
}
}
pci_dev_put(dev);
return ret;
}
I suspect this probably is very unlikely, but it would be useful to have
ret initialized to some value to avoid garbage being returned. Not sure
what the best value is to set as as default in this corner case.
Colin
next reply other threads:[~2023-07-27 13:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-27 13:55 Colin King (gmail) [this message]
2023-07-31 14:02 ` potential return of uninitialized variable ret in function skx_upi_topology_cb Alexander Antonov
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=21e2ea66-9524-8e34-a2f0-8e16b9617d68@gmail.com \
--to=colin.i.king@gmail.com \
--cc=alexander.antonov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.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;
as well as URLs for NNTP newsgroup(s).