From: Abhinav Kumar <quic_abhinavk@quicinc.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Marijn Suijten <marijn.suijten@somainline.org>
Cc: Ethan Carter Edwards <ethan@ethancedwards.com>,
Rob Clark <robdclark@gmail.com>, Sean Paul <sean@poorly.run>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
<linux-arm-msm@vger.kernel.org>,
<dri-devel@lists.freedesktop.org>,
<freedreno@lists.freedesktop.org>, <linux-kernel@vger.kernel.org>,
<linux-hardening@vger.kernel.org>
Subject: Re: [PATCH v2] drm/msm/dpu: Fix uninitialized variable
Date: Wed, 12 Feb 2025 17:51:11 -0800 [thread overview]
Message-ID: <eb0e478f-87c8-4d1d-a491-d0b1120d60b7@quicinc.com> (raw)
In-Reply-To: <22c97d77-5983-429b-ba0b-ce821a717a0e@quicinc.com>
On 2/11/2025 4:19 PM, Abhinav Kumar wrote:
>
>
> On 2/11/2025 4:13 PM, Dmitry Baryshkov wrote:
>> On Tue, Feb 11, 2025 at 10:23:54AM +0100, Marijn Suijten wrote:
>>> On 2025-02-10 14:14:14, Abhinav Kumar wrote:
>>>>
>>>>
>>>> On 2/9/2025 7:51 PM, Ethan Carter Edwards wrote:
>>>>> There is a possibility for an uninitialized *ret* variable to be
>>>>> returned in some code paths.
>>>>>
>>>>> Fix this by initializing *ret* to 0.
>>>>>
>>>>> Addresses-Coverity-ID: 1642546 ("Uninitialized scalar variable")
>>>>> Fixes: 774bcfb731765d ("drm/msm/dpu: add support for virtual planes")
>>>>> Signed-off-by: Ethan Carter Edwards <ethan@ethancedwards.com>
>>>>> ---
>>>>> Changes in v2:
>>>>> - Return explicit 0 when no error occurs
>>>>> - Add hardening mailing lists
>>>>> - Link to v1: https://lore.kernel.org/r/20250209-dpu-
>>>>> v1-1-0db666884f70@ethancedwards.com
>>>>> ---
>>>>> drivers/gpu/drm/msm/disp/dpu1/dpu_plane.c | 7 +++----
>>>>> 1 file changed, 3 insertions(+), 4 deletions(-)
>>>>>
>>>>
>>>> Thanks for your patch, this was addressed with
>>>>
>>>> https://patchwork.freedesktop.org/patch/631567/ but since this is
>>>> better
>>>> I am fine with this, will pick this one up
>>>
>>> The `return 0;` in this patch should certainly fix this issue
>>> entirely and we
>>> don't need to inline the `int ret` for that, which I think is against
>>> mixed
>>> declaration rules anyway?
>>>
>>> As far as I understand that's what Dmitry suggested in v1, but he r-
>>> b'd it in
>>> this form. Dmitry, was that intended?
>>
>> I think it should be fine, if the gcc doesn't warn against it.
>>
>
> Let me test out the compilation while applying and see if it throws any
> errors. If it does, will report here and we can go with the other patch.
>
On my end, compilation looks fine, so will pickup this version.
Thanks
Abhinav
>>>
>>> - Marijn
>>>
>>>> Reviewed-by: Abhinav Kumar <quic_abhinavk@quicinc.com>
>>>>
>>>>
>>>>> diff --git a/drivers/gpu/drm/msm/disp/dpu1/dpu_plane.c b/drivers/
>>>>> gpu/drm/msm/disp/dpu1/dpu_plane.c
>>>>> index
>>>>> 098abc2c0003cde90ce6219c97ee18fa055a92a5..af3e541f60c303eb5212524e877129359b5ca98c 100644
>>>>> --- a/drivers/gpu/drm/msm/disp/dpu1/dpu_plane.c
>>>>> +++ b/drivers/gpu/drm/msm/disp/dpu1/dpu_plane.c
>>>>> @@ -1164,7 +1164,6 @@ int dpu_assign_plane_resources(struct
>>>>> dpu_global_state *global_state,
>>>>> unsigned int num_planes)
>>>>> {
>>>>> unsigned int i;
>>>>> - int ret;
>>>>> for (i = 0; i < num_planes; i++) {
>>>>> struct drm_plane_state *plane_state = states[i];
>>>>> @@ -1173,13 +1172,13 @@ int dpu_assign_plane_resources(struct
>>>>> dpu_global_state *global_state,
>>>>> !plane_state->visible)
>>>>> continue;
>>>>> - ret = dpu_plane_virtual_assign_resources(crtc, global_state,
>>>>> + int ret = dpu_plane_virtual_assign_resources(crtc,
>>>>> global_state,
>>>>> state, plane_state);
>>>>> if (ret)
>>>>> - break;
>>>>> + return ret;
>>>>> }
>>>>> - return ret;
>>>>> + return 0;
>>>>> }
>>>>> static void dpu_plane_flush_csc(struct dpu_plane *pdpu, struct
>>>>> dpu_sw_pipe *pipe)
>>>>>
>>>>> ---
>>>>> base-commit: a64dcfb451e254085a7daee5fe51bf22959d52d3
>>>>> change-id: 20250209-dpu-c3fac78fc617
>>>>>
>>>>> Best regards,
>>>>
>>
>
next prev parent reply other threads:[~2025-02-13 1:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-10 3:51 [PATCH v2] drm/msm/dpu: Fix uninitialized variable Ethan Carter Edwards
2025-02-10 4:15 ` Dmitry Baryshkov
2025-02-10 22:14 ` Abhinav Kumar
2025-02-11 9:23 ` Marijn Suijten
2025-02-12 0:13 ` Dmitry Baryshkov
2025-02-12 0:19 ` Abhinav Kumar
2025-02-13 1:51 ` Abhinav Kumar [this message]
2025-02-17 22:28 ` (subset) " Abhinav Kumar
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=eb0e478f-87c8-4d1d-a491-d0b1120d60b7@quicinc.com \
--to=quic_abhinavk@quicinc.com \
--cc=airlied@gmail.com \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=ethan@ethancedwards.com \
--cc=freedreno@lists.freedesktop.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marijn.suijten@somainline.org \
--cc=robdclark@gmail.com \
--cc=sean@poorly.run \
--cc=simona@ffwll.ch \
/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