From: Markus Elfring <Markus.Elfring@web.de>
To: Alper Ak <alperyasinak1@gmail.com>, linux-media@vger.kernel.org
Cc: LKML <linux-kernel@vger.kernel.org>,
Biju Das <biju.das.jz@bp.renesas.com>,
Daniel Scally <dan.scally+renesas@ideasonboard.com>,
Hans Verkuil <hverkuil+cisco@kernel.org>,
Jacopo Mondi <jacopo.mondi@ideasonboard.com>,
Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Tommaso Merciai <tommaso.merciai.xr@bp.renesas.com>
Subject: Re: [PATCH] media: rzg2l-cru: Fix possible ERR_PTR deference
Date: Sat, 14 Feb 2026 16:03:17 +0100 [thread overview]
Message-ID: <043fc46a-39be-49cd-9dd0-eb735e92dc2c@web.de> (raw)
In-Reply-To: <CAGpma=7O5Uy1U-ePSixiyoWJremYk=x_L=oR19_VptgNAjen=A@mail.gmail.com>
> No, I haven't seen this happen in practice. This was reported by
> static analysis tool.
* Did this tool get a special name?
* Was any background information published for it?
> Since the function explicitly documents these
> error cases, it seemed appropriate to add defensive error checking to
> avoid potential ERR_PTR dereference.
How do you think about to improve change descriptions accordingly?
Regards,
Markus
prev parent reply other threads:[~2026-02-14 15:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-07 9:48 [PATCH] media: rzg2l-cru: Fix possible ERR_PTR deference Alper Ak
2026-02-07 21:27 ` Laurent Pinchart
2026-02-08 11:07 ` Alper Ak
2026-02-08 13:49 ` Laurent Pinchart
2026-02-14 15:03 ` Markus Elfring [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=043fc46a-39be-49cd-9dd0-eb735e92dc2c@web.de \
--to=markus.elfring@web.de \
--cc=alperyasinak1@gmail.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=dan.scally+renesas@ideasonboard.com \
--cc=hverkuil+cisco@kernel.org \
--cc=jacopo.mondi@ideasonboard.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=tommaso.merciai.xr@bp.renesas.com \
/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