From: Andi Shyti <andi.shyti@kernel.org>
To: Krzysztof Karas <krzysztof.karas@intel.com>
Cc: intel-gfx@lists.freedesktop.org,
Andi Shyti <andi.shyti@linux.intel.com>,
Sebastian Brzezinka <sebastian.brzezinka@intel.com>,
Krzysztof Niemiec <krzysztof.niemiec@intel.com>,
Janusz Krzysztofik <janusz.krzysztofik@linux.intel.com>
Subject: Re: [PATCH v4 1/2] drm/i915/selftests: Prevent userspace mapping invalidation
Date: Thu, 9 Apr 2026 13:09:45 +0200 [thread overview]
Message-ID: <adeCdrdcZZWa98VY@zenone.zhora.eu> (raw)
In-Reply-To: <20260408083034.2060372-2-krzysztof.karas@intel.com>
Hi Krzysztof,
> + if (!u_pid_nr) {
> + pr_warn("No current->mm and no PID provided to safely borrow userspace memory from.\n"
> + "This may lead to switching off tests requiring that for mappings");
This line is too long (please check with checkpatch). The message
is to long. We don't need to provide a full explanation. You can
actually just write something like "No usable userspace mm".
jkk
> + goto run_tests;
> + }
> +
> + u_pid = find_get_pid(u_pid_nr);
> +
> + if (!u_pid) {
> + pr_warn("Could not find PID: %d\n", u_pid_nr);
> + goto run_tests;
> + }
> +
> + task = get_pid_task(u_pid, PIDTYPE_PID);
> + put_pid(u_pid);
> + if (!task) {
> + pr_warn("Could not find userspace task for PID: %d\n", u_pid_nr);
> + goto run_tests;
> + }
> +
> + mm = get_task_mm(task);
> + put_task_struct(task);
> + if (!mm) {
> + pr_warn("Could not find address space of task with PID: %d\n", u_pid_nr);
> + goto run_tests;
> + }
> +
> + kthread_use_mm(mm);
> + mmput_async(mm);
> + if (unlikely(!current->mm)) {
> + pr_warn("Could not set mm as current->mm\n");
> + }
Please remove the two brackets here.
On a general note, I'm not a big fan of the goto's used for
jumping around the code, unless it's an exit point.
Perhaps this can be written as:
if (!current->mm) {
mm = a_new_function(...);
if (mm) {
kthread_use_mm(mm);
...
}
...
}
Thanks,
Andi
> + }
> +
next prev parent reply other threads:[~2026-04-09 11:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-08 8:30 [RFC v4 0/2] drm/i915/selftests: Use safe userspace memory for mappings Krzysztof Karas
2026-04-08 8:30 ` [PATCH v4 1/2] drm/i915/selftests: Prevent userspace mapping invalidation Krzysztof Karas
2026-04-08 9:20 ` Janusz Krzysztofik
2026-04-09 6:21 ` Krzysztof Karas
2026-04-09 11:09 ` Andi Shyti [this message]
2026-04-08 8:30 ` [PATCH v4 2/2] drm/i915/selftests: Run vma tests only if current->mm is present Krzysztof Karas
2026-04-08 9:25 ` Janusz Krzysztofik
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=adeCdrdcZZWa98VY@zenone.zhora.eu \
--to=andi.shyti@kernel.org \
--cc=andi.shyti@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=janusz.krzysztofik@linux.intel.com \
--cc=krzysztof.karas@intel.com \
--cc=krzysztof.niemiec@intel.com \
--cc=sebastian.brzezinka@intel.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