From: Tom Zanussi <zanussi@kernel.org>
To: Ramon Fried <rfried.dev@gmail.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Thomas Gleixner <tglx@linutronix.de>,
Carsten Emde <C.Emde@osadl.org>, John Kacur <jkacur@redhat.com>,
Daniel Wagner <wagi@monom.org>,
Clark Williams <williams@redhat.com>,
Zhang Xiao <xiao.zhang@windriver.com>
Subject: Re: [PATCH RT 1/2] tasklet: Address a race resulting in double-enqueue
Date: Tue, 09 Jun 2020 12:20:35 -0500 [thread overview]
Message-ID: <aee4ed8bdd405c1e0e964fef6d57f410267aa25a.camel@kernel.org> (raw)
In-Reply-To: <50AE5644-D046-4043-8A70-204D0BFEB67F@gmail.com>
Hi Ramon,
On Tue, 2020-06-09 at 20:14 +0300, Ramon Fried wrote:
>
> On June 9, 2020 8:10:43 PM GMT+03:00, Sebastian Andrzej Siewior <
> bigeasy@linutronix.de> wrote:
> > On 2020-06-09 20:07:06 [+0300], Ramon Fried wrote:
> > > Indeed
> > > I'm truly sorry, I thought our crash kernel is configured as RT
> > > as
> >
> > well.
> > > so, as I understand, if I build the RT kernel without preempt
> > > enabled
> >
> > I can hit this bug?
> >
> > Don't worry, I should have been better with the details in the log.
> >
> > So you should _always_ hit the warning/bug if you compile a kernel
> > without SMP and RT. If you enable one of these then everything
> > should
> > be
> > fine.
>
> Would there be a fix for that?
I haven't tested the fix yet, but can you try the below patch and see
if it fixes your broken case?
[PATCH] tasklet: Fix UP case for tasklet CHAINED state
commit 62d0a2a30cd0 (tasklet: Address a race resulting in
double-enqueue) addresses a problem that can result in a tasklet being
enqueued on two cpus at the same time by combining the RUN flag with a
new CHAINED flag, and relies on the combination to be present in order
to zero it out, which can never happen on (!SMP and !PREEMPT_RT_FULL)
because the RUN flag is SMP/PREEMPT_RT_FULL-only.
So make sure the above commit is only applied for the SMP ||
PREEMPT_RT_FULL case.
Signed-off-by: Tom Zanussi <zanussi@kernel.org>
---
kernel/softirq.c | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/kernel/softirq.c b/kernel/softirq.c
index 73dae64bfc9c..9bad7a16dc61 100644
--- a/kernel/softirq.c
+++ b/kernel/softirq.c
@@ -947,10 +947,12 @@ static void __tasklet_schedule_common(struct
tasklet_struct *t,
* is locked before adding it to the list.
*/
if (test_bit(TASKLET_STATE_SCHED, &t->state)) {
+#if defined(CONFIG_SMP) || defined(CONFIG_PREEMPT_RT_FULL)
if (test_and_set_bit(TASKLET_STATE_CHAINED, &t->state))
{
tasklet_unlock(t);
return;
}
+#endif
t->next = NULL;
*head->tail = t;
head->tail = &(t->next);
@@ -1044,7 +1046,11 @@ static void tasklet_action_common(struct
softirq_action *a,
again:
t->func(t->data);
+#if defined(CONFIG_SMP) || defined(CONFIG_PREEMPT_RT_FULL)
while (cmpxchg(&t->state, TASKLET_STATEF_RC, 0) !=
TASKLET_STATEF_RC) {
+#else
+ while (!tasklet_tryunlock(t)) {
+#endif
/*
* If it got disabled meanwhile, bail out:
*/
--
2.17.1
next prev parent reply other threads:[~2020-06-09 17:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-23 20:54 [PATCH RT 0/2] Linux v4.19.115-rt49-rc1 zanussi
2020-04-23 20:54 ` [PATCH RT 1/2] tasklet: Address a race resulting in double-enqueue zanussi
2020-06-04 16:04 ` Ramon Fried
2020-06-04 20:51 ` Tom Zanussi
2020-06-09 15:47 ` Sebastian Andrzej Siewior
2020-06-09 16:17 ` Tom Zanussi
2020-06-09 16:34 ` Sebastian Andrzej Siewior
2020-06-09 16:37 ` Ramon Fried
2020-06-09 16:40 ` Ramon Fried
2020-06-09 16:42 ` Sebastian Andrzej Siewior
2020-06-09 17:07 ` Ramon Fried
2020-06-09 17:10 ` Sebastian Andrzej Siewior
2020-06-09 17:14 ` Ramon Fried
2020-06-09 17:20 ` Tom Zanussi [this message]
2020-06-09 20:03 ` Ramon Fried
2020-06-09 20:09 ` Tom Zanussi
2020-06-09 16:57 ` Tom Zanussi
2020-04-23 20:54 ` [PATCH RT 2/2] Linux 4.19.115-rt49-rc1 zanussi
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=aee4ed8bdd405c1e0e964fef6d57f410267aa25a.camel@kernel.org \
--to=zanussi@kernel.org \
--cc=C.Emde@osadl.org \
--cc=bigeasy@linutronix.de \
--cc=jkacur@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=rfried.dev@gmail.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=wagi@monom.org \
--cc=williams@redhat.com \
--cc=xiao.zhang@windriver.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;
as well as URLs for NNTP newsgroup(s).