From: Thomas Gleixner <tglx@linutronix.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [GIT pull] smp/hotplug updates for 4.13
Date: Tue, 11 Jul 2017 08:09:16 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1707110808040.1799@nanos> (raw)
In-Reply-To: <CA+55aFxeEnmx-8R1FLwRqamvMZuUqkHto8tadVBae+3WnLYbgA@mail.gmail.com>
On Sun, 9 Jul 2017, Linus Torvalds wrote:
> On Sun, Jul 9, 2017 at 2:07 AM, Thomas Gleixner <tglx@linutronix.de> wrote:
> >
> > + /* Wait for the CPU to reach CPUHP_AP_ONLINE_IDLE */
> > wait_for_completion(&st->done);
> > + BUG_ON(!cpu_online(cpu));
>
> I realize this isn't actually a new BUG_ON(), just a moved one, but
> can we *please* just agree to get rid of these machine-killing
> idiocies?
>
> The fact that it would be a bug if this triggers doesn't excuse it one
> whit. BUG_ON() is simply bad.
>
> Either it's a "this cannot happen", in which case it should be
> deleted, or it's a "if this ever happens, we really should notice it",
> in which case it should probably be a
>
> if (WARN_ON)ONCE(..))
> return -EBUSY;
>
> or something.
>
> That routine very much has an existing error path for failure to bring
> up a CPU, dammit!
>
> THERE IS NO EXCUSE FOR KILLING THE MACHINE THERE!
Agreed. I noticed when I moved the code, but then forgot. Will queue a fix.
Thanks,
tglx
next prev parent reply other threads:[~2017-07-11 6:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-09 9:07 Thomas Gleixner
2017-07-09 18:15 ` Linus Torvalds
2017-07-11 6:09 ` Thomas Gleixner [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-07-03 8:31 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=alpine.DEB.2.20.1707110808040.1799@nanos \
--to=tglx@linutronix.de \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®