From: Aditya Chari S <adi25charis@gmail.com>
To: Johan Hovold <johan@kernel.org>, Alex Elder <elder@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: greybus-dev@lists.linaro.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org,
Aditya Chari S <adi25charis@gmail.com>
Subject: [PATCH] greybus: usb: fix response buffer size for fixed-length hub requests
Date: Mon, 3 Aug 2026 06:32:48 +0530 [thread overview]
Message-ID: <20260803010248.339120-1-adi25charis@gmail.com> (raw)
hub_control() sized the Greybus operation's response buffer purely
off the caller-supplied wLength. However, per the USB hub class spec,
GetHubDescriptor, GetHubStatus, and GetPortStatus have a response
length that is fixed by the request type itself, and can be larger
than (or independent of) whatever wLength the USB core happens to
pass down. This could under-allocate the response buffer for these
request types.
Special-case these three request types so the response buffer is
always large enough for the data the module will actually send back,
matching the equivalent handling in usbcore's rh_call_control(). Fall
back to wLength for all other request types, as before.
Compile-tested with 'make M=drivers/staging/greybus C=1', including
sparse, with no warnings. checkpatch --strict is also clean.
Note: this driver's hub_control() is currently unreachable at runtime
since gb_usb_probe() unconditionally disables USB support pending
separate USB core changes. As Project Ara hardware is no longer
available, this change has not been tested on physical hardware or
with a Greybus module; it was verified only by compilation, sparse,
and code review against the equivalent logic in usbcore.
Signed-off-by: Aditya Chari S <adi25charis@gmail.com>
---
drivers/staging/greybus/usb.c | 31 +++++++++++++++++++++++++++----
1 file changed, 27 insertions(+), 4 deletions(-)
diff --git a/drivers/staging/greybus/usb.c b/drivers/staging/greybus/usb.c
index 475f24f20..ea6c0800c 100644
--- a/drivers/staging/greybus/usb.c
+++ b/drivers/staging/greybus/usb.c
@@ -105,8 +105,29 @@ static int hub_control(struct usb_hcd *hcd, u16 typeReq, u16 wValue, u16 wIndex,
size_t response_size;
int ret;
- /* FIXME: handle unspecified lengths */
- response_size = sizeof(*response) + wLength;
+ /*
+ * Several USB hub class requests have a response length that is
+ * fixed by the request type rather than by wLength (which may be
+ * zero, or otherwise smaller than the actual data the module will
+ * return). Make sure we always allocate enough room for those.
+ */
+ switch (typeReq) {
+ case GetHubDescriptor:
+ response_size = sizeof(*response) +
+ sizeof(struct usb_hub_descriptor);
+ break;
+ case GetHubStatus:
+ response_size = sizeof(*response) +
+ sizeof(struct usb_hub_status);
+ break;
+ case GetPortStatus:
+ response_size = sizeof(*response) +
+ sizeof(struct usb_port_status);
+ break;
+ default:
+ response_size = sizeof(*response) + wLength;
+ break;
+ }
operation = gb_operation_create(dev->connection,
GB_USB_TYPE_HUB_CONTROL,
@@ -126,10 +147,12 @@ static int hub_control(struct usb_hcd *hcd, u16 typeReq, u16 wValue, u16 wIndex,
if (ret)
goto out;
- if (wLength) {
+ if (response_size > sizeof(*response)) {
+ size_t data_size = response_size - sizeof(*response);
+
/* Greybus core has verified response size */
response = operation->response->payload;
- memcpy(buf, response->buf, wLength);
+ memcpy(buf, response->buf, data_size);
}
out:
gb_operation_put(operation);
--
2.53.0
next reply other threads:[~2026-08-08 4:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-03 1:02 Aditya Chari S [this message]
2026-08-08 5:46 ` [PATCH] greybus: usb: fix response buffer size for fixed-length hub requests Greg Kroah-Hartman
2026-08-08 8:19 ` Dan Carpenter
2026-08-03 23:51 ` Aditya Chari S
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=20260803010248.339120-1-adi25charis@gmail.com \
--to=adi25charis@gmail.com \
--cc=elder@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=greybus-dev@lists.linaro.org \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
/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