mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: Ekansh Gupta <quic_ekangupt@quicinc.com>, linux-arm-msm@vger.kernel.org
Cc: gregkh@linuxfoundation.org, quic_bkumar@quicinc.com,
	linux-kernel@vger.kernel.org, quic_chennak@quicinc.com,
	stable <stable@kernel.org>
Subject: Re: [PATCH v3 2/9] misc: fastrpc: Fix DSP capabilities request
Date: Fri, 31 May 2024 10:33:29 +0100	[thread overview]
Message-ID: <32750882-2e4c-44b7-af6d-a1ec0857b69a@linaro.org> (raw)
In-Reply-To: <20240530102032.27179-3-quic_ekangupt@quicinc.com>



On 30/05/2024 11:20, Ekansh Gupta wrote:
> Incorrect remote arguments are getting passed when requesting for
> capabilities from DSP. Also there is no requirement to update the
> PD type as it might cause problems for any PD other than user PD.
> In addition to this, the collected capability information is not
> getting copied properly to user. Add changes to address these
> problems and get correct DSP capabilities.
> 
> Fixes: 6c16fd8bdd40 ("misc: fastrpc: Add support to get DSP capabilities")
> Cc: stable <stable@kernel.org>
> Signed-off-by: Ekansh Gupta <quic_ekangupt@quicinc.com>
> ---
>   drivers/misc/fastrpc.c | 7 +++----
>   1 file changed, 3 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/misc/fastrpc.c b/drivers/misc/fastrpc.c
> index 4028cb96bcf2..61389795f498 100644
> --- a/drivers/misc/fastrpc.c
> +++ b/drivers/misc/fastrpc.c
> @@ -1700,9 +1700,8 @@ static int fastrpc_get_info_from_dsp(struct fastrpc_user *fl, uint32_t *dsp_attr
>   	args[0].length = sizeof(dsp_attr_buf_len);
>   	args[0].fd = -1;
>   	args[1].ptr = (u64)(uintptr_t)&dsp_attr_buf[1];
> -	args[1].length = dsp_attr_buf_len;
> +	args[1].length = dsp_attr_buf_len * sizeof(uint32_t);
This does not look correct,

we have allocated buffer of size FASTRPC_MAX_DSP_ATTRIBUTES_LEN which is
already (sizeof(u32) * FASTRPC_MAX_DSP_ATTRIBUTES)

now this patch multiplies with again sizeof(uint32_t), this is going to 
send dsp incorrect size for buffer and overrun the buffer size.



>   	args[1].fd = -1;
> -	fl->pd = USER_PD;
another patch may be.

>   
>   	return fastrpc_internal_invoke(fl, true, FASTRPC_DSP_UTILITIES_HANDLE,
>   				       FASTRPC_SCALARS(0, 1, 1), args);
> @@ -1730,7 +1729,7 @@ static int fastrpc_get_info_from_kernel(struct fastrpc_ioctl_capability *cap,
>   	if (!dsp_attributes)
>   		return -ENOMEM;
>   
> -	err = fastrpc_get_info_from_dsp(fl, dsp_attributes, FASTRPC_MAX_DSP_ATTRIBUTES_LEN);
> +	err = fastrpc_get_info_from_dsp(fl, dsp_attributes, FASTRPC_MAX_DSP_ATTRIBUTES);

You change this again to send FASTRPC_MAX_DSP_ATTRIBUTES instead of 
FASTRPC_MAX_DSP_ATTRIBUTES_LEN but why?


>   	if (err == DSP_UNSUPPORTED_API) {
>   		dev_info(&cctx->rpdev->dev,
>   			 "Warning: DSP capabilities not supported on domain: %d\n", domain);
> @@ -1783,7 +1782,7 @@ static int fastrpc_get_dsp_info(struct fastrpc_user *fl, char __user *argp)
>   	if (err)
>   		return err;
>   
> -	if (copy_to_user(argp, &cap.capability, sizeof(cap.capability)))
> +	if (copy_to_user(argp, &cap, sizeof(cap)))

Why are we copying the full struct here? All that user needs is 
cap.capability?



--srini


>   		return -EFAULT;
>   
>   	return 0;

  parent reply	other threads:[~2024-05-31  9:33 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-30 10:20 [PATCH v3 0/9] Add missing features to FastRPC driver Ekansh Gupta
2024-05-30 10:20 ` [PATCH v3 1/9] misc: fastrpc: Add missing dev_err newlines Ekansh Gupta
2024-05-30 10:20 ` [PATCH v3 2/9] misc: fastrpc: Fix DSP capabilities request Ekansh Gupta
2024-05-30 10:59   ` Dmitry Baryshkov
2024-06-03  6:15     ` Ekansh Gupta
2024-06-03  9:54       ` Dmitry Baryshkov
2024-05-31  9:33   ` Srinivas Kandagatla [this message]
2024-06-03  7:05     ` Ekansh Gupta
2024-06-03  9:56       ` Dmitry Baryshkov
2024-05-30 10:20 ` [PATCH v3 3/9] misc: fastrpc: Fix memory corruption in DSP capabilities Ekansh Gupta
2024-05-30 11:00   ` Dmitry Baryshkov
2024-05-31  9:36   ` Srinivas Kandagatla
2024-06-03  6:23     ` Ekansh Gupta
2024-05-30 10:20 ` [PATCH v3 4/9] misc: fastrpc: Add static PD restart support Ekansh Gupta
2024-05-30 11:04   ` Dmitry Baryshkov
2024-06-03 10:53   ` Caleb Connolly
2024-06-04  9:23     ` Bharath Kumar V
2024-06-04  9:34       ` Dmitry Baryshkov
2024-06-04 11:24       ` Caleb Connolly
2024-05-30 10:20 ` [PATCH v3 5/9] misc: fastrpc: Redesign remote heap management Ekansh Gupta
2024-05-30 11:14   ` Dmitry Baryshkov
2024-06-03  6:25     ` Ekansh Gupta
2024-05-30 10:20 ` [PATCH v3 6/9] misc: fastrpc: Fix unsigned PD support Ekansh Gupta
2024-05-30 23:44   ` Dmitry Baryshkov
2024-05-30 10:20 ` [PATCH v3 7/9] misc: fastrpc: Restrict untrusted app to attach to privileged PD Ekansh Gupta
2024-05-30 23:46   ` Dmitry Baryshkov
2024-05-31  9:48   ` Srinivas Kandagatla
2024-05-30 10:20 ` [PATCH v3 8/9] misc: fastrpc: Restrict untrusted app to spawn signed PD Ekansh Gupta
2024-05-30 23:49   ` Dmitry Baryshkov
2024-06-03  6:27     ` Ekansh Gupta
2024-06-03 10:02       ` Dmitry Baryshkov
2024-06-06  7:22         ` Ekansh Gupta
2024-05-30 10:20 ` [PATCH v3 9/9] misc: fastrpc: Add system unsigned PD support Ekansh Gupta
2024-05-30 23:50   ` Dmitry Baryshkov

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=32750882-2e4c-44b7-af6d-a1ec0857b69a@linaro.org \
    --to=srinivas.kandagatla@linaro.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=quic_bkumar@quicinc.com \
    --cc=quic_chennak@quicinc.com \
    --cc=quic_ekangupt@quicinc.com \
    --cc=stable@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®