Message ID | 20240911115253.10920-1-johan+linaro@kernel.org (mailing list archive) |
---|---|
Headers | show |
Series | phy: qcom: qmp-usb: fix NULL-deref on runtime suspend | expand |
On Wed, Sep 11, 2024 at 01:52:49PM GMT, Johan Hovold wrote: > 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 For the series: Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Hi Vinod, On Wed, Sep 11, 2024 at 01:52:49PM +0200, Johan Hovold wrote: > 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 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 It's been a month (and a merge window) so sending a reminder. Could you pick these up for 6.12-rc? Johan
On Wed, 11 Sep 2024 13:52:49 +0200, Johan Hovold wrote: > 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 > > > [...] Applied, thanks! [1/4] phy: qcom: qmp-usb: fix NULL-deref on runtime suspend commit: bd9e4d4a3b127686efc60096271b0a44c3100061 [2/4] phy: qcom: qmp-usb-legacy: fix NULL-deref on runtime suspend commit: 29240130ab77c80bea1464317ae2a5fd29c16a0c [3/4] phy: qcom: qmp-usbc: fix NULL-deref on runtime suspend commit: 34c21f94fa1e147a19b54b6adf0c93a623b70dd8 [4/4] phy: qcom: qmp-usb: move driver data initialisation earlier commit: 1dd196f9004848d0318e8831f962cc76255431d8 Best regards,