From: Markus Trippelsdorf <markus@trippelsdorf.de>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [GIT pull] smp/hotplug: Removal of notifiers
Date: Mon, 26 Dec 2016 08:45:31 +0100 [thread overview]
Message-ID: <20161226074530.GA297@x4> (raw)
In-Reply-To: <alpine.DEB.2.20.1612251431340.3605@nanos>
On 2016.12.25 at 14:39 +0100, Thomas Gleixner wrote:
> Linus,
>
> please pull the latest smp-urgent-for-linus git tree from:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git smp-urgent-for-linus
>
> Thomas Gleixner (11):
> cpu/hotplug: Prevent overwriting of callbacks
The following commit:
commit dc280d93623927570da279e99393879dbbab39e7
Author: Thomas Gleixner <tglx@linutronix.de>
Date: Wed Dec 21 20:19:49 2016 +0100
cpu/hotplug: Prevent overwriting of callbacks
results in an early OOPs during boot on my AMD machine.
I haven't wrote down the entire backtrace, but basically things start to
go wrong in mce_threshold_create_device() from
arch/x86/kernel/cpu/mcheck/mce_amd.c.
# CONFIG_HOTPLUG_CPU is not set
Reverting the commit "fixes" the issue for me.
--
Markus
next prev parent reply other threads:[~2016-12-26 7:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-25 13:39 [GIT pull] smp/hotplug: Removal of notifiers Thomas Gleixner
2016-12-26 7:45 ` Markus Trippelsdorf [this message]
2016-12-26 11:06 ` Markus Trippelsdorf
2016-12-26 15:45 ` Markus Trippelsdorf
2016-12-26 17:31 ` Boris Ostrovsky
2016-12-26 18:21 ` Thomas Gleixner
2016-12-26 20:53 ` Boris Ostrovsky
2016-12-26 21:00 ` Borislav Petkov
2016-12-26 21:16 ` Thomas Gleixner
2016-12-26 21:42 ` 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=20161226074530.GA297@x4 \
--to=markus@trippelsdorf.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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.