From: Liam Merwick <liam.merwick@oracle.com>
To: kraxel@redhat.com, qemu-devel@nongnu.org
Cc: liam.merwick@oracle.com, Darren.Kenny@oracle.com,
Mark.Kanda@oracle.com, ameya.more@oracle.com
Subject: [Qemu-devel] [PATCH 1/2] usb: rearrange usb_ep_get()
Date: Wed, 30 Jan 2019 14:37:01 +0000 [thread overview]
Message-ID: <1548859022-3969-2-git-send-email-liam.merwick@oracle.com> (raw)
In-Reply-To: <1548859022-3969-1-git-send-email-liam.merwick@oracle.com>
There is no need to calculate the 'eps' variable in usb_ep_get()
if 'ep' is the control endpoint. Instead the calculation should
be done after validating the input and the resulting pointer also
validated before returning an entry indexed on the endpoint 'ep'.
Signed-off-by: Liam Merwick <liam.merwick@oracle.com>
Reviewed-by: Darren Kenny <Darren.Kenny@oracle.com>
Reviewed-by: Mark Kanda <Mark.Kanda@oracle.com>
Reviewed-by: Ameya More <ameya.more@oracle.com>
---
hw/usb/core.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/hw/usb/core.c b/hw/usb/core.c
index 241ae66b1505..1aa0051b2b2d 100644
--- a/hw/usb/core.c
+++ b/hw/usb/core.c
@@ -720,12 +720,13 @@ struct USBEndpoint *usb_ep_get(USBDevice *dev, int pid, int ep)
if (dev == NULL) {
return NULL;
}
- eps = (pid == USB_TOKEN_IN) ? dev->ep_in : dev->ep_out;
if (ep == 0) {
return &dev->ep_ctl;
}
assert(pid == USB_TOKEN_IN || pid == USB_TOKEN_OUT);
assert(ep > 0 && ep <= USB_MAX_ENDPOINTS);
+ eps = (pid == USB_TOKEN_IN) ? dev->ep_in : dev->ep_out;
+ assert(eps != NULL);
return eps + ep - 1;
}
--
1.8.3.1
next prev parent reply other threads:[~2019-01-30 14:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-30 14:37 [Qemu-devel] [PATCH 0/2] USB static analysis patches Liam Merwick
2019-01-30 14:37 ` Liam Merwick [this message]
2019-01-31 7:59 ` [Qemu-devel] [PATCH 1/2] usb: rearrange usb_ep_get() Gerd Hoffmann
2019-01-30 14:37 ` [Qemu-devel] [PATCH 2/2] usb: deal with potential Null pointer returned by usb_ep_get() Liam Merwick
2019-01-31 8:03 ` Gerd Hoffmann
2019-02-04 11:50 ` Liam Merwick
2019-02-05 8:36 ` Gerd Hoffmann
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=1548859022-3969-2-git-send-email-liam.merwick@oracle.com \
--to=liam.merwick@oracle.com \
--cc=Darren.Kenny@oracle.com \
--cc=Mark.Kanda@oracle.com \
--cc=ameya.more@oracle.com \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).