From: Mathias Nyman <mathias.nyman@linux.intel.com>
To: <gregkh@linuxfoundation.org>
Cc: <linux-usb@vger.kernel.org>,
Mathias Nyman <mathias.nyman@linux.intel.com>
Subject: [PATCH 0/4] xhci features for usb-next
Date: Tue, 6 Apr 2021 10:02:04 +0300 [thread overview]
Message-ID: <20210406070208.3406266-1-mathias.nyman@linux.intel.com> (raw)
Hi Greg
I saw you already picked the Mediatek xhci patches.
Here are a few additional patches I had pending for usb-next
but didn't get around to submit before easter.
Mostly fixing potential issues found by fuzzer and other tools.
Thanks
-Mathias
Mathias Nyman (4):
xhci: check port array allocation was successful before dereferencing
it
xhci: check control context is valid before dereferencing it.
xhci: fix potential array out of bounds with several interrupters
xhci: prevent double-fetch of transfer and transfer event TRBs
drivers/usb/host/xhci-mem.c | 3 +++
drivers/usb/host/xhci-ring.c | 42 ++++++++++++++++--------------------
drivers/usb/host/xhci.c | 14 +++++++++++-
3 files changed, 35 insertions(+), 24 deletions(-)
--
2.25.1
next reply other threads:[~2021-04-06 7:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-06 7:02 Mathias Nyman [this message]
2021-04-06 7:02 ` [PATCH 1/4] xhci: check port array allocation was successful before dereferencing it Mathias Nyman
2021-04-06 7:02 ` [PATCH 2/4] xhci: check control context is valid " Mathias Nyman
2021-04-06 7:02 ` [PATCH 3/4] xhci: fix potential array out of bounds with several interrupters Mathias Nyman
2021-04-06 7:02 ` [PATCH 4/4] xhci: prevent double-fetch of transfer and transfer event TRBs Mathias Nyman
-- strict thread matches above, loose matches on Subject: below --
2021-06-17 15:03 [PATCH 0/4] xhci features for usb-next Mathias Nyman
2021-06-17 15:34 ` Greg KH
2019-11-15 16:49 Mathias Nyman
2019-08-30 13:39 Mathias Nyman
2019-04-26 13:23 Mathias Nyman
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=20210406070208.3406266-1-mathias.nyman@linux.intel.com \
--to=mathias.nyman@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.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 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.