From: Jameson Thies <jthies@google.com>
To: heikki.krogerus@linux.intel.com, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: bleung@chromium.org, gregkh@linuxfoundation.org,
akuchynski@chromium.org, Jameson Thies <jthies@google.com>
Subject: [PATCH v1 0/2] Cleanup UCSI DisplayPort OOB fix
Date: Thu, 10 Sep 2026 23:35:51 +0000 [thread overview]
Message-ID: <20260910233553.3477055-1-jthies@google.com> (raw)
Recently I sent
https://patch.msgid.link/20260825234545.2076049-1-jthies@google.com
to prevent an OOB array index in the UCSI displayport driver. This
merged to 7.3-rc2 but did not include feedback from reviewers in a
v2 version of the patch here
https://lore.kernel.org/all/20260904234401.2339633-1-jthies@google.com/
This series reverts the v1 version of the patch merged to 7.3-rc2
then applies the fix including reviewer feedback. Because this
series is cleaning up the previous change, and not needed to prevent
the OOB access, I've removed the CC stable and Fixes tag from the
displayport driver update.
Let mw know if you have any questions/concerns.
Jameson Thies (2):
Revert "usb: typec: ucsi: displayport: Fix OOB altmode array index"
usb: typec: ucsi: displayport: Check CAM to fix OOB altmode array
index
drivers/usb/typec/ucsi/displayport.c | 9 ++++++---
1 file changed, 6 insertions(+), 3 deletions(-)
base-commit: 34c9c5517033a74039a54dfab24e7bf767a4e0e4
--
2.55.0.1007.g17ff1f9808-goog
next reply other threads:[~2026-09-10 23:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-10 23:35 Jameson Thies [this message]
2026-09-10 23:35 ` [PATCH v1 1/2] Revert "usb: typec: ucsi: displayport: Fix OOB altmode array index" Jameson Thies
2026-09-10 23:35 ` [PATCH v1 2/2] usb: typec: ucsi: displayport: Check CAM to fix OOB altmode array index Jameson Thies
2026-09-11 13:31 ` [PATCH v1 0/2] Cleanup UCSI DisplayPort OOB fix Heikki Krogerus
2026-09-11 18:29 ` Jameson Thies
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=20260910233553.3477055-1-jthies@google.com \
--to=jthies@google.com \
--cc=akuchynski@chromium.org \
--cc=bleung@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox