From: Boris Brezillon <boris.brezillon@collabora.com>
To: "Boris Brezillon" <boris.brezillon@collabora.com>,
"Steven Price" <steven.price@arm.com>,
"Liviu Dudau" <liviu.dudau@arm.com>,
"Adrián Larumbe" <adrian.larumbe@collabora.com>
Cc: dri-devel@lists.freedesktop.org,
Julia Lawall <julia.lawall@inria.fr>,
kernel@collabora.com, stable@vger.kernel.org,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH v2] drm/panthor: Fix access to uninitialized variable in tick_ctx_cleanup()
Date: Tue, 1 Oct 2024 18:44:51 +0200 [thread overview]
Message-ID: <20241001184451.041cf02f@collabora.com> (raw)
In-Reply-To: <20240930163742.87036-1-boris.brezillon@collabora.com>
On Mon, 30 Sep 2024 18:37:42 +0200
Boris Brezillon <boris.brezillon@collabora.com> wrote:
> The group variable can't be used to retrieve ptdev in our second loop,
> because it points to the previously iterated list_head, not a valid
> group. Get the ptdev object from the scheduler instead.
>
> Cc: <stable@vger.kernel.org>
> Fixes: d72f049087d4 ("drm/panthor: Allow driver compilation")
> Reported-by: kernel test robot <lkp@intel.com>
> Reported-by: Julia Lawall <julia.lawall@inria.fr>
> Closes: https://lore.kernel.org/r/202409302306.UDikqa03-lkp@intel.com/
> Signed-off-by: Boris Brezillon <boris.brezillon@collabora.com>
Queued to drm-misc-fixes.
> ---
> drivers/gpu/drm/panthor/panthor_sched.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/panthor/panthor_sched.c b/drivers/gpu/drm/panthor/panthor_sched.c
> index 201d5e7a921e..24ff91c084e4 100644
> --- a/drivers/gpu/drm/panthor/panthor_sched.c
> +++ b/drivers/gpu/drm/panthor/panthor_sched.c
> @@ -2052,6 +2052,7 @@ static void
> tick_ctx_cleanup(struct panthor_scheduler *sched,
> struct panthor_sched_tick_ctx *ctx)
> {
> + struct panthor_device *ptdev = sched->ptdev;
> struct panthor_group *group, *tmp;
> u32 i;
>
> @@ -2060,7 +2061,7 @@ tick_ctx_cleanup(struct panthor_scheduler *sched,
> /* If everything went fine, we should only have groups
> * to be terminated in the old_groups lists.
> */
> - drm_WARN_ON(&group->ptdev->base, !ctx->csg_upd_failed_mask &&
> + drm_WARN_ON(&ptdev->base, !ctx->csg_upd_failed_mask &&
> group_can_run(group));
>
> if (!group_can_run(group)) {
> @@ -2083,7 +2084,7 @@ tick_ctx_cleanup(struct panthor_scheduler *sched,
> /* If everything went fine, the groups to schedule lists should
> * be empty.
> */
> - drm_WARN_ON(&group->ptdev->base,
> + drm_WARN_ON(&ptdev->base,
> !ctx->csg_upd_failed_mask && !list_empty(&ctx->groups[i]));
>
> list_for_each_entry_safe(group, tmp, &ctx->groups[i], run_node) {
prev parent reply other threads:[~2024-10-01 16:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-30 16:37 [PATCH v2] drm/panthor: Fix access to uninitialized variable in tick_ctx_cleanup() Boris Brezillon
2024-09-30 17:39 ` Liviu Dudau
2024-10-01 16:44 ` Boris Brezillon [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=20241001184451.041cf02f@collabora.com \
--to=boris.brezillon@collabora.com \
--cc=adrian.larumbe@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=julia.lawall@inria.fr \
--cc=kernel@collabora.com \
--cc=liviu.dudau@arm.com \
--cc=lkp@intel.com \
--cc=stable@vger.kernel.org \
--cc=steven.price@arm.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;
as well as URLs for NNTP newsgroup(s).