From: Johan Hovold <johan+linaro@kernel.org>
To: Vinod Koul <vkoul@kernel.org>,
Kishon Vijay Abraham I <kishon@kernel.org>
Cc: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
linux-arm-msm@vger.kernel.org, linux-phy@lists.infradead.org,
linux-kernel@vger.kernel.org,
Johan Hovold <johan+linaro@kernel.org>
Subject: [PATCH 0/4] phy: qcom: qmp-usb: fix NULL-deref on runtime suspend
Date: Wed, 11 Sep 2024 13:52:49 +0200 [thread overview]
Message-ID: <20240911115253.10920-1-johan+linaro@kernel.org> (raw)
When working on suspend support for Qualcomm platforms like x1e80100, I
ran into a NULL-pointer dereference in one of the QMP drivers. Turns out
this issue has since been reproduced in two more drivers.
Johan
Johan Hovold (4):
phy: qcom: qmp-usb: fix NULL-deref on runtime suspend
phy: qcom: qmp-usb-legacy: fix NULL-deref on runtime suspend
phy: qcom: qmp-usbc: fix NULL-deref on runtime suspend
phy: qcom: qmp-usb: move driver data initialisation earlier
drivers/phy/qualcomm/phy-qcom-qmp-combo.c | 3 +--
drivers/phy/qualcomm/phy-qcom-qmp-usb-legacy.c | 1 +
drivers/phy/qualcomm/phy-qcom-qmp-usb.c | 1 +
drivers/phy/qualcomm/phy-qcom-qmp-usbc.c | 1 +
4 files changed, 4 insertions(+), 2 deletions(-)
--
2.44.2
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
next reply other threads:[~2024-09-11 11:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-11 11:52 Johan Hovold [this message]
2024-09-11 11:52 ` [PATCH 1/4] phy: qcom: qmp-usb: fix NULL-deref on runtime suspend Johan Hovold
2024-09-11 11:52 ` [PATCH 2/4] phy: qcom: qmp-usb-legacy: " Johan Hovold
2024-09-11 11:52 ` [PATCH 3/4] phy: qcom: qmp-usbc: " Johan Hovold
2024-09-11 11:52 ` [PATCH 4/4] phy: qcom: qmp-usb: move driver data initialisation earlier Johan Hovold
2024-09-11 11:57 ` Johan Hovold
2024-09-11 19:01 ` [PATCH 0/4] phy: qcom: qmp-usb: fix NULL-deref on runtime suspend Dmitry Baryshkov
2024-10-16 7:43 ` Johan Hovold
2024-10-17 15:31 ` Vinod Koul
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=20240911115253.10920-1-johan+linaro@kernel.org \
--to=johan+linaro@kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=kishon@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=vkoul@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;
as well as URLs for NNTP newsgroup(s).