From: Andrea Righi <arighi@nvidia.com>
To: Christian Loehle <christian.loehle@arm.com>
Cc: tj@kernel.org, void@manifault.com, linux-kernel@vger.kernel.org,
sched-ext@lists.linux.dev, changwoo@igalia.com, hodgesd@meta.com,
mingo@redhat.com, peterz@infradead.org
Subject: Re: [PATCH v2 3/3] sched_ext: Guarantee rq lock on scx_bpf_cpu_rq()
Date: Mon, 4 Aug 2025 14:41:19 +0200 [thread overview]
Message-ID: <aJCqb-ZI4pd15cr5@gpd4> (raw)
In-Reply-To: <20250804112743.711816-4-christian.loehle@arm.com>
On Mon, Aug 04, 2025 at 12:27:43PM +0100, Christian Loehle wrote:
> Most fields in scx_bpf_cpu_rq() assume that its rq_lock is held.
> Furthermore they become meaningless without rq lock, too.
> Only return scx_bpf_cpu_rq() if we hold rq lock of that rq.
>
> All upstream scx schedulers can be converted into the new
> scx_bpf_remote_curr() instead.
>
> Signed-off-by: Christian Loehle <christian.loehle@arm.com>
> ---
> kernel/sched/ext.c | 10 +++++++++-
> 1 file changed, 9 insertions(+), 1 deletion(-)
>
> diff --git a/kernel/sched/ext.c b/kernel/sched/ext.c
> index 1d9d9cbed0aa..0b05ddc1f100 100644
> --- a/kernel/sched/ext.c
> +++ b/kernel/sched/ext.c
> @@ -7420,10 +7420,18 @@ __bpf_kfunc s32 scx_bpf_task_cpu(const struct task_struct *p)
> */
> __bpf_kfunc struct rq *scx_bpf_cpu_rq(s32 cpu)
> {
> + struct rq *rq;
> +
> if (!kf_cpu_valid(cpu, NULL))
> return NULL;
>
> - return cpu_rq(cpu);
> + rq = cpu_rq(cpu);
> + if (rq != scx_locked_rq_state) {
I think you want to check rq != scx_locked_rq(), since scx_locked_rq_state
is a per-CPU variable.
We may also want to add a preempt_disable/enable() for consistency. How
about something like this?
preempt_disable();
rq = cpu_rq(cpu);
if (rq != scx_locked_rq()) {
scx_kf_error("Accessing CPU%d rq from CPU%d without holding its lock",
cpu, smp_processor_id());
rq = NULL;
}
preempt_enable();
Thanks,
-Andrea
> + scx_kf_error("Accessing not locked rq %d", cpu);
> + return NULL;
> + }
> +
> + return rq;
> }
>
> struct task_struct *bpf_task_acquire(struct task_struct *p);
> --
> 2.34.1
>
next prev parent reply other threads:[~2025-08-04 12:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-04 11:27 [PATCH v2 0/3] sched_ext: Harden scx_bpf_cpu_rq() Christian Loehle
2025-08-04 11:27 ` [PATCH v2 1/3] sched_ext: Mark scx_bpf_cpu_rq as NULL returnable Christian Loehle
2025-08-04 11:27 ` [PATCH v2 2/3] sched_ext: Provide scx_bpf_remote_curr() Christian Loehle
2025-08-04 12:51 ` Andrea Righi
2025-08-04 13:27 ` Christian Loehle
2025-08-04 15:48 ` Andrea Righi
2025-08-04 11:27 ` [PATCH v2 3/3] sched_ext: Guarantee rq lock on scx_bpf_cpu_rq() Christian Loehle
2025-08-04 12:41 ` Andrea Righi [this message]
2025-08-04 13:02 ` Christian Loehle
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=aJCqb-ZI4pd15cr5@gpd4 \
--to=arighi@nvidia.com \
--cc=changwoo@igalia.com \
--cc=christian.loehle@arm.com \
--cc=hodgesd@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=sched-ext@lists.linux.dev \
--cc=tj@kernel.org \
--cc=void@manifault.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