From: Philipp Stanner <pstanner@redhat.com>
To: "Christian König" <christian.koenig@amd.com>,
"Luben Tuikov" <ltuikov89@gmail.com>,
"Matthew Brost" <matthew.brost@intel.com>,
"Danilo Krummrich" <dakr@kernel.org>,
"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>,
"Tvrtko Ursulin" <tursulin@igalia.com>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] drm/sched: memset() 'job' in drm_sched_job_init()
Date: Tue, 22 Oct 2024 16:17:29 +0200 [thread overview]
Message-ID: <3b7b2e9f324d3a40f290392f56569154a3d6395f.camel@redhat.com> (raw)
In-Reply-To: <9c1f72ea-06d9-4615-b2f8-d98a0aa78aa1@amd.com>
On Mon, 2024-10-21 at 15:05 +0200, Christian König wrote:
> Am 21.10.24 um 12:50 schrieb Philipp Stanner:
> > drm_sched_job_init() has no control over how users allocate struct
> > drm_sched_job. Unfortunately, the function can also not set some
> > struct
> > members such as job->sched.
> >
> > This could theoretically lead to UB by users dereferencing the
> > struct's
> > pointer members too early.
> >
> > It is easier to debug such issues if these pointers are initialized
> > to
> > NULL, so dereferencing them causes a NULL pointer exception.
> > Accordingly, drm_sched_entity_init() does precisely that and
> > initializes
> > its struct with memset().
> >
> > Initialize parameter "job" to 0 in drm_sched_job_init().
> >
> > Signed-off-by: Philipp Stanner <pstanner@redhat.com>
> > ---
> > No changes in v2.
> >
> > +CC Christian and Tvrtko in this thread.
> > Would be cool if someone can do a review.
> > ---
> > drivers/gpu/drm/scheduler/sched_main.c | 8 ++++++++
> > 1 file changed, 8 insertions(+)
> >
> > diff --git a/drivers/gpu/drm/scheduler/sched_main.c
> > b/drivers/gpu/drm/scheduler/sched_main.c
> > index dab8cca79eb7..2e0e5a9577d1 100644
> > --- a/drivers/gpu/drm/scheduler/sched_main.c
> > +++ b/drivers/gpu/drm/scheduler/sched_main.c
> > @@ -796,6 +796,14 @@ int drm_sched_job_init(struct drm_sched_job
> > *job,
> > return -EINVAL;
> > }
> >
> > + /*
> > + * We don't know for sure how the user has allocated.
> > Thus, zero the
> > + * struct so that unallowed (i.e., too early) usage of
> > pointers that
> > + * this function does not set is guaranteed to lead to a
> > NULL pointer
> > + * exception instead of UB.
> > + */
> > + memset(job, 0, sizeof(*job));
> > +
>
> Maybe just implicitly set the sched pointer to NULL here?
>
> On the other hand compilers these days are really good at optimizing
> that away anyway, so feel free to add Reviewed-by: Christian König
> <christian.koenig@amd.com> to the series as is as well.
(I had performance-tested it with several million jobs and couldn't
detect a performance regression that was measurable)
Applied #1 to drm-misc-next, thanks.
Regarding patch #2, I just noticed that it violates the docstring
style. I therefore hereby reject my own patch and will resubmit it in a
cleaner form ^^'
P.
>
> Regards,
> Christian.
>
> > job->entity = entity;
> > job->credits = credits;
> > job->s_fence = drm_sched_fence_alloc(entity, owner);
>
next prev parent reply other threads:[~2024-10-22 14:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-21 10:50 Philipp Stanner
2024-10-21 10:50 ` [PATCH 2/2] drm/sched: warn about drm_sched_job_init()'s partial init Philipp Stanner
2024-10-21 13:05 ` [PATCH 1/2] drm/sched: memset() 'job' in drm_sched_job_init() Christian König
2024-10-22 14:17 ` Philipp Stanner [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-08-06 14:38 Philipp Stanner
2024-08-20 10:23 ` Philipp Stanner
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=3b7b2e9f324d3a40f290392f56569154a3d6395f.camel@redhat.com \
--to=pstanner@redhat.com \
--cc=airlied@gmail.com \
--cc=christian.koenig@amd.com \
--cc=dakr@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ltuikov89@gmail.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=matthew.brost@intel.com \
--cc=mripard@kernel.org \
--cc=simona@ffwll.ch \
--cc=tursulin@igalia.com \
--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®