From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Andrei Kuchynski <akuchynski@chromium.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Benson Leung <bleung@chromium.org>,
"Christian A. Ehrhardt" <lk@c--e.de>,
Jameson Thies <jthies@google.com>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] usb: typec: ucsi: Fix NULL pointer access
Date: Tue, 4 Mar 2025 17:19:16 +0200 [thread overview]
Message-ID: <Z8cZ9O-qZnV5btpx@kuha.fi.intel.com> (raw)
In-Reply-To: <20250301081057.1952519-2-akuchynski@chromium.org>
On Sat, Mar 01, 2025 at 08:10:56AM +0000, Andrei Kuchynski wrote:
> Resources should be released only after all threads that utilize them
> have been destroyed.
> This commit ensures that resources are not released prematurely by waiting
> for the associated workqueue to complete before deallocating them.
>
> Signed-off-by: Andrei Kuchynski <akuchynski@chromium.org>
This needs to be marked as a fix. Please add the appropriate Fixes
tag and Cc stable.
thanks,
> ---
> drivers/usb/typec/ucsi/ucsi.c | 13 +++++++------
> 1 file changed, 7 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/usb/typec/ucsi/ucsi.c b/drivers/usb/typec/ucsi/ucsi.c
> index fcf499cc9458..43b4f8207bb3 100644
> --- a/drivers/usb/typec/ucsi/ucsi.c
> +++ b/drivers/usb/typec/ucsi/ucsi.c
> @@ -1825,11 +1825,11 @@ static int ucsi_init(struct ucsi *ucsi)
>
> err_unregister:
> for (con = connector; con->port; con++) {
> + if (con->wq)
> + destroy_workqueue(con->wq);
> ucsi_unregister_partner(con);
> ucsi_unregister_altmodes(con, UCSI_RECIPIENT_CON);
> ucsi_unregister_port_psy(con);
> - if (con->wq)
> - destroy_workqueue(con->wq);
>
> usb_power_delivery_unregister_capabilities(con->port_sink_caps);
> con->port_sink_caps = NULL;
> @@ -2013,10 +2013,6 @@ void ucsi_unregister(struct ucsi *ucsi)
>
> for (i = 0; i < ucsi->cap.num_connectors; i++) {
> cancel_work_sync(&ucsi->connector[i].work);
> - ucsi_unregister_partner(&ucsi->connector[i]);
> - ucsi_unregister_altmodes(&ucsi->connector[i],
> - UCSI_RECIPIENT_CON);
> - ucsi_unregister_port_psy(&ucsi->connector[i]);
>
> if (ucsi->connector[i].wq) {
> struct ucsi_work *uwork;
> @@ -2032,6 +2028,11 @@ void ucsi_unregister(struct ucsi *ucsi)
> destroy_workqueue(ucsi->connector[i].wq);
> }
>
> + ucsi_unregister_partner(&ucsi->connector[i]);
> + ucsi_unregister_altmodes(&ucsi->connector[i],
> + UCSI_RECIPIENT_CON);
> + ucsi_unregister_port_psy(&ucsi->connector[i]);
> +
> usb_power_delivery_unregister_capabilities(ucsi->connector[i].port_sink_caps);
> ucsi->connector[i].port_sink_caps = NULL;
> usb_power_delivery_unregister_capabilities(ucsi->connector[i].port_source_caps);
> --
> 2.48.1.711.g2feabab25a-goog
--
heikki
prev parent reply other threads:[~2025-03-04 15:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-01 8:10 [PATCH 0/1] Fix race condition causing NULL pointer dereference Andrei Kuchynski
2025-03-01 8:10 ` [PATCH 1/1] usb: typec: ucsi: Fix NULL pointer access Andrei Kuchynski
2025-03-04 15:19 ` Heikki Krogerus [this message]
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=Z8cZ9O-qZnV5btpx@kuha.fi.intel.com \
--to=heikki.krogerus@linux.intel.com \
--cc=akuchynski@chromium.org \
--cc=bleung@chromium.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=jthies@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=lk@c--e.de \
/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
all inboxes | Powered by JetHome®