From: Chandra Mohan Sundar <chandramohan.explore@gmail.com>
To: Sakari Ailus <sakari.ailus@iki.fi>
Cc: alain.volmat@foss.st.com, mchehab@kernel.org,
mcoquelin.stm32@gmail.com, alexandre.torgue@foss.st.com,
linux-media@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, shuah@kernel.org,
linux-kernel-mentees@lists.linux.dev
Subject: Re: [PATCH] media: v4l: Fix dereference before NULL check
Date: Fri, 22 Aug 2025 08:41:07 +0530 [thread overview]
Message-ID: <CADBJw5bgK9Hcs3SwB0fU0yjiAqD1OZvc5RQT+yVHRAX7EjCG=g@mail.gmail.com> (raw)
In-Reply-To: <aKdWnKdSDs2j73F-@valkosipuli.retiisi.eu>
Hi Sakari Ailus,
Thanks a lot for your review and suggestions. Sure, I will choose an
appropriate subject.
Thanks,
Chandra Mohan Sundar
On Thu, Aug 21, 2025 at 10:57 PM Sakari Ailus <sakari.ailus@iki.fi> wrote:
>
> Hi Chandra,
>
> Please choose an appropriate subject on the next time, this is missing what
> the patch is for -- see git log if in doubt.
>
> On Mon, Aug 18, 2025 at 03:01:57PM +0530, Chandra Mohan Sundar wrote:
> > In 'stm32_csi_start', 'csidev->s_subdev' is dereferenced directly while
> > assigning a value to the 'src_pad'. However the same value is being
> > checked against NULL at a later point of time indicating that there
> > are chances that the value can be NULL.
> >
> > Move the dereference after the NULL check.
> >
> > Fixes: e7bad98c205d1 ("media: v4l: Convert the users of v4l2_get_link_freq to call it on a pad")
>
> Fixes: requires Cc: stable. I've fixed these this time. See
> Documentation/process/submitting-patches.rst .
>
> > Signed-off-by: Chandra Mohan Sundar <chandramohan.explore@gmail.com>
> > ---
> > drivers/media/platform/st/stm32/stm32-csi.c | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/media/platform/st/stm32/stm32-csi.c b/drivers/media/platform/st/stm32/stm32-csi.c
> > index b69048144cc1..fd2b6dfbd44c 100644
> > --- a/drivers/media/platform/st/stm32/stm32-csi.c
> > +++ b/drivers/media/platform/st/stm32/stm32-csi.c
> > @@ -443,8 +443,7 @@ static void stm32_csi_phy_reg_write(struct stm32_csi_dev *csidev,
> > static int stm32_csi_start(struct stm32_csi_dev *csidev,
> > struct v4l2_subdev_state *state)
> > {
> > - struct media_pad *src_pad =
> > - &csidev->s_subdev->entity.pads[csidev->s_subdev_pad_nb];
> > + struct media_pad *src_pad;
> > const struct stm32_csi_mbps_phy_reg *phy_regs = NULL;
> > struct v4l2_mbus_framefmt *sink_fmt;
> > const struct stm32_csi_fmts *fmt;
> > @@ -466,6 +465,7 @@ static int stm32_csi_start(struct stm32_csi_dev *csidev,
> > if (!csidev->s_subdev)
> > return -EIO;
> >
> > + src_pad = &csidev->s_subdev->entity.pads[csidev->s_subdev_pad_nb];
> > link_freq = v4l2_get_link_freq(src_pad,
> > fmt->bpp, 2 * csidev->num_lanes);
> > if (link_freq < 0)
>
> --
> Regards,
>
> Sakari Ailus
prev parent reply other threads:[~2025-08-22 11:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-18 9:31 [PATCH] media: v4l: Fix dereference before NULL check Chandra Mohan Sundar
2025-08-21 17:25 ` Sakari Ailus
2025-08-22 3:11 ` Chandra Mohan Sundar [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='CADBJw5bgK9Hcs3SwB0fU0yjiAqD1OZvc5RQT+yVHRAX7EjCG=g@mail.gmail.com' \
--to=chandramohan.explore@gmail.com \
--cc=alain.volmat@foss.st.com \
--cc=alexandre.torgue@foss.st.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=mcoquelin.stm32@gmail.com \
--cc=sakari.ailus@iki.fi \
--cc=shuah@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;
as well as URLs for NNTP newsgroup(s).