From: Thomas Gleixner <firstname.lastname@example.org>
To: email@example.com, Uladzislau Rezki <firstname.lastname@example.org>
Cc: Sebastian Andrzej Siewior <email@example.com>,
"tip-bot2 for Paul E. McKenney" <firstname.lastname@example.org>,
Peter Zijlstra <email@example.com>,
Frederic Weisbecker <firstname.lastname@example.org>,
Subject: Re: [tip: core/rcu] softirq: Don't try waking ksoftirqd before it has been spawned
Date: Thu, 15 Apr 2021 01:54:18 +0200 [thread overview]
Message-ID: <email@example.com> (raw)
On Wed, Apr 14 2021 at 11:11, Paul E. McKenney wrote:
> On Wed, Apr 14, 2021 at 10:57:57AM +0200, Uladzislau Rezki wrote:
>> On Wed, Apr 14, 2021 at 09:13:22AM +0200, Sebastian Andrzej Siewior wrote:
>> At the same time Paul made another patch:
>> softirq: Don't try waking ksoftirqd before it has been spawned
>> it allows us to keep RCU-tasks initialization before even
>> early_initcall() where it is now and let our rcu-self-test
>> to be completed without any hanging.
> In short, this window of time in which it is not possible to reliably
> wait on a softirq handler has caused trouble, just as several other
> similar boot-sequence time windows have caused trouble in the past.
> It therefore makes sense to just eliminate this problem, and prevent
> future developers from facing inexplicable silent boot-time hangs.
> We can move the spawning of ksoftirqd kthreads earlier, but that
> simply narrows the window. It does not eliminate the problem.
> I can easily believe that this might have -rt consequences that need
> attention. For your amusement, I will make a few guesses as to what
> these might be:
> o Back-of-interrupt softirq handlers degrade real-time response.
> This should not be a problem this early in boot, and once the
> ksoftirqd kthreads are spawned, there will never be another
> back-of-interrupt softirq handler in kernels that have
> force_irqthreads set, which includes -rt kernels.
Not a problem obviously.
> o That !__this_cpu_read(ksoftirqd) check remains at runtime, even
> though it always evaluates to false. I would be surprised if
> this overhead is measurable at the system level, but if it is,
> static branches should take care of this.
> o There might be a -rt lockdep check that isn't happy with
> back-of-interrupt softirq handlers. But such a lockdep check
> could be conditioned on __this_cpu_read(ksoftirqd), thus
> preventing it from firing during that short window at boot time.
It's not like there are only a handful of lockdep invocations which need
to be taken care of. The lockdep checks are mostly inside of lock
operations and if lockdep has recorded back-of-interrupt context once
during boot it will complain about irqs enabled context usage later on
no matter what.
If you can come up with a reasonable implementation of that without
losing valuable lockdep coverage and without creating a major mess in
the code then I'm all ears.
But lockdep is just one of the problems
> o The -rt kernels might be using locks to implement things like
> local_bh_disable(), in which case back-of-interrupt softirq
> handlers could result in self-deadlock. This could be addressed
> by disabling bh the old way up to the time that the ksoftirqd
> kthreads are created. Because these are created while the system
> is running on a single CPU (right?), a simple flag (or static
> branch) could be used to switch this behavior into lock-only
> mode long before the first real-time application can be spawned.
That has absolutely nothing to do with the first real-time application
at all and just looking at the local_bh_disable() part does not cut it
The point is that the fundamental assumption of RT to break the non-rt
semantics of interrupts and soft interrupts in order to rely on always
thread context based serialization is going down the drain with that.
Surely we can come up with yet another pile of horrible hacks to work
around that, which in turn will cause more problems than they solve.
But what for? Just to make it possible to issue rcu_whatever() during
early boot just because?
Give me _one_ serious technical reason why this is absolutely required
and why the accidental misplacement which might happen due to
unawareness, sloppyness or incompetence is reason enough to create a
horrible clusterfail just for purely academic reasons.
None of the usecases at hand did have any reason to depend on the early
boot behaviour of softirqs and unless you can come up with something
really compelling the proper solution is to revert this commit and add
the following instead:
@@ -74,7 +74,10 @@ static void wakeup_softirqd(void)
/* Interrupts are disabled: no need to stop preemption */
struct task_struct *tsk = __this_cpu_read(ksoftirqd);
- if (tsk && tsk->state != TASK_RUNNING)
+ if (WARN_ON_ONCE(!tsk))
+ if (tsk->state != TASK_RUNNING)
which will trigger on any halfways usefull CI infrastructure which cares
about the !default use cases of the kernel.
Putting a restriction like that onto the early boot process is not the
end of the world and might teach people who think that their oh so
important stuff is not that important at all especially not during the
early boot phase which is fragile enough already.
There is absolutely no need to proliferate cargo cult programming.
Keep It Simple ...
> So my turn. Did I miss anything?
next prev parent reply other threads:[~2021-04-14 23:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-11 13:43 [tip: core/rcu] softirq: Don't try waking ksoftirqd before it has been spawned tip-bot2 for Paul E. McKenney
2021-04-12 14:16 ` Thomas Gleixner
2021-04-12 18:36 ` Paul E. McKenney
2021-04-14 7:13 ` Sebastian Andrzej Siewior
2021-04-14 8:57 ` Uladzislau Rezki
2021-04-14 18:11 ` Paul E. McKenney
2021-04-14 23:54 ` Thomas Gleixner [this message]
2021-04-15 5:02 ` Paul E. McKenney
2021-04-15 14:34 ` Uladzislau Rezki
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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;
as well as URLs for NNTP newsgroup(s).