From: Borislav Petkov <bp@alien8.de>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Chuansheng Liu <chuansheng.liu@intel.com>,
linux-kernel@vger.kernel.org, tglx@linutronix.de,
mingo@redhat.com, hpa@zytor.com
Subject: Re: [PATCH v2] x86/mce/therm_throt: Fix the access of uninitialized therm_work
Date: Mon, 13 Jan 2020 10:05:09 +0100 [thread overview]
Message-ID: <20200113090509.GC13310@zn.tnic> (raw)
In-Reply-To: <20200110182929.GA20511@agluck-desk2.amr.corp.intel.com>
On Fri, Jan 10, 2020 at 10:29:29AM -0800, Luck, Tony wrote:
> On Tue, Jan 07, 2020 at 12:41:16AM +0000, Chuansheng Liu wrote:
> > In my ICL platform, it can be reproduced in several times
> > of reboot stress. With this fix, the system keeps alive
> > for more than 200 times of reboot stress.
> >
> > V2: Boris shares a good suggestion that we can moving the
> > interrupt unmasking at the end of therm_work initialization.
> >
> > Signed-off-by: Chuansheng Liu <chuansheng.liu@intel.com>
>
> Looks good to me:
>
> Acked-by: Tony Luck <tony.luck@intel.com>
Thx.
This "ICL platform" - whatever that is - is this shipping already so
that this qualifies for stable@ or can it go the normal path?
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2020-01-13 9:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-07 0:41 [PATCH v2] x86/mce/therm_throt: Fix the access of uninitialized therm_work Chuansheng Liu
2020-01-10 18:29 ` Luck, Tony
2020-01-13 9:05 ` Borislav Petkov [this message]
2020-01-14 2:19 ` Liu, Chuansheng
2020-01-15 11:37 ` [tip: ras/urgent] x86/mce/therm_throt: Do not access " tip-bot2 for Chuansheng Liu
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=20200113090509.GC13310@zn.tnic \
--to=bp@alien8.de \
--cc=chuansheng.liu@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.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).