From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Dan Carpenter <dan.carpenter@linaro.org>
Cc: Jani Nikula <jani.nikula@linux.intel.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Tvrtko Ursulin <tursulin@ursulin.net>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
"Frederic Weisbecker" <frederic@kernel.org>,
Chris Wilson <chris@chris-wilson.co.uk>,
<intel-gfx@lists.freedesktop.org>,
<dri-devel@lists.freedesktop.org>, <linux-kernel@vger.kernel.org>,
<kernel-janitors@vger.kernel.org>
Subject: Re: [PATCH v2] drm/i915/selftests: Change mock_request() to return error pointers
Date: Thu, 26 Jun 2025 10:54:55 -0400 [thread overview]
Message-ID: <aF1fPx1U1f1h8_7F@intel.com> (raw)
In-Reply-To: <aFw0VyNuV5twrHIQ@intel.com>
On Wed, Jun 25, 2025 at 01:39:35PM -0400, Rodrigo Vivi wrote:
> On Wed, Jun 25, 2025 at 10:21:58AM -0500, Dan Carpenter wrote:
> > There was an error pointer vs NULL bug in __igt_breadcrumbs_smoketest().
> > The __mock_request_alloc() function implements the
> > smoketest->request_alloc() function pointer. It was supposed to return
> > error pointers, but it propogates the NULL return from mock_request()
> > so in the event of a failure, it would lead to a NULL pointer
> > dereference.
> >
> > To fix this, change the mock_request() function to return error pointers
> > and update all the callers to expect that.
> >
> > Fixes: 52c0fdb25c7c ("drm/i915: Replace global breadcrumbs with per-context interrupt tracking")
> > Signed-off-by: Dan Carpenter <dan.carpenter@linaro.org>
> > ---
> > V2: In v1 I just updated __mock_request_alloc() to return an error pointer
> > but in v2, I changed mock_request() to update an error pointer and
> > updated all the callers. It's a more extensive change, but hopefully
> > cleaner.
>
> Thank you
>
> Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
and pushed to drm-intel-next
Thanks again
>
>
> >
> > drivers/gpu/drm/i915/selftests/i915_request.c | 20 +++++++++----------
> > drivers/gpu/drm/i915/selftests/mock_request.c | 2 +-
> > 2 files changed, 11 insertions(+), 11 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/i915/selftests/i915_request.c b/drivers/gpu/drm/i915/selftests/i915_request.c
> > index 88870844b5bd..2fb7a9e7efec 100644
> > --- a/drivers/gpu/drm/i915/selftests/i915_request.c
> > +++ b/drivers/gpu/drm/i915/selftests/i915_request.c
> > @@ -73,8 +73,8 @@ static int igt_add_request(void *arg)
> > /* Basic preliminary test to create a request and let it loose! */
> >
> > request = mock_request(rcs0(i915)->kernel_context, HZ / 10);
> > - if (!request)
> > - return -ENOMEM;
> > + if (IS_ERR(request))
> > + return PTR_ERR(request);
> >
> > i915_request_add(request);
> >
> > @@ -91,8 +91,8 @@ static int igt_wait_request(void *arg)
> > /* Submit a request, then wait upon it */
> >
> > request = mock_request(rcs0(i915)->kernel_context, T);
> > - if (!request)
> > - return -ENOMEM;
> > + if (IS_ERR(request))
> > + return PTR_ERR(request);
> >
> > i915_request_get(request);
> >
> > @@ -160,8 +160,8 @@ static int igt_fence_wait(void *arg)
> > /* Submit a request, treat it as a fence and wait upon it */
> >
> > request = mock_request(rcs0(i915)->kernel_context, T);
> > - if (!request)
> > - return -ENOMEM;
> > + if (IS_ERR(request))
> > + return PTR_ERR(request);
> >
> > if (dma_fence_wait_timeout(&request->fence, false, T) != -ETIME) {
> > pr_err("fence wait success before submit (expected timeout)!\n");
> > @@ -219,8 +219,8 @@ static int igt_request_rewind(void *arg)
> > GEM_BUG_ON(IS_ERR(ce));
> > request = mock_request(ce, 2 * HZ);
> > intel_context_put(ce);
> > - if (!request) {
> > - err = -ENOMEM;
> > + if (IS_ERR(request)) {
> > + err = PTR_ERR(request);
> > goto err_context_0;
> > }
> >
> > @@ -237,8 +237,8 @@ static int igt_request_rewind(void *arg)
> > GEM_BUG_ON(IS_ERR(ce));
> > vip = mock_request(ce, 0);
> > intel_context_put(ce);
> > - if (!vip) {
> > - err = -ENOMEM;
> > + if (IS_ERR(vip)) {
> > + err = PTR_ERR(vip);
> > goto err_context_1;
> > }
> >
> > diff --git a/drivers/gpu/drm/i915/selftests/mock_request.c b/drivers/gpu/drm/i915/selftests/mock_request.c
> > index 09f747228dff..1b0cf073e964 100644
> > --- a/drivers/gpu/drm/i915/selftests/mock_request.c
> > +++ b/drivers/gpu/drm/i915/selftests/mock_request.c
> > @@ -35,7 +35,7 @@ mock_request(struct intel_context *ce, unsigned long delay)
> > /* NB the i915->requests slab cache is enlarged to fit mock_request */
> > request = intel_context_create_request(ce);
> > if (IS_ERR(request))
> > - return NULL;
> > + return request;
> >
> > request->mock.delay = delay;
> > return request;
> > --
> > 2.47.2
> >
next prev parent reply other threads:[~2025-06-26 14:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-25 15:21 [PATCH v2] drm/i915/selftests: Change mock_request() to return error pointers Dan Carpenter
2025-06-25 16:30 ` ✓ i915.CI.BAT: success for " Patchwork
2025-06-25 17:39 ` [PATCH v2] " Rodrigo Vivi
2025-06-26 14:54 ` Rodrigo Vivi [this message]
2025-06-26 0:24 ` ✗ i915.CI.Full: failure for " Patchwork
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=aF1fPx1U1f1h8_7F@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=airlied@gmail.com \
--cc=chris@chris-wilson.co.uk \
--cc=dan.carpenter@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=frederic@kernel.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=simona@ffwll.ch \
--cc=tursulin@ursulin.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.