From: Johan Hovold <johan@kernel.org>
To: trix@redhat.com
Cc: johan@kernel.org, gregkh@linuxfoundation.org,
natechancellor@gmail.com, ndesaulniers@google.com,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
clang-built-linux@googlegroups.com
Subject: Re: [PATCH] USB: serial: mos7720: improve handling of a kmalloc failure in read_mos_reg()
Date: Tue, 12 Jan 2021 09:57:31 +0100 [thread overview]
Message-ID: <X/1ke4/PaRQRGJTg@hovoldconsulting.com> (raw)
In-Reply-To: <20210111220904.1035957-1-trix@redhat.com>
On Mon, Jan 11, 2021 at 02:09:04PM -0800, trix@redhat.com wrote:
> From: Tom Rix <trix@redhat.com>
>
> clang static analysis reports this problem
>
> mos7720.c:352:2: warning: Undefined or garbage value returned to caller
> return d;
> ^~~~~~~~
>
> In the parport_mos7715_read_data()'s call to read_mos_reg(), 'd' is
> only set after the alloc block.
>
> buf = kmalloc(1, GFP_KERNEL);
> if (!buf)
> return -ENOMEM;
>
> Although the problem is reported in parport_most7715_read_data(),
> none of the callee's of read_mos_reg() check the return status.
>
> So move the clearing of data to before the malloc.
>
> Fixes: 0d130367abf5 ("USB: serial: mos7720: fix control-message error handling")
> Signed-off-by: Tom Rix <trix@redhat.com>
> ---
> drivers/usb/serial/mos7720.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/usb/serial/mos7720.c b/drivers/usb/serial/mos7720.c
> index 41ee2984a0df..23e8162c768b 100644
> --- a/drivers/usb/serial/mos7720.c
> +++ b/drivers/usb/serial/mos7720.c
> @@ -214,6 +214,7 @@ static int read_mos_reg(struct usb_serial *serial, unsigned int serial_portnum,
> u8 *buf;
> int status;
>
> + *data = 0;
> buf = kmalloc(1, GFP_KERNEL);
> if (!buf)
> return -ENOMEM;
I added a clearing of the buffer to this error path instead to avoid the
redundant assignment for every call due to something which will
basically never happen.
> @@ -227,7 +228,6 @@ static int read_mos_reg(struct usb_serial *serial, unsigned int serial_portnum,
> "mos7720: usb_control_msg() failed: %d\n", status);
> if (status >= 0)
> status = -EIO;
> - *data = 0;
> }
>
> kfree(buf);
Johan
prev parent reply other threads:[~2021-01-12 8:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-11 22:09 trix
2021-01-11 22:31 ` Nathan Chancellor
2021-01-12 8:57 ` Johan Hovold [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=X/1ke4/PaRQRGJTg@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=clang-built-linux@googlegroups.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=natechancellor@gmail.com \
--cc=ndesaulniers@google.com \
--cc=trix@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
all inboxes | Powered by JetHome®