From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Ramon Fried <rfried.dev@gmail.com>
Cc: Tom Zanussi <zanussi@kernel.org>,
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, 9 Jun 2020 19:10:43 +0200 [thread overview]
Message-ID: <20200609171043.vhvms7lowffqm6e4@linutronix.de> (raw)
In-Reply-To: <61D63A44-E3D9-4E7F-BE08-B887C078F445@gmail.com>
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.
Sebastian
next prev parent reply other threads:[~2020-06-09 17:10 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 [this message]
2020-06-09 17:14 ` Ramon Fried
2020-06-09 17:20 ` Tom Zanussi
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=20200609171043.vhvms7lowffqm6e4@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=C.Emde@osadl.org \
--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 \
--cc=zanussi@kernel.org \
/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).