From: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
To: Roshan Khatri <topofeverest8848@gmail.com>
Cc: Michael Chan <michael.chan@broadcom.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: b44: uninitialized variable in multiple places in b44.c
Date: Thu, 19 Dec 2024 07:33:39 +0100 [thread overview]
Message-ID: <Z2O+Q5Qp1R5KdMbg@mev-dev.igk.intel.com> (raw)
In-Reply-To: <20241219043410.1912288-1-topofeverest8848@gmail.com>
On Thu, Dec 19, 2024 at 04:34:10AM +0000, Roshan Khatri wrote:
> smatch reported uninitialized variable in multiples places in b44.c.
> This patch fixes the uniinitialized variable errors in multiple places
> reported by smatch.
>
You need fixes tag with the commit that introduced the issue when
targetting net. Like here for example [1]
[1] https://lore.kernel.org/netdev/CANn89i+yvyPMU1SE=p3Mm1S=UexsXSa4gzH3heUg17sa+iFK9w@mail.gmail.com/T/#t
> Signed-off-by: Roshan Khatri <topofeverest8848@gmail.com>
> ---
> drivers/net/ethernet/broadcom/b44.c | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/net/ethernet/broadcom/b44.c b/drivers/net/ethernet/broadcom/b44.c
> index e5809ad5eb82..9a466c5c4b6c 100644
> --- a/drivers/net/ethernet/broadcom/b44.c
> +++ b/drivers/net/ethernet/broadcom/b44.c
> @@ -314,7 +314,7 @@ static int b44_mdio_write_phylib(struct mii_bus *bus, int phy_id, int location,
>
> static int b44_phy_reset(struct b44 *bp)
> {
> - u32 val;
> + u32 val = 0;
> int err;
>
> if (bp->flags & B44_FLAG_EXTERNAL_PHY)
> @@ -414,7 +414,7 @@ static inline void b44_wap54g10_workaround(struct b44 *bp)
>
> static int b44_setup_phy(struct b44 *bp)
> {
> - u32 val;
> + u32 val = 0;
> int err;
>
> b44_wap54g10_workaround(bp);
> @@ -512,7 +512,7 @@ static void b44_link_report(struct b44 *bp)
>
> static void b44_check_phy(struct b44 *bp)
> {
> - u32 bmsr, aux;
> + u32 bmsr = 0, aux = 0;
>
> if (bp->flags & B44_FLAG_EXTERNAL_PHY) {
> bp->flags |= B44_FLAG_100_BASE_T;
> @@ -544,7 +544,7 @@ static void b44_check_phy(struct b44 *bp)
> if (!netif_carrier_ok(bp->dev) &&
> (bmsr & BMSR_LSTATUS)) {
> u32 val = br32(bp, B44_TX_CTRL);
> - u32 local_adv, remote_adv;
> + u32 local_adv = 0, remote_adv = 0;
This two are real problems, because if the flag isn't clear, or first
read fails the variables won't be initialized when used.
>
> if (bp->flags & B44_FLAG_FULL_DUPLEX)
> val |= TX_CTRL_DUPLEX;
> @@ -1786,7 +1786,7 @@ static void b44_get_drvinfo (struct net_device *dev, struct ethtool_drvinfo *inf
> static int b44_nway_reset(struct net_device *dev)
> {
> struct b44 *bp = netdev_priv(dev);
> - u32 bmcr;
> + u32 bmcr = 0;
The rest doesn't look like unitialized, you passing a pointer and
filling it with a value. Can't see the branch when the value is left
without filling, but maybe I don't see something obvious.
BTW, you have many "incorrect type in assignment" in cnic.c file.
Thanks
> int r;
>
> spin_lock_irq(&bp->lock);
> --
> 2.34.1
prev parent reply other threads:[~2024-12-19 6:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-19 4:34 Roshan Khatri
2024-12-19 6:33 ` Michal Swiatkowski [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=Z2O+Q5Qp1R5KdMbg@mev-dev.igk.intel.com \
--to=michal.swiatkowski@linux.intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=topofeverest8848@gmail.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®