From: Sergey Shtylyov <s.shtylyov@auroraos.dev>
To: 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>,
<linux-usb@vger.kernel.org>, <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next RFT] ch9200: return error on failed register writes in ch9200_bind()
Date: Tue, 8 Sep 2026 22:52:46 +0300 [thread overview]
Message-ID: <faca06b3-0d16-4add-b2cd-2b87ce2d3710@auroraos.dev> (raw)
In-Reply-To: <20260903201842.62338-1-s.shtylyov@auroraos.dev>
On 9/3/26 11:18 PM, Sergey Shtylyov wrote:
> The successful register writes, done via the USB control requests in
> control_write(), seem vital for the normal functioning of the device,
> however the driver's bind() method ignores error codes returned from
> control_write(). Do bail out of ch9200_bind() on failed writes...
>
> Found by Linux Verification Center (linuxtesting.org) with the Svace
> static analysis tool.
>
> Signed-off-by: Sergey Shtylyov <s.shtylyov@auroraos.dev>
Scratch this patch, I was sloppy... :-)
[...]
> diff --git a/drivers/net/usb/ch9200.c b/drivers/net/usb/ch9200.c
> index a206ffa76f1b..ce2e62f85c3d 100644
> --- a/drivers/net/usb/ch9200.c
> +++ b/drivers/net/usb/ch9200.c
> @@ -360,32 +360,44 @@ static int ch9200_bind(struct usbnet *dev, struct usb_interface *intf)
> data[1] = 0x0F;
> retval = control_write(dev, REQUEST_WRITE, 0, MAC_REG_THRESHOLD, data,
> 0x02, CONTROL_TIMEOUT_MS);
> + if (retval)
Should be (retval < 0) here an below, as Sashiko pointed out.
[...]
MBR, Sergey
prev parent reply other threads:[~2026-09-08 19:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 20:18 [PATCH net-next RFT] ch9200: return error on failed register writes in ch9200_bind() Sergey Shtylyov
2026-09-08 19:52 ` Sergey Shtylyov [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=faca06b3-0d16-4add-b2cd-2b87ce2d3710@auroraos.dev \
--to=s.shtylyov@auroraos.dev \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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