From: Shigeru Yoshida <syoshida@redhat.com>
To: make24@iscas.ac.cn
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, liujunliang_ljl@163.com, andrew@lunn.ch,
horms@kernel.org, linux-usb@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH net v4] net: usb: sr9700: fix uninitialized variable use in sr_mdio_read
Date: Thu, 25 Jul 2024 12:01:00 +0900 (JST) [thread overview]
Message-ID: <20240725.120100.2041590414991833213.syoshida@redhat.com> (raw)
In-Reply-To: <20240725022942.1720199-1-make24@iscas.ac.cn>
On Thu, 25 Jul 2024 10:29:42 +0800, Ma Ke wrote:
> It could lead to error happen because the variable res is not updated if
> the call to sr_share_read_word returns an error. In this particular case
> error code was returned and res stayed uninitialized. Same issue also
> applies to sr_read_reg.
>
> This can be avoided by checking the return value of sr_share_read_word
> and sr_read_reg, and propagating the error if the read operation failed.
>
> Found by code review.
>
> Cc: stable@vger.kernel.org
> Fixes: c9b37458e956 ("USB2NET : SR9700 : One chip USB 1.1 USB2NET SR9700Device Driver Support")
> Signed-off-by: Ma Ke <make24@iscas.ac.cn>
I did a quick check for sr9700.c and there seems to be other
suspicious usage of sr_read_reg(). But, for sr_mdio_read(), I think
the patch is sufficient.
Reviewed-by: Shigeru Yoshida <syoshida@redhat.com>
> ---
> Changes in v4:
> - added a check for sr_read_reg() as suggestions.
> Changes in v3:
> - added Cc stable line as suggestions.
> Changes in v2:
> - modified the subject as suggestions.
> ---
> drivers/net/usb/sr9700.c | 11 +++++++++--
> 1 file changed, 9 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/net/usb/sr9700.c b/drivers/net/usb/sr9700.c
> index 0a662e42ed96..cb7d2f798fb4 100644
> --- a/drivers/net/usb/sr9700.c
> +++ b/drivers/net/usb/sr9700.c
> @@ -179,6 +179,7 @@ static int sr_mdio_read(struct net_device *netdev, int phy_id, int loc)
> struct usbnet *dev = netdev_priv(netdev);
> __le16 res;
> int rc = 0;
> + int err;
>
> if (phy_id) {
> netdev_dbg(netdev, "Only internal phy supported\n");
> @@ -189,11 +190,17 @@ static int sr_mdio_read(struct net_device *netdev, int phy_id, int loc)
> if (loc == MII_BMSR) {
> u8 value;
>
> - sr_read_reg(dev, SR_NSR, &value);
> + err = sr_read_reg(dev, SR_NSR, &value);
> + if (err < 0)
> + return err;
> +
> if (value & NSR_LINKST)
> rc = 1;
> }
> - sr_share_read_word(dev, 1, loc, &res);
> + err = sr_share_read_word(dev, 1, loc, &res);
> + if (err < 0)
> + return err;
> +
> if (rc == 1)
> res = le16_to_cpu(res) | BMSR_LSTATUS;
> else
> --
> 2.25.1
>
next prev parent reply other threads:[~2024-07-25 3:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-25 2:29 [PATCH net v4] net: usb: sr9700: fix uninitialized variable use in sr_mdio_read Ma Ke
2024-07-25 3:01 ` Shigeru Yoshida [this message]
2024-07-25 8:06 ` Hariprasad Kelam
2024-07-26 10:20 ` patchwork-bot+netdevbpf
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=20240725.120100.2041590414991833213.syoshida@redhat.com \
--to=syoshida@redhat.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=liujunliang_ljl@163.com \
--cc=make24@iscas.ac.cn \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stable@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