public inbox for drm-ai-reviews@public-inbox.freedesktop.org
 help / color / mirror / Atom feed
From: Philipp Stanner <phasta@mailbox.org>
To: phasta@kernel.org, Christian König <christian.koenig@amd.com>,
	Candice Li <candice.li@amd.com>,
	dri-devel@lists.freedesktop.org
Cc: Alexander Deucher <alexander.deucher@amd.com>,
	Hawking Zhang <Hawking.Zhang@amd.com>,
	Tvrtko Ursulin <tvrtko.ursulin@igalia.com>
Subject: Re: [PATCH] drm/sched: fix NULL deref when logging missing entity runqueue
Date: Wed, 03 Jun 2026 09:10:34 +0200	[thread overview]
Message-ID: <b065b85e15ade7a6e470745ba72c9381f3567ece.camel@mailbox.org> (raw)
In-Reply-To: <2f036bd31f8047c140644aae106084d46bcb50a1.camel@mailbox.org>

+Cc Tvrtko

On Wed, 2026-06-03 at 09:06 +0200, Philipp Stanner wrote:
> On Wed, 2026-06-03 at 09:00 +0200, Christian König wrote:
> > On 6/3/26 04:56, Candice Li wrote:
> > > job->sched is not initialized until drm_sched_job_arm(), so use
> > > pr_err() instead of dev_err(job->sched->dev, ...) when entity->rq
> > > is NULL.
> > 
> > You need to CC the designated maintainer on stuff like that! Please use get_maintainer.pl script.
> 
> Thx, Christian
> 
> > 
> > Regards,
> > Christian.
> > 
> > > 
> > > Signed-off-by: Candice Li <candice.li@amd.com>
> > > ---
> > >  drivers/gpu/drm/scheduler/sched_main.c | 2 +-
> > >  1 file changed, 1 insertion(+), 1 deletion(-)
> > > 
> > > diff --git a/drivers/gpu/drm/scheduler/sched_main.c b/drivers/gpu/drm/scheduler/sched_main.c
> > > index bd7936c03da2aa..d21eada76cedf1 100644
> > > --- a/drivers/gpu/drm/scheduler/sched_main.c
> > > +++ b/drivers/gpu/drm/scheduler/sched_main.c
> > > @@ -806,7 +806,7 @@ int drm_sched_job_init(struct drm_sched_job *job,
> > >  		 * or worse--a blank screen--leave a trail in the
> > >  		 * logs, so this can be debugged easier.
> > >  		 */
> > > -		dev_err(job->sched->dev, "%s: entity has no rq!\n", __func__);
> > > +		pr_err("*ERROR* %s: entity has no rq!\n", __func__);
> 
> I think while at it you want to remove '*ERROR*' – the pr_err etc.
> markers contain the qualifiers like _err, _warn etc. so that the level
> is already included for free.

OK, I couldn't see that Tvrtko already jumped in because of his other
patch.

https://lore.kernel.org/dri-devel/20260602153339.43453-1-tvrtko.ursulin@igalia.com/T/#u

I think Tvrtko's patch looks not very controversial and allows us to
get rid of that code, so let's opt for that.

Thx
P.

> 
> Regards
> P.
> 
> > >  		return -ENOENT;
> > >  	}
> > >  

  reply	other threads:[~2026-06-03  7:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-03  2:56 [PATCH] drm/sched: fix NULL deref when logging missing entity runqueue Candice Li
2026-06-03  5:58 ` Tvrtko Ursulin
2026-06-03  7:00 ` Christian König
2026-06-03  7:06   ` Philipp Stanner
2026-06-03  7:10     ` Philipp Stanner [this message]
2026-06-04  1:58 ` Claude review: " Claude Code Review Bot
2026-06-04  1:58 ` Claude Code Review Bot

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=b065b85e15ade7a6e470745ba72c9381f3567ece.camel@mailbox.org \
    --to=phasta@mailbox.org \
    --cc=Hawking.Zhang@amd.com \
    --cc=alexander.deucher@amd.com \
    --cc=candice.li@amd.com \
    --cc=christian.koenig@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=phasta@kernel.org \
    --cc=tvrtko.ursulin@igalia.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