From: Greg KH <gregkh@linuxfoundation.org>
To: Hongbo Li <lihongbo22@huawei.com>
Cc: heikki.krogerus@linux.intel.com, nathan.c.rebello@gmail.com,
kyungtae.kim@dartmouth.edu, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 6.6 & 5.10] usb: typec: ucsi: validate connector number in ucsi_connector_change
Date: Fri, 8 May 2026 13:03:22 +0200 [thread overview]
Message-ID: <2026050843-denatured-bonfire-6337@gregkh> (raw)
In-Reply-To: <20260508092026.1364820-1-lihongbo22@huawei.com>
On Fri, May 08, 2026 at 05:20:26PM +0800, Hongbo Li wrote:
> Commit d2d8c17ac01a ("usb: typec: ucsi: validate connector
> number in ucsi_notify_common()") and commit 5a1140404cbf ("usb:
> typec: ucsi: skip connector validation before init") add the bounds
> check when do the connector change both in pre-init notification and
> the forward notifications. But they are difficult to backport to
> early stable branch such as LTS 6.6, LTS 5.10 due to many dependencies.
> Instead, we choose to validate connector number in ucsi_connector_change
> directly to avoid out-of-range issue.
Why just these 2 branches?
And what specific commits are needed exactly? Why not just backport
them all? that will make future changes apply properly as well, making
the overall work much less over time.
thanks,
greg k-h
next prev parent reply other threads:[~2026-05-08 11:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-08 9:20 [PATCH 6.6 & 5.10] usb: typec: ucsi: validate connector number in ucsi_connector_change Hongbo Li
2026-05-08 11:03 ` Greg KH [this message]
2026-05-08 12:59 ` Hongbo Li
2026-05-08 13:04 ` Greg KH
2026-05-09 3:32 ` Hongbo Li
2026-05-09 3:52 ` Greg KH
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=2026050843-denatured-bonfire-6337@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=kyungtae.kim@dartmouth.edu \
--cc=lihongbo22@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=nathan.c.rebello@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox