From: Shuah Khan <shuah@kernel.org>
To: Michael Grzeschik <m.grzeschik@pengutronix.de>,
linux-usb@vger.kernel.org
Cc: valentina.manea.m@gmail.com, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org, kernel@pengutronix.de,
Shuah Khan <shuah@kernel.org>
Subject: Re: [PATCH] usbip: dynamically allocate idev by nports found in sysfs
Date: Tue, 22 May 2018 10:06:27 -0600 [thread overview]
Message-ID: <05a0fd16-cd54-1bb8-7566-0d88e1bd73cf@kernel.org> (raw)
In-Reply-To: <20180518143947.27963-1-m.grzeschik@pengutronix.de>
Hi Michael,
Thanks for the patch. Couple of comments below:
On 05/18/2018 08:39 AM, Michael Grzeschik wrote:
> As the amount of available ports varies by the kernels build
> configuration. To remove the limitation of the fixed 128 ports
> we allocate the amount of idevs by using the number we get
> from the kernel.
>
> Signed-off-by: Michael Grzeschik <m.grzeschik@pengutronix.de>
> ---
> tools/usb/usbip/libsrc/vhci_driver.c | 11 ++++++++---
> tools/usb/usbip/libsrc/vhci_driver.h | 3 +--
> 2 files changed, 9 insertions(+), 5 deletions(-)
>
> diff --git a/tools/usb/usbip/libsrc/vhci_driver.c b/tools/usb/usbip/libsrc/vhci_driver.c
> index c9c81614a66ad..9a8acfc7697fa 100644
> --- a/tools/usb/usbip/libsrc/vhci_driver.c
> +++ b/tools/usb/usbip/libsrc/vhci_driver.c
> @@ -266,11 +266,11 @@ int usbip_vhci_driver_open(void)
> if (vhci_driver->nports <= 0) {
> err("no available ports");
> goto err;
> - } else if (vhci_driver->nports > MAXNPORT) {
> - err("port number exceeds %d", MAXNPORT);
> - goto err;
> }
>
> + vhci_driver->idev = calloc(vhci_driver->nports,
> + sizeof(struct usbip_imported_device));
> +
Missing check for memory allocation failure. Please add it.
> vhci_driver->ncontrollers = get_ncontrollers();
> dbg("available controllers: %d", vhci_driver->ncontrollers);
>
> @@ -287,6 +287,9 @@ int usbip_vhci_driver_open(void)
> err:
> udev_device_unref(vhci_driver->hc_device);
>
> + if (vhci_driver->idev)
> + free(vhci_driver->idev);
> +
> if (vhci_driver)
> free(vhci_driver);
>
> @@ -305,6 +308,8 @@ void usbip_vhci_driver_close(void)
>
> udev_device_unref(vhci_driver->hc_device);
>
> + free(vhci_driver->idev);
> +
> free(vhci_driver);
>
> vhci_driver = NULL;
> diff --git a/tools/usb/usbip/libsrc/vhci_driver.h b/tools/usb/usbip/libsrc/vhci_driver.h
> index 418b404d51210..67dbd1551e159 100644
> --- a/tools/usb/usbip/libsrc/vhci_driver.h
> +++ b/tools/usb/usbip/libsrc/vhci_driver.h
> @@ -13,7 +13,6 @@
>
> #define USBIP_VHCI_BUS_TYPE "platform"
> #define USBIP_VHCI_DEVICE_NAME "vhci_hcd.0"
> -#define MAXNPORT 128
>
> enum hub_speed {
> HUB_SPEED_HIGH = 0,
> @@ -41,7 +40,7 @@ struct usbip_vhci_driver {
>
> int ncontrollers;
> int nports;
> - struct usbip_imported_device idev[MAXNPORT];
> + struct usbip_imported_device *idev;
> };
>
>
>
Rest looks good.
thanks,
-- Shuah
next prev parent reply other threads:[~2018-05-22 16:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-18 14:39 Michael Grzeschik
2018-05-22 16:06 ` Shuah Khan [this message]
2018-05-22 17:04 ` [PATCH v2] " Michael Grzeschik
2018-05-22 22:56 ` Shuah Khan
2018-05-23 9:22 ` [PATCH v3] " Michael Grzeschik
2018-05-23 16:44 ` Shuah Khan
2018-05-23 21:01 ` Michael Grzeschik
2018-05-24 7:34 ` Michael Grzeschik
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=05a0fd16-cd54-1bb8-7566-0d88e1bd73cf@kernel.org \
--to=shuah@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=m.grzeschik@pengutronix.de \
--cc=valentina.manea.m@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®