From: Johan Hovold <johan@kernel.org>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Oliver Neukum <oneukum@suse.com>,
Anirudh Rayabharam <mail@anirudhrb.com>,
Zheng Yongjun <zhengyongjun3@huawei.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Emil Renner Berthing <kernel@esmil.dk>,
Rustam Kovhaev <rkovhaev@gmail.com>,
linux-usb@vger.kernel.org, netdev@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH v2 net] net: hso: check for allocation failure in hso_create_bulk_serial_device()
Date: Mon, 17 May 2021 10:07:25 +0200 [thread overview]
Message-ID: <YKIkPS/RNh32i042@hovoldconsulting.com> (raw)
In-Reply-To: <YJ6IMH7jI9QFdGIX@mwanda>
On Fri, May 14, 2021 at 05:24:48PM +0300, Dan Carpenter wrote:
> In current kernels, small allocations never actually fail so this
> patch shouldn't affect runtime.
>
> Originally this error handling code written with the idea that if
> the "serial->tiocmget" allocation failed, then we would continue
> operating instead of bailing out early. But in later years we added
> an unchecked dereference on the next line.
>
> serial->tiocmget->serial_state_notification = kzalloc();
> ^^^^^^^^^^^^^^^^^^
>
> Since these allocations are never going fail in real life, this is
> mostly a philosophical debate, but I think bailing out early is the
> correct behavior that the user would want. And generally it's safer to
> bail as soon an error happens.
>
> Fixes: af0de1303c4e ("usb: hso: obey DMA rules in tiocmget")
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
> ---
> v2: Do more extensive clean up. As Johan pointed out the comments and
> later NULL checks can be removed.
>
> drivers/net/usb/hso.c | 37 ++++++++++++++++++-------------------
> 1 file changed, 18 insertions(+), 19 deletions(-)
>
> diff --git a/drivers/net/usb/hso.c b/drivers/net/usb/hso.c
> index 3ef4b2841402..260f850d69eb 100644
> --- a/drivers/net/usb/hso.c
> +++ b/drivers/net/usb/hso.c
> @@ -2618,29 +2618,28 @@ static struct hso_device *hso_create_bulk_serial_device(
> num_urbs = 2;
> serial->tiocmget = kzalloc(sizeof(struct hso_tiocmget),
> GFP_KERNEL);
> + if (!serial->tiocmget)
> + goto exit;
> serial->tiocmget->serial_state_notification
> = kzalloc(sizeof(struct hso_serial_state_notification),
> GFP_KERNEL);
> - /* it isn't going to break our heart if serial->tiocmget
> - * allocation fails don't bother checking this.
> - */
> - if (serial->tiocmget && serial->tiocmget->serial_state_notification) {
> - tiocmget = serial->tiocmget;
> - tiocmget->endp = hso_get_ep(interface,
> - USB_ENDPOINT_XFER_INT,
> - USB_DIR_IN);
> - if (!tiocmget->endp) {
> - dev_err(&interface->dev, "Failed to find INT IN ep\n");
> - goto exit;
> - }
> -
> - tiocmget->urb = usb_alloc_urb(0, GFP_KERNEL);
> - if (tiocmget->urb) {
> - mutex_init(&tiocmget->mutex);
> - init_waitqueue_head(&tiocmget->waitq);
> - } else
> - hso_free_tiomget(serial);
> + if (!serial->tiocmget->serial_state_notification)
> + goto exit;
> + tiocmget = serial->tiocmget;
> + tiocmget->endp = hso_get_ep(interface,
> + USB_ENDPOINT_XFER_INT,
> + USB_DIR_IN);
> + if (!tiocmget->endp) {
> + dev_err(&interface->dev, "Failed to find INT IN ep\n");
> + goto exit;
> }
> +
> + tiocmget->urb = usb_alloc_urb(0, GFP_KERNEL);
> + if (tiocmget->urb) {
> + mutex_init(&tiocmget->mutex);
> + init_waitqueue_head(&tiocmget->waitq);
> + } else
> + hso_free_tiomget(serial);
This should probably be changed to bail out on allocation errors as well
now but that can be done as a follow-up. Either way:
Reviewed-by: Johan Hovold <johan@kernel.org>
> }
> else
> num_urbs = 1;
Johan
next prev parent reply other threads:[~2021-05-17 8:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-12 10:09 [PATCH net] net: hso: check for allocation failure in hso_create_bulk_serial_device() Dan Carpenter
2021-05-12 10:19 ` Johan Hovold
2021-05-12 13:12 ` Dan Carpenter
2021-05-14 14:24 ` [PATCH v2 " Dan Carpenter
2021-05-17 8:07 ` Johan Hovold [this message]
2021-05-17 21:00 ` 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=YKIkPS/RNh32i042@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=dan.carpenter@oracle.com \
--cc=davem@davemloft.net \
--cc=geert@linux-m68k.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=kernel@esmil.dk \
--cc=kuba@kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mail@anirudhrb.com \
--cc=netdev@vger.kernel.org \
--cc=oneukum@suse.com \
--cc=rkovhaev@gmail.com \
--cc=zhengyongjun3@huawei.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;
as well as URLs for NNTP newsgroup(s).