From: Nikita Travkin <nikita@trvn.ru>
To: Mukesh Ojha <mukesh.ojha@oss.qualcomm.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Dmitry Baryshkov <lumag@kernel.org>,
Chris Lew <quic_clew@quicinc.com>,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
Gokul Krishnakumar <gokul.krishnakumar@oss.qualcomm.com>,
stable@vger.kernel.org,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Subject: Re: [PATCH v3] soc: qcom: pd-mapper: Fix element length in servreg_loc_pfr_req_ei
Date: Mon, 09 Mar 2026 15:06:54 +0500 [thread overview]
Message-ID: <d9ef1fcaf15248f23c19882c8783b3ea@trvn.ru> (raw)
In-Reply-To: <20260309090151.897685-1-mukesh.ojha@oss.qualcomm.com>
Mukesh Ojha писал(а) 09.03.2026 14:01:
> From: Gokul Krishnakumar <gokul.krishnakumar@oss.qualcomm.com>
>
> It looks element length declared in servreg_loc_pfr_req_ei for reason
> not matching servreg_loc_pfr_req's reason field due which we could
> observe decoding error on PD crash.
>
> qmi_decode_string_elem: String len 81 >= Max Len 65
>
> Fix this by matching with servreg_loc_pfr_req's reason field.
>
I've recently encountered same problem when causing a crash of slpi
on my Lenovo thinkpad x13s. This patch seems to fix it.
Before:
[19146.069830] qmi_decode_string_elem: String len 87 >= Max Len 65
[19146.069851] failed to decode incoming message
[19146.085449] qcom_q6v5_pas 2400000.remoteproc: fatal error received: err_qdi.c:1122:EF:sensor_process:0x2:SNS_REG_TASK:0x62:sns_registry_sensor.c:154:sns_registry_sensor.c
[19146.085462] remoteproc remoteproc0: crash detected in slpi: type fatal error
After:
[ 40.343732] PDM: service 'sensor_process' crash: 'EF:sensor_process:0x2:SNS_REG_TASK:0x62:sns_registry_s'
[ 40.358994] qcom_q6v5_pas 2400000.remoteproc: fatal error received: err_qdi.c:1122:EF:sensor_process:0x2:SNS_REG_TASK:0x62:sns_registry_sensor.c:154:sns_registry_sensor.c
[ 40.359012] remoteproc remoteproc0: crash detected in slpi: type fatal error
(There are two empty lines in dmesg now before the PDM: message, not
sure what writes them)
Tested-by: Nikita Travkin <nikita@trvn.ru>
Thanks!
Nikita
> Cc: stable@vger.kernel.org
> Fixes: 1ebcde047c54 ("soc: qcom: add pd-mapper implementation")
> Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
> Signed-off-by: Gokul Krishnakumar <gokul.krishnakumar@oss.qualcomm.com>
> [mukesh: the element length change to the service field is not required.
> Fixed it by removing the change and rephrasing the commit text.]
> Signed-off-by: Mukesh Ojha <mukesh.ojha@oss.qualcomm.com>
> ---
> Changes in v3: https://lore.kernel.org/lkml/20260202103641.3003867-1-mukesh.ojha@oss.qualcomm.com/
> - Remove debug patch as we have enough prints to make decode error
> code.
> - Added Gokul as the author of the patch and added the information on the
> changes done by me on top.
>
> Changes in v2: https://lore.kernel.org/lkml/20260129152320.3658053-1-mukesh.ojha@oss.qualcomm.com/
> - Given credit to my colleague Gokul.K who first faced this issue and given
> initial fix and that was later corrected by me.
> - Rebased it on next-20260130 and added stable mailing list, R-b tag.
>
>
> drivers/soc/qcom/pdr_internal.h | 2 +-
> drivers/soc/qcom/qcom_pdr_msg.c | 2 +-
> include/linux/soc/qcom/pdr.h | 1 +
> 3 files changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/soc/qcom/pdr_internal.h b/drivers/soc/qcom/pdr_internal.h
> index 039508c1bbf7..047c0160b617 100644
> --- a/drivers/soc/qcom/pdr_internal.h
> +++ b/drivers/soc/qcom/pdr_internal.h
> @@ -84,7 +84,7 @@ struct servreg_set_ack_resp {
>
> struct servreg_loc_pfr_req {
> char service[SERVREG_NAME_LENGTH + 1];
> - char reason[257];
> + char reason[SERVREG_PFR_LENGTH + 1];
> };
>
> struct servreg_loc_pfr_resp {
> diff --git a/drivers/soc/qcom/qcom_pdr_msg.c b/drivers/soc/qcom/qcom_pdr_msg.c
> index ca98932140d8..02022b11ecf0 100644
> --- a/drivers/soc/qcom/qcom_pdr_msg.c
> +++ b/drivers/soc/qcom/qcom_pdr_msg.c
> @@ -325,7 +325,7 @@ const struct qmi_elem_info servreg_loc_pfr_req_ei[] = {
> },
> {
> .data_type = QMI_STRING,
> - .elem_len = SERVREG_NAME_LENGTH + 1,
> + .elem_len = SERVREG_PFR_LENGTH + 1,
> .elem_size = sizeof(char),
> .array_type = VAR_LEN_ARRAY,
> .tlv_type = 0x02,
> diff --git a/include/linux/soc/qcom/pdr.h b/include/linux/soc/qcom/pdr.h
> index 83a8ea612e69..2b7691e47c2a 100644
> --- a/include/linux/soc/qcom/pdr.h
> +++ b/include/linux/soc/qcom/pdr.h
> @@ -5,6 +5,7 @@
> #include <linux/soc/qcom/qmi.h>
>
> #define SERVREG_NAME_LENGTH 64
> +#define SERVREG_PFR_LENGTH 256
>
> struct pdr_service;
> struct pdr_handle;
prev parent reply other threads:[~2026-03-09 10:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-09 9:01 Mukesh Ojha
2026-03-09 10:06 ` Nikita Travkin [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=d9ef1fcaf15248f23c19882c8783b3ea@trvn.ru \
--to=nikita@trvn.ru \
--cc=andersson@kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=gokul.krishnakumar@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lumag@kernel.org \
--cc=mukesh.ojha@oss.qualcomm.com \
--cc=quic_clew@quicinc.com \
--cc=stable@vger.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
all inboxes | Powered by JetHome®