From: Johan Hovold <johan+linaro@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Thinh Nguyen <Thinh.Nguyen@synopsys.com>,
Krishna Kurapati PSSNV <quic_kriskura@quicinc.com>,
linux-arm-msm@vger.kernel.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org,
Johan Hovold <johan+linaro@kernel.org>
Subject: [PATCH 0/3] USB: dwc3: qcom: fix resource leaks on probe deferral
Date: Fri, 17 Nov 2023 18:36:47 +0100 [thread overview]
Message-ID: <20231117173650.21161-1-johan+linaro@kernel.org> (raw)
When reviewing the recently submitted series which reworks the dwc3 qcom
glue implementation [1], I noticed that the driver's tear down handling
is currently broken, something which can lead to memory leaks and
potentially use-after-free issues on probe deferral and on driver
unbind.
Let's get this sorted before reworking driver.
Note that the last patch has only been compile tested as I don't have
access to a sdm845 device.
Johan
[1] https://lore.kernel.org/lkml/20231016-dwc3-refactor-v1-0-ab4a84165470@quicinc.com/
Johan Hovold (3):
USB: dwc3: qcom: fix resource leaks on probe deferral
USB: dwc3: qcom: fix software node leak on probe errors
USB: dwc3: qcom: fix ACPI platform device leak
drivers/usb/dwc3/dwc3-qcom.c | 57 +++++++++++++++++++++++++++---------
1 file changed, 43 insertions(+), 14 deletions(-)
--
2.41.0
next reply other threads:[~2023-11-17 17:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-17 17:36 Johan Hovold [this message]
2023-11-17 17:36 ` [PATCH 1/3] USB: dwc3: qcom: fix resource leaks on probe deferral Johan Hovold
2023-11-17 19:03 ` Andrew Halaney
2023-11-17 17:36 ` [PATCH 2/3] USB: dwc3: qcom: fix software node leak on probe errors Johan Hovold
2023-11-17 19:09 ` Andrew Halaney
2023-11-21 14:20 ` Heikki Krogerus
2023-11-17 17:36 ` [PATCH 3/3] USB: dwc3: qcom: fix ACPI platform device leak Johan Hovold
2023-11-17 19:17 ` Andrew Halaney
2023-11-20 9:39 ` Shawn Guo
2023-11-17 23:47 ` [PATCH 0/3] USB: dwc3: qcom: fix resource leaks on probe deferral Konrad Dybcio
2023-11-20 15:22 ` Andrew Halaney
2023-11-20 16:53 ` Johan Hovold
2023-11-21 14:21 ` Greg Kroah-Hartman
2023-11-21 15:04 ` Johan Hovold
2023-11-21 18:03 ` Greg Kroah-Hartman
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=20231117173650.21161-1-johan+linaro@kernel.org \
--to=johan+linaro@kernel.org \
--cc=Thinh.Nguyen@synopsys.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=konrad.dybcio@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=quic_kriskura@quicinc.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