From: Wentao Liang <vulab@iscas.ac.cn>
To: jani.nikula@linux.intel.com, joonas.lahtinen@linux.intel.com,
rodrigo.vivi@intel.com
Cc: tursulin@ursulin.net, intel-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Wentao Liang <vulab@iscas.ac.cn>,
stable@vger.kernel.org
Subject: [PATCH] drm/i915/selftests: Unpin the context in the LRC garbage test
Date: Tue, 3 Nov 2026 08:04:34 +0000 [thread overview]
Message-ID: <20261103080434.1127682-1-vulab@iscas.ac.cn> (raw)
garbage() explicitly pins the context to corrupt its register state, but
only releases that pin when request creation fails. On success, its caller
waits for the request and drops the context reference without unpinning.
The request's own context pin does not account for this extra pin.
Release the explicit pin immediately after creating the request, on both
success and failure. A successful request already holds the context pin
it needs until retirement, as in the other context selftests.
Fixes: 24eba7a9981d ("drm/i915/selftests: Check recovery from corrupted LRC")
Cc: stable@vger.kernel.org
Assisted-by: DeepSeek-V4.1-Flash and OpenAI Codex
Signed-off-by: Wentao Liang <vulab@iscas.ac.cn>
---
drivers/gpu/drm/i915/gt/selftest_lrc.c | 11 +++--------
1 file changed, 3 insertions(+), 8 deletions(-)
diff --git a/drivers/gpu/drm/i915/gt/selftest_lrc.c b/drivers/gpu/drm/i915/gt/selftest_lrc.c
index 23f04f6f8fba..314922e778a8 100644
--- a/drivers/gpu/drm/i915/gt/selftest_lrc.c
+++ b/drivers/gpu/drm/i915/gt/selftest_lrc.c
@@ -1782,18 +1782,13 @@ static struct i915_request *garbage(struct intel_context *ce,
LRC_STATE_OFFSET);
rq = intel_context_create_request(ce);
- if (IS_ERR(rq)) {
- err = PTR_ERR(rq);
- goto err_unpin;
- }
+ intel_context_unpin(ce);
+ if (IS_ERR(rq))
+ return rq;
i915_request_get(rq);
i915_request_add(rq);
return rq;
-
-err_unpin:
- intel_context_unpin(ce);
- return ERR_PTR(err);
}
static int __lrc_garbage(struct intel_engine_cs *engine, struct rnd_state *prng)
--
2.34.1
next reply other threads:[~2026-11-03 8:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 8:04 Wentao Liang [this message]
2026-11-03 9:28 ` Krzysztof Kozlowski
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=20261103080434.1127682-1-vulab@iscas.ac.cn \
--to=vulab@iscas.ac.cn \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=stable@vger.kernel.org \
--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 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®