From: "Maíra Canal" <mcanal@igalia.com>
To: Jeongjun Park <aha310510@gmail.com>, Melissa Wen <mwen@igalia.com>
Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Iago Toral Quiroga <itoral@igalia.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
stable@kernel.org
Subject: Re: [PATCH] drm/v3d: fix to avoid cleaning up uninitialized CPU jobs
Date: Thu, 28 May 2026 16:14:18 -0300 [thread overview]
Message-ID: <9956a72e-57ad-4bad-a3f6-87710eb4924d@igalia.com> (raw)
In-Reply-To: <20260525140422.1545327-1-aha310510@gmail.com>
Hi Jeongjun,
On 25/05/26 11:04, Jeongjun Park wrote:
> The CPU submit ioctl checks cpu_job->job_type before the CPU job has been
> initialized with v3d_job_init(). When no CPU job extension is supplied,
> the check fails and the ioctl goes to the common error path.
>
> That path calls v3d_job_cleanup(), which expects a fully initialized
> v3d_job. However at this point the CPU job has only been allocated,
> so the embedded DRM scheduler job state has not been initialized yet.
>
> Initialize the CPU job after parsing extensions, but before validating
> the CPU job type and BO count. Keep pre-initialization failures on a
Considering that this is a minimal fix for stable, could you explain me
why do you believe moving v3d_job_init() is the best solution?
Best regards,
- Maíra
> separate path that only deallocates the job and releases multisync
> post-dependencies. Also use the CPU-job release callback so initialized
> CPU jobs are released through the normal cleanup path.
>
> Cc: stable@kernel.org
> Fixes: aafc1a2bea67 ("drm/v3d: Add a CPU job submission")
> Signed-off-by: Jeongjun Park <aha310510@gmail.com>
> ---
> drivers/gpu/drm/v3d/v3d_submit.c | 19 +++++++++++--------
> 1 file changed, 11 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/gpu/drm/v3d/v3d_submit.c b/drivers/gpu/drm/v3d/v3d_submit.c
> index 3ddd53b6f437..f5a1b388eaa3 100644
> --- a/drivers/gpu/drm/v3d/v3d_submit.c
> +++ b/drivers/gpu/drm/v3d/v3d_submit.c
> @@ -1300,10 +1300,18 @@ v3d_submit_cpu_ioctl(struct drm_device *dev, void *data,
> ret = v3d_get_extensions(file_priv, args->extensions, &se, cpu_job);
> if (ret) {
> drm_dbg(dev, "Failed to get extensions.\n");
> - goto fail;
> + v3d_job_deallocate((void *)&cpu_job);
> + goto fail_init;
> }
> }
>
> + ret = v3d_job_init(v3d, file_priv, &cpu_job->base,
> + v3d_cpu_job_free, 0, &se, V3D_CPU);
> + if (ret) {
> + v3d_job_deallocate((void *)&cpu_job);
> + goto fail_init;
> + }
> +
> /* Every CPU job must have a CPU job user extension */
> if (!cpu_job->job_type) {
> drm_dbg(dev, "CPU job must have a CPU job user extension.\n");
> @@ -1319,13 +1327,6 @@ v3d_submit_cpu_ioctl(struct drm_device *dev, void *data,
>
> trace_v3d_submit_cpu_ioctl(&v3d->drm, cpu_job->job_type);
>
> - ret = v3d_job_init(v3d, file_priv, &cpu_job->base,
> - v3d_cpu_job_free, 0, &se, V3D_CPU);
> - if (ret) {
> - v3d_job_deallocate((void *)&cpu_job);
> - goto fail;
> - }
> -
> clean_job = cpu_job->indirect_csd.clean_job;
> csd_job = cpu_job->indirect_csd.job;
>
> @@ -1402,6 +1403,8 @@ v3d_submit_cpu_ioctl(struct drm_device *dev, void *data,
> v3d_job_cleanup((void *)cpu_job);
> v3d_job_cleanup((void *)csd_job);
> v3d_job_cleanup(clean_job);
> +
> +fail_init:
> v3d_put_multisync_post_deps(&se);
>
> return ret;
next prev parent reply other threads:[~2026-05-28 19:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-25 14:04 Jeongjun Park
2026-05-28 19:14 ` Maíra Canal [this message]
2026-06-02 15:41 ` Jeongjun Park
2026-06-02 15:48 ` Maíra Canal
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=9956a72e-57ad-4bad-a3f6-87710eb4924d@igalia.com \
--to=mcanal@igalia.com \
--cc=aha310510@gmail.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=itoral@igalia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=mwen@igalia.com \
--cc=simona@ffwll.ch \
--cc=stable@kernel.org \
--cc=tzimmermann@suse.de \
/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®