From: Vinod Koul <vkoul@kernel.org>
To: mani@kernel.org, James.Bottomley@HansenPartnership.com,
martin.petersen@oracle.com, bvanassche@acm.org,
andersson@kernel.org, neil.armstrong@linaro.org,
konrad.dybcio@oss.qualcomm.com,
dmitry.baryshkov@oss.qualcomm.com, quic_cang@quicinc.com,
Nitin Rawat <quic_nitirawa@quicinc.com>
Cc: linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-scsi@vger.kernel.org,
Naresh Kamboju <naresh.kamboju@linaro.org>,
Aishwarya <aishwarya.tcv@arm.com>,
Ram Kumar Dwivedi <quic_rdwivedi@quicinc.com>
Subject: Re: [PATCH V3] scsi: ufs: qcom : Fix NULL pointer dereference in ufs_qcom_setup_clocks
Date: Thu, 26 Jun 2025 17:47:04 -0700 [thread overview]
Message-ID: <175098522490.106297.11028357355875089075.b4-ty@kernel.org> (raw)
In-Reply-To: <20250623134809.20405-1-quic_nitirawa@quicinc.com>
On Mon, 23 Jun 2025 19:18:09 +0530, Nitin Rawat wrote:
> Fix a NULL pointer dereference in ufs_qcom_setup_clocks due to an
> uninitialized 'host' variable. The variable 'phy' is now assigned
> after confirming 'host' is not NULL.
>
> Call Stack:
>
> Unable to handle kernel NULL pointer dereference at
> virtual address 0000000000000000
>
> [...]
Applied, thanks!
[1/1] scsi: ufs: qcom : Fix NULL pointer dereference in ufs_qcom_setup_clocks
commit: 720fa0cb59e411eca6b274f78073b6d2fe68eb45
Best regards,
--
~Vinod
prev parent reply other threads:[~2025-06-27 0:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-23 13:48 Nitin Rawat
2025-06-25 1:28 ` Martin K. Petersen
2025-06-25 8:14 ` Nitin Rawat
2025-06-27 0:47 ` Vinod Koul [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=175098522490.106297.11028357355875089075.b4-ty@kernel.org \
--to=vkoul@kernel.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=aishwarya.tcv@arm.com \
--cc=andersson@kernel.org \
--cc=bvanassche@acm.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mani@kernel.org \
--cc=martin.petersen@oracle.com \
--cc=naresh.kamboju@linaro.org \
--cc=neil.armstrong@linaro.org \
--cc=quic_cang@quicinc.com \
--cc=quic_nitirawa@quicinc.com \
--cc=quic_rdwivedi@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
all inboxes | Powered by JetHome®