From: Thomas Gleixner <tglx@linutronix.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Waiman Long <longman@redhat.com>
Cc: Qian Cai <cai@lca.pw>,
"Joel Fernandes \(Google\)" <joel@joelfernandes.org>,
"Paul E. McKenney" <paulmck@kernel.org>,
rcu@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Will Deacon <will@kernel.org>, Ingo Molnar <mingo@kernel.org>,
Frederic Weisbecker <fweisbec@gmail.com>
Subject: Re: Hard lockups due to "tick/common: Make tick_periodic() check for missing ticks"
Date: Fri, 20 Mar 2020 12:50:12 +0100 [thread overview]
Message-ID: <87zhcb2qkr.fsf@nanos.tec.linutronix.de> (raw)
In-Reply-To: <20200320130017.6457a1e8@canb.auug.org.au>
Stephen Rothwell <sfr@canb.auug.org.au> writes:
Thu, 19 Mar 2020 15:00:35 -0400 Waiman Long <longman@redhat.com> wrote:
>> I am fine for reverting the patch for now. I am still having some
>> trouble reproducing it and I have other tasks to work on right now. I
>> will get to the bottom of it and resubmit a new patch later on.
>
> I have reverted that commit from linux-next today.
I did the same in the tip tree.
next prev parent reply other threads:[~2020-03-20 11:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-06 4:06 PROVE_RCU_LIST + /proc/lockdep warning Qian Cai
2020-03-07 3:33 ` Hard lockups due to "tick/common: Make tick_periodic() check for missing ticks" Qian Cai
2020-03-08 21:18 ` Waiman Long
2020-03-19 13:58 ` Qian Cai
2020-03-19 19:00 ` Waiman Long
2020-03-20 2:00 ` Stephen Rothwell
2020-03-20 11:50 ` Thomas Gleixner [this message]
2020-03-07 17:16 ` PROVE_RCU_LIST + /proc/lockdep warning Joel Fernandes
2020-03-09 1:40 ` Boqun Feng
2020-03-10 18:42 ` Qian Cai
2020-03-11 3:30 ` Boqun Feng
2020-03-11 13:24 ` Qian Cai
2020-03-12 0:48 ` Boqun Feng
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=87zhcb2qkr.fsf@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=cai@lca.pw \
--cc=fweisbec@gmail.com \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mingo@kernel.org \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=rcu@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=will@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.