From: Eli Billauer <eli.billauer@gmail.com>
To: Zheyu Ma <zheyuma97@gmail.com>
Cc: arnd@arndb.de, gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] char: xillybus: Check endpoint type before allocing
Date: Sat, 14 May 2022 15:52:20 +0300 [thread overview]
Message-ID: <627FA604.2010302@gmail.com> (raw)
In-Reply-To: <20220514114819.2773691-1-zheyuma97@gmail.com>
On 14/05/22 14:48, Zheyu Ma wrote:
> The driver submits bulk urb without checking the endpoint type is
> actually bulk.
>
> [ 3.108690] usb 1-1: BOGUS urb xfer, pipe 3 != type 1
> [ 3.108983] WARNING: CPU: 0 PID: 211 at drivers/usb/core/urb.c:503 usb_submit_urb+0xcd9/0x18b0
> [ 3.110976] RIP: 0010:usb_submit_urb+0xcd9/0x18b0
> [ 3.115318] Call Trace:
> [ 3.115452]<TASK>
> [ 3.115570] try_queue_bulk_in+0x43c/0x6e0 [xillyusb]
> [ 3.115838] xillyusb_probe+0x488/0x1230 [xillyusb]
>
> Add a check in endpoint_alloc() to fix the bug.
>
> Signed-off-by: Zheyu Ma<zheyuma97@gmail.com>
> ---
> Changes in v2:
> - Check the endpoint type at probe time
> ---
> drivers/char/xillybus/xillyusb.c | 27 ++++++++++++++++++++++++++-
> 1 file changed, 26 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/char/xillybus/xillyusb.c b/drivers/char/xillybus/xillyusb.c
> index dc3551796e5e..4467f13993ef 100644
> --- a/drivers/char/xillybus/xillyusb.c
> +++ b/drivers/char/xillybus/xillyusb.c
> @@ -167,6 +167,7 @@ struct xillyusb_dev {
> struct device *dev; /* For dev_err() and such */
> struct kref kref;
> struct workqueue_struct *workq;
> + struct usb_interface *intf;
>
> int error;
> spinlock_t error_lock; /* protect @error */
> @@ -475,6 +476,25 @@ static void endpoint_dealloc(struct xillyusb_endpoint *ep)
> kfree(ep);
> }
>
> +static int xillyusb_check_endpoint(struct xillyusb_dev *xdev, u8 ep_num)
> +{
> + struct usb_host_interface *if_desc = xdev->intf->altsetting;
> + int i;
> +
> + for (i = 0; i< if_desc->desc.bNumEndpoints; i++) {
> + struct usb_endpoint_descriptor *ep =&if_desc->endpoint[i].desc;
> +
> + if (ep->bEndpointAddress != ep_num)
> + continue;
> +
> + if ((usb_pipein(ep_num)&& usb_endpoint_is_bulk_in(ep)) ||
> + (usb_pipeout(ep_num)&& usb_endpoint_is_bulk_out(ep)))
> + return 0;
> + }
> +
> + return -EINVAL;
> +}
> +
> static struct xillyusb_endpoint
> *endpoint_alloc(struct xillyusb_dev *xdev,
> u8 ep_num,
> @@ -482,10 +502,14 @@ static struct xillyusb_endpoint
> unsigned int order,
> int bufnum)
> {
> - int i;
> + int i, ret;
>
> struct xillyusb_endpoint *ep;
>
> + ret = xillyusb_check_endpoint(xdev, ep_num);
> + if (ret)
> + return NULL;
> +
> ep = kzalloc(sizeof(*ep), GFP_KERNEL);
>
> if (!ep)
> @@ -2125,6 +2149,7 @@ static int xillyusb_probe(struct usb_interface *interface,
> mutex_init(&xdev->process_in_mutex);
> mutex_init(&xdev->msg_mutex);
>
> + xdev->intf = interface;
> xdev->udev = usb_get_dev(interface_to_usbdev(interface));
> xdev->dev =&interface->dev;
> xdev->error = 0;
>
I wonder why this check is necessary. The XillyUSB device presents bulk
endpoints only, and the driver never tries anything else.
Actually, if this warning appears in a real-life scenario, it definitely
indicates a serious problem. So I think the warning should be visible,
rather than silenced like this.
I realize that a code sanitizer has been triggered, but is there more to
this?
Thanks,
Eli
next prev parent reply other threads:[~2022-05-14 12:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-14 7:14 [PATCH] char: xillybus: Check endpoint type properly Zheyu Ma
2022-05-14 7:18 ` Greg KH
2022-05-14 11:48 ` [PATCH v2] char: xillybus: Check endpoint type before allocing Zheyu Ma
2022-05-14 12:52 ` Eli Billauer [this message]
2022-05-14 13:24 ` Greg KH
2022-05-14 13:32 ` Greg KH
2022-05-20 3:32 ` Zheyu Ma
2022-05-20 5:41 ` Greg KH
2022-05-22 5:06 ` Zheyu Ma
2022-05-23 16:06 ` Greg KH
2022-05-23 17:05 ` Eli Billauer
2022-05-23 17:15 ` Greg KH
2022-05-24 12:23 ` Eli Billauer
2022-05-26 12:02 ` Zheyu Ma
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=627FA604.2010302@gmail.com \
--to=eli.billauer@gmail.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zheyuma97@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.