From: Tejun Heo <tj@kernel.org>
To: Andrea Righi <arighi@nvidia.com>
Cc: David Vernet <void@manifault.com>,
Changwoo Min <changwoo@igalia.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH sched_ext/for-6.16] sched_ext: Add RCU protection to scx_root in DSQ iterator
Date: Wed, 30 Apr 2025 08:59:06 -1000 [thread overview]
Message-ID: <aBJy-hdrkauDW6X_@slm.duckdns.org> (raw)
In-Reply-To: <20250430090930.355732-1-arighi@nvidia.com>
On Wed, Apr 30, 2025 at 11:09:30AM +0200, Andrea Righi wrote:
> @@ -6907,28 +6907,39 @@ __bpf_kfunc int bpf_iter_scx_dsq_new(struct bpf_iter_scx_dsq *it, u64 dsq_id,
> {
> struct bpf_iter_scx_dsq_kern *kit = (void *)it;
> struct scx_sched *sch;
> + int ret = 0;
>
> BUILD_BUG_ON(sizeof(struct bpf_iter_scx_dsq_kern) >
> sizeof(struct bpf_iter_scx_dsq));
> BUILD_BUG_ON(__alignof__(struct bpf_iter_scx_dsq_kern) !=
> __alignof__(struct bpf_iter_scx_dsq));
>
> + rcu_read_lock();
> sch = rcu_dereference(scx_root);
Can you instead try changing rcu_derefernece(scx_root) to
rcu_derefernece_check(scx_root, rcu_read_lock_bh_held())? The warning is
because this can be called both from rcu-locked and bh contexts and while
grabbing rcu_read_lock() once works, telling rcu that the dereference can be
in both contexts is more accurate here.
Thanks.
--
tejun
next prev parent reply other threads:[~2025-04-30 18:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-30 9:09 Andrea Righi
2025-04-30 18:59 ` Tejun Heo [this message]
2025-04-30 19:59 ` 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=aBJy-hdrkauDW6X_@slm.duckdns.org \
--to=tj@kernel.org \
--cc=arighi@nvidia.com \
--cc=changwoo@igalia.com \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®