From: Linus Torvalds <torvalds@linux-foundation.org>
To: "Liang, Kan" <kan.liang@intel.com>
Cc: Don Zickus <dzickus@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"mingo@kernel.org" <mingo@kernel.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"babu.moger@oracle.com" <babu.moger@oracle.com>,
"atomlin@redhat.com" <atomlin@redhat.com>,
"prarit@redhat.com" <prarit@redhat.com>,
"peterz@infradead.org" <peterz@infradead.org>,
"eranian@google.com" <eranian@google.com>,
"acme@redhat.com" <acme@redhat.com>,
"ak@linux.intel.com" <ak@linux.intel.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH V2] kernel/watchdog: fix spurious hard lockups
Date: Mon, 14 Aug 2017 18:28:01 -0700 [thread overview]
Message-ID: <CA+55aFwFr4tDeVH+G7QwFWV+rUdDLQTvFrPX+ZT3wOx4Ew5tMw@mail.gmail.com> (raw)
In-Reply-To: <37D7C6CF3E00A74B8858931C1DB2F07753784A2B@SHSMSX103.ccr.corp.intel.com>
On Mon, Aug 14, 2017 at 6:16 PM, Liang, Kan <kan.liang@intel.com> wrote:
>
> We have confirmed that the hardlock with "speed up the hrtimer" patch is
> actually another issue.
Good.
However:
> Tim has already proposed a patch to fix it.
> Here is his patch. https://lkml.org/lkml/2017/8/14/1000
Ugh. I hate that patch, and hope we can find a proper fix for it. But
I'll respond separately to it, and it's independent of the watchdog
issue.
Linus
next prev parent reply other threads:[~2017-08-15 1:28 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-21 14:41 [PATCH V2] kernel/watchdog: fix spurious hard lockups kan.liang
2017-06-21 15:12 ` Thomas Gleixner
2017-06-21 15:47 ` Liang, Kan
2017-06-21 17:40 ` Prarit Bhargava
2017-06-21 17:07 ` Andi Kleen
2017-06-21 19:59 ` Thomas Gleixner
2017-06-21 21:53 ` Thomas Gleixner
2017-06-22 15:33 ` Thomas Gleixner
2017-06-22 15:44 ` Don Zickus
2017-06-22 15:48 ` Liang, Kan
2017-06-23 8:01 ` Thomas Gleixner
2017-06-23 16:29 ` Don Zickus
2017-06-23 21:50 ` Thomas Gleixner
2017-06-26 20:19 ` Don Zickus
2017-06-26 20:30 ` Thomas Gleixner
2017-06-27 20:12 ` Don Zickus
2017-06-27 20:49 ` Liang, Kan
2017-06-27 21:09 ` Don Zickus
2017-06-27 23:48 ` Andi Kleen
2017-06-28 19:00 ` Don Zickus
2017-06-28 20:14 ` Andi Kleen
2017-06-29 15:44 ` Don Zickus
2017-06-29 16:12 ` Andi Kleen
2017-06-29 16:26 ` Don Zickus
2017-06-29 16:36 ` Andi Kleen
2017-07-17 1:24 ` Liang, Kan
2017-07-17 7:14 ` Thomas Gleixner
2017-07-17 12:18 ` Liang, Kan
2017-07-17 13:13 ` Thomas Gleixner
2017-07-17 14:46 ` Liang, Kan
2017-07-17 15:00 ` Thomas Gleixner
2017-07-17 14:46 ` Don Zickus
2017-08-15 1:16 ` Liang, Kan
2017-08-15 1:28 ` Linus Torvalds [this message]
2017-08-15 7:50 ` Thomas Gleixner
2017-08-17 15:45 ` Liang, Kan
2017-08-18 10:39 ` [tip:core/urgent] kernel/watchdog: Prevent false positives with turbo modes tip-bot for Thomas Gleixner
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=CA+55aFwFr4tDeVH+G7QwFWV+rUdDLQTvFrPX+ZT3wOx4Ew5tMw@mail.gmail.com \
--to=torvalds@linux-foundation.org \
--cc=acme@redhat.com \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=atomlin@redhat.com \
--cc=babu.moger@oracle.com \
--cc=dzickus@redhat.com \
--cc=eranian@google.com \
--cc=kan.liang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=prarit@redhat.com \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
/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).