From: Srinivas Kandagatla <srini@kernel.org>
To: Amol Maheshwari <amahesh@qti.qualcomm.com>,
Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Thierry Escande <thierry.escande@linaro.org>,
Mukesh Ojha <mukesh.ojha@oss.qualcomm.com>
Cc: linux-arm-msm@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v2 1/2] misc: fastrpc: Fix NULL pointer dereference in rpmsg callback
Date: Tue, 19 May 2026 17:08:24 +0100 [thread overview]
Message-ID: <177920690436.52506.3867617056043903009.b4-ty@kernel.org> (raw)
In-Reply-To: <20260504171701.18164-1-mukesh.ojha@oss.qualcomm.com>
On Mon, 04 May 2026 22:47:00 +0530, Mukesh Ojha wrote:
> A NULL pointer dereference was observed on Hawi at boot when the DSP
> sends a glink message before fastrpc_rpmsg_probe() has completed
> initialization:
>
> Unable to handle kernel NULL pointer dereference at virtual address 0000000000000178
> pc : _raw_spin_lock_irqsave+0x34/0x8c
> lr : fastrpc_rpmsg_callback+0x3c/0xcc [fastrpc]
> ...
> Call trace:
> _raw_spin_lock_irqsave+0x34/0x8c (P)
> fastrpc_rpmsg_callback+0x3c/0xcc [fastrpc]
> qcom_glink_native_rx+0x538/0x6a4
> qcom_glink_smem_intr+0x14/0x24 [qcom_glink_smem]
>
> [...]
Applied, thanks!
[1/2] misc: fastrpc: Fix NULL pointer dereference in rpmsg callback
commit: 4d24965e0ae82ae4b49c4d739d030ee23a1779d4
[2/2] misc: fastrpc: Move prints outside spinlock in fastrpc_cb_probe
commit: 8d712bcdd1ef73bf790f01039508fb4e9c076bb1
Best regards,
--
Srinivas Kandagatla <srini@kernel.org>
prev parent reply other threads:[~2026-05-19 16:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-04 17:17 Mukesh Ojha
2026-05-04 17:17 ` [PATCH v2 2/2] misc: fastrpc: Move prints outside spinlock in fastrpc_cb_probe Mukesh Ojha
2026-05-04 18:54 ` Bjorn Andersson
2026-05-04 18:53 ` [PATCH v2 1/2] misc: fastrpc: Fix NULL pointer dereference in rpmsg callback Bjorn Andersson
2026-05-05 17:19 ` Mukesh Ojha
2026-05-19 16:08 ` Srinivas Kandagatla [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=177920690436.52506.3867617056043903009.b4-ty@kernel.org \
--to=srini@kernel.org \
--cc=amahesh@qti.qualcomm.com \
--cc=arnd@arndb.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mukesh.ojha@oss.qualcomm.com \
--cc=stable@vger.kernel.org \
--cc=thierry.escande@linaro.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
all inboxes | Powered by JetHome®