From: Peter Zijlstra <peterz@infradead.org>
To: Tejun Heo <tj@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Borislav Petkov <bp@suse.de>,
Tadeusz Struk <tadeusz.struk@linaro.org>, x86-ml <x86@kernel.org>,
lkml <linux-kernel@vger.kernel.org>,
zhangqiao22@huawei.com, dietmar.eggemann@arm.com
Subject: Re: [GIT PULL] sched/urgent for 5.17-rc4
Date: Mon, 14 Feb 2022 20:35:54 +0100 [thread overview]
Message-ID: <YgqvGuQUF1BdpAl0@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <YgqquDnQe3SihgJU@slm.duckdns.org>
On Mon, Feb 14, 2022 at 09:17:12AM -1000, Tejun Heo wrote:
> Hello, Peter.
>
> On Mon, Feb 14, 2022 at 10:16:57AM +0100, Peter Zijlstra wrote:
> > diff --git a/kernel/fork.c b/kernel/fork.c
> > index d75a528f7b21..05faebafe2b5 100644
> > --- a/kernel/fork.c
> > +++ b/kernel/fork.c
> > @@ -2266,6 +2266,13 @@ static __latent_entropy struct task_struct *copy_process(
> > if (retval)
> > goto bad_fork_put_pidfd;
> >
> > + /*
> > + * Now that the cgroups are pinned, re-clone the parent cgroup and put
> > + * the new task on the correct runqueue. All this *before* the task
> > + * becomes visible.
> > + */
> > + sched_cgroup_fork(p, args);
>
> Would it be less confusing to comment that this isn't ->can_fork() because
> scheduler task_group needs to be initialized for autogroup even when cgroup
> is disabled and maybe name it sched_cgroup_can_fork() even if it always
> succeeds?
So there's two things that need doing; the re-cloning of the task_group
thing, but also calling of __set_task_cpu() which sets up the proper
runqueue links.
The first is CGroup only, and *could* in theory be done in ->can_fork(),
but the second needs to be done unconditionally, and it doesn't make
much sense to split this up.
I actually tried, but it made the patch bigger/uglier -- but maybe I
didn't try hard enough.
> > +void sched_cgroup_fork(struct task_struct *p, struct kernel_clone_args *kargs)
> > {
> > unsigned long flags;
> > -#ifdef CONFIG_CGROUP_SCHED
> > - struct task_group *tg;
> > -#endif
> >
> > + /*
> > + * Because we're not yet on the pid-hash, p->pi_lock isn't strictly
> > + * required yet, but lockdep gets upset if rules are violated.
> > + */
> > raw_spin_lock_irqsave(&p->pi_lock, flags);
> > #ifdef CONFIG_CGROUP_SCHED
> > - tg = container_of(kargs->cset->subsys[cpu_cgrp_id],
> > - struct task_group, css);
> > - p->sched_task_group = autogroup_task_group(p, tg);
> > + if (1) {
> > + struct task_group *tg;
> > + tg = container_of(kargs->cset->subsys[cpu_cgrp_id],
> > + struct task_group, css);
> > + tg = autogroup_task_group(p, tg);
> > + p->sched_task_group = autogroup_task_group(p, tg);
> > + }
>
> I suppose the double autogroup_task_group() call is unintentional?
Yeah, that's a silly fail. Will ammend.
> Otherwise, looks good to me. The only requirement from cgroup side is that
> the membership should be initialized between ->can_fork() and ->fork()
> inclusively, and sans autogroup this would have been done as a part of
> ->can_fork() so the proposed change makes sense to me.
Thanks! I suppose I should go write me a Changelog then... assuming it
actually works :-)
next prev parent reply other threads:[~2022-02-14 20:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-13 12:37 Borislav Petkov
2022-02-13 18:02 ` Linus Torvalds
2022-02-14 8:45 ` Peter Zijlstra
2022-02-14 9:16 ` Peter Zijlstra
2022-02-14 19:17 ` Tejun Heo
2022-02-14 19:35 ` Peter Zijlstra [this message]
2022-02-14 19:46 ` Tejun Heo
2022-02-17 8:51 ` [PATCH] sched: Fix yet more sched_fork() races Peter Zijlstra
2022-02-17 10:50 ` Dietmar Eggemann
2022-02-17 12:08 ` Zhang Qiao
2022-02-17 17:33 ` Tadeusz Struk
2022-02-18 6:18 ` Zhang Qiao
2022-02-19 10:14 ` [tip: sched/urgent] " tip-bot2 for Peter Zijlstra
2022-02-13 18:04 ` [GIT PULL] sched/urgent for 5.17-rc4 pr-tracker-bot
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=YgqvGuQUF1BdpAl0@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bp@suse.de \
--cc=dietmar.eggemann@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tadeusz.struk@linaro.org \
--cc=tj@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.org \
--cc=zhangqiao22@huawei.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®