[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <61D63A44-E3D9-4E7F-BE08-B887C078F445@gmail.com>
Date: Tue, 09 Jun 2020 20:07:06 +0300
From: Ramon Fried <rfried.dev@...il.com>
To: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
CC: Tom Zanussi <zanussi@...nel.org>,
LKML <linux-kernel@...r.kernel.org>,
linux-rt-users <linux-rt-users@...r.kernel.org>,
Steven Rostedt <rostedt@...dmis.org>,
Thomas Gleixner <tglx@...utronix.de>,
Carsten Emde <C.Emde@...dl.org>,
John Kacur <jkacur@...hat.com>, Daniel Wagner <wagi@...om.org>,
Clark Williams <williams@...hat.com>,
Zhang Xiao <xiao.zhang@...driver.com>
Subject: Re: [PATCH RT 1/2] tasklet: Address a race resulting in double-enqueue
On June 9, 2020 7:42:13 PM GMT+03:00, Sebastian Andrzej Siewior <bigeasy@...utronix.de> wrote:
>On 2020-06-09 19:40:03 [+0300], Ramon Fried wrote:
>> Correction. normal kernel is running with RT enabled, crash kernel
>without.
>
>no RT and no SMP in your crash kernel? So this information in your
>first
>email would have saved me some timeā¦
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?
>
>Sebastian
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
Powered by blists - more mailing lists