All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Christian Loehle <christian.loehle@arm.com>
Cc: arighi@nvidia.com, 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 v3 2/3] sched_ext: Provide scx_bpf_task_acquire_remote_curr()
Date: Sat, 9 Aug 2025 09:01:18 -1000	[thread overview]
Message-ID: <aJea_sEq9pRWgShm@slm.duckdns.org> (raw)
In-Reply-To: <20250805111036.130121-3-christian.loehle@arm.com>

On Tue, Aug 05, 2025 at 12:10:35PM +0100, Christian Loehle wrote:
> Provide scx_bpf_task_acquire_remote_curr() as a way for scx schedulers
> to check the curr task of a remote rq without assuming its lock is
> held.
> 
> Many scx schedulers make use of scx_bpf_cpu_rq() to check a remote curr
> (e.g. to see if it should be preempted). This is problematic because
> scx_bpf_cpu_rq() provides access to all fields of struct rq, most of
> which aren't safe to use without holding the associated rq lock.
> 
> Signed-off-by: Christian Loehle <christian.loehle@arm.com>

Applied 1-2 to sched_ext/for-6.17-fixes.

Thanks.

-- 
tejun

  reply	other threads:[~2025-08-09 19:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-05 11:10 [PATCH v3 0/3] sched_ext: Harden scx_bpf_cpu_rq() Christian Loehle
2025-08-05 11:10 ` [PATCH v3 1/3] sched_ext: Mark scx_bpf_cpu_rq as NULL returnable Christian Loehle
2025-08-05 11:10 ` [PATCH v3 2/3] sched_ext: Provide scx_bpf_task_acquire_remote_curr() Christian Loehle
2025-08-09 19:01   ` Tejun Heo [this message]
2025-08-11 17:08     ` Tejun Heo
2025-08-05 11:10 ` [PATCH v3 3/3] sched_ext: Guarantee rq lock on scx_bpf_cpu_rq() Christian Loehle
2025-08-09 19:03   ` Tejun Heo
2025-08-10 10:52     ` Andrea Righi
2025-08-10 22:18       ` Christian Loehle
2025-08-11 16:52         ` Tejun Heo
2025-08-11 14:35       ` Jake Hillion
2025-08-11 16:51         ` Tejun Heo
2025-08-12 13:31         ` Andrea Righi
2025-08-05 14:33 ` [PATCH v3 0/3] sched_ext: Harden scx_bpf_cpu_rq() Andrea Righi

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=aJea_sEq9pRWgShm@slm.duckdns.org \
    --to=tj@kernel.org \
    --cc=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=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 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.