From: Ekansh Gupta <ekansh.gupta@oss.qualcomm.com>
To: Srinivas Kandagatla <srinivas.kandagatla@oss.qualcomm.com>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: linux-arm-msm@vger.kernel.org, gregkh@linuxfoundation.org,
quic_bkumar@quicinc.com, linux-kernel@vger.kernel.org,
quic_chennak@quicinc.com, dri-devel@lists.freedesktop.org,
arnd@arndb.de, stable@kernel.org
Subject: Re: [PATCH v1 1/5] misc: fastrpc: Add NULL check to fastrpc_buf_free to prevent crash
Date: Mon, 19 May 2025 16:20:58 +0530 [thread overview]
Message-ID: <2b1f5b07-aec0-46e8-81c0-9f0090828ef1@oss.qualcomm.com> (raw)
In-Reply-To: <c80c48a1-f1b6-4520-9d7c-3a83915c7717@oss.qualcomm.com>
On 5/19/2025 4:10 PM, Srinivas Kandagatla wrote:
> On 5/19/25 11:09, Dmitry Baryshkov wrote:
>> On Mon, May 19, 2025 at 10:25:46AM +0100, Srinivas Kandagatla wrote:
>>> On 5/13/25 05:28, Ekansh Gupta wrote:
>>>> The fastrpc_buf_free function currently does not handle the case where
>>>> the input buffer pointer (buf) is NULL. This can lead to a null pointer
>>>> dereference, causing a crash or undefined behavior when the function
>>>> attempts to access members of the buf structure. Add a NULL check to
>>>> ensure safe handling of NULL pointers and prevent potential crashes.
>>>>
>>> You are mostly defining the code here, but not the root cause of it,
>>> What exactly is the call trace for this crash?
>>>
>>>> Fixes: c68cfb718c8f9 ("misc: fastrpc: Add support for context Invoke method")
>>>> Cc: stable@kernel.org
>>>> Signed-off-by: Ekansh Gupta <ekansh.gupta@oss.qualcomm.com>
>>>> ---
>>>> drivers/misc/fastrpc.c | 3 +++
>>>> 1 file changed, 3 insertions(+)
>>>>
>>>> diff --git a/drivers/misc/fastrpc.c b/drivers/misc/fastrpc.c
>>>> index 7b7a22c91fe4..ca3721365ddc 100644
>>>> --- a/drivers/misc/fastrpc.c
>>>> +++ b/drivers/misc/fastrpc.c
>>>> @@ -394,6 +394,9 @@ static int fastrpc_map_lookup(struct fastrpc_user *fl, int fd,
>>>>
>>>> static void fastrpc_buf_free(struct fastrpc_buf *buf)
>>>> {
>>>> + if (!buf)
>>>> + return;
>>>> +
>>> Most of the users of the fastrpc_buf_free() already have the null
>>> checks, It will be Interesting to know.
>>>
>>> If we decide to make this function to do null null check, then the
>>> existing checks in the caller are redundant.
>> I think it was a primary reason for a change: to eliminate NULL checks
>> on the caller side, as we do in a lot of other kernel API.
> Lets remove the existing NULL checks at caller side as part of this
> patch too.
Sure, I'll remove the checks in the next spin.
>
>
> --Srini
>
>>> --srini
>>>> dma_free_coherent(buf->dev, buf->size, buf->virt,
>>>> FASTRPC_PHYS(buf->phys));
>>>> kfree(buf);
next prev parent reply other threads:[~2025-05-19 10:51 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-13 4:28 [PATCH v1 0/5] misc: fastrpc: Add missing bug fixes Ekansh Gupta
2025-05-13 4:28 ` [PATCH v1 1/5] misc: fastrpc: Add NULL check to fastrpc_buf_free to prevent crash Ekansh Gupta
2025-05-19 9:25 ` Srinivas Kandagatla
2025-05-19 10:09 ` Dmitry Baryshkov
2025-05-19 10:40 ` Srinivas Kandagatla
2025-05-19 10:50 ` Ekansh Gupta [this message]
2025-05-13 4:28 ` [PATCH v1 2/5] misc: fastrpc: Move all remote heap allocations to a new list Ekansh Gupta
2025-05-19 10:16 ` Dmitry Baryshkov
2025-05-19 11:06 ` Ekansh Gupta
2025-05-19 13:29 ` Dmitry Baryshkov
2025-05-22 4:54 ` Ekansh Gupta
2025-05-22 12:09 ` Dmitry Baryshkov
2025-06-12 5:13 ` Ekansh Gupta
2025-06-12 11:16 ` Dmitry Baryshkov
2025-05-19 11:35 ` Srinivas Kandagatla
2025-05-22 5:09 ` Ekansh Gupta
2025-05-13 4:28 ` [PATCH v1 3/5] misc: fastrpc: Fix initial memory allocation for Audio PD memory pool Ekansh Gupta
2025-05-19 10:17 ` Dmitry Baryshkov
2025-05-19 10:53 ` Ekansh Gupta
2025-05-19 13:31 ` Dmitry Baryshkov
2025-05-22 4:58 ` Ekansh Gupta
2025-05-22 12:11 ` Dmitry Baryshkov
2025-05-19 11:41 ` Srinivas Kandagatla
2025-05-22 5:11 ` Ekansh Gupta
2025-05-13 4:28 ` [PATCH v1 4/5] misc: fastrpc: Remove buffer from list prior to unmap operation Ekansh Gupta
2025-05-19 10:20 ` Dmitry Baryshkov
2025-05-19 10:56 ` Ekansh Gupta
2025-05-19 13:32 ` Dmitry Baryshkov
2025-05-13 4:28 ` [PATCH v1 5/5] misc: fastrpc: Add missing unmapping user-requested remote heap Ekansh Gupta
2025-05-19 10:52 ` Dmitry Baryshkov
2025-05-19 10:58 ` Ekansh Gupta
2025-05-19 13:34 ` Dmitry Baryshkov
2025-05-22 5:01 ` Ekansh Gupta
2025-05-22 12:13 ` Dmitry Baryshkov
2025-06-12 5:20 ` Ekansh Gupta
2025-06-12 8:05 ` Dmitry Baryshkov
2025-06-12 9:32 ` Ekansh Gupta
2025-06-12 10:24 ` Dmitry Baryshkov
2025-07-09 5:43 ` Ekansh Gupta
2025-07-19 9:44 ` Dmitry Baryshkov
2025-07-23 9:24 ` Ekansh Gupta
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=2b1f5b07-aec0-46e8-81c0-9f0090828ef1@oss.qualcomm.com \
--to=ekansh.gupta@oss.qualcomm.com \
--cc=arnd@arndb.de \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=dri-devel@lists.freedesktop.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=srinivas.kandagatla@oss.qualcomm.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®