From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: <bp@alien8.de>
Cc: <tony.luck@intel.com>, <mattieu.souchaud@free.fr>,
<linux-edac@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86/mce: Don't unregister CPU hotplug notifier in error path
Date: Sun, 22 Jun 2014 10:25:50 -0700 (PDT) [thread overview]
Message-ID: <1acfd8b6-48f1-4324-9723-224a7f4f7367@default> (raw)
----- bp@alien8.de wrote:
> On Fri, Jun 20, 2014 at 10:04:37PM -0400, Boris Ostrovsky wrote:
> > I'll try it later but this doesn't look sufficient to me: we might
> not
> > reach this point if subsys_system_register() or
> zalloc_cpumask_var()
> > fail.
>
> If those fail, I'd say we have a much bigger problem than undeleted
> timers.
You can add
Tested-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
if you prefer to go with that version. I still think it's not 100% reliable (because of what I said above) but at least it fixes the current breakage.
>
> > We could register the notifier as the first thing in this routine
> > (probably after mce_available() succeeds).
>
> I guess...
Actually that won't work --- we need to register bus at sysfs first.
-boris
next reply other threads:[~2014-06-22 17:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-22 17:25 Boris Ostrovsky [this message]
2014-06-24 10:25 ` [PATCH] x86/mce: Don't unregister CPU hotplug notifier in error path Borislav Petkov
2014-06-24 10:34 ` [PATCH] x86, MCE: Robustify mcheck_init_device Borislav Petkov
-- strict thread matches above, loose matches on Subject: below --
2014-06-20 14:28 [PATCH] x86/mce: Don't unregister CPU hotplug notifier in error path Boris Ostrovsky
2014-06-20 15:23 ` Borislav Petkov
2014-06-20 15:41 ` Boris Ostrovsky
2014-06-20 15:58 ` Borislav Petkov
2014-06-20 16:16 ` Boris Ostrovsky
2014-06-20 17:52 ` Borislav Petkov
2014-06-20 19:39 ` Boris Ostrovsky
2014-06-20 20:03 ` Borislav Petkov
2014-06-20 20:16 ` Boris Ostrovsky
2014-06-20 20:29 ` Borislav Petkov
2014-06-20 20:43 ` Boris Ostrovsky
2014-06-20 21:11 ` Borislav Petkov
2014-06-21 2:04 ` Boris Ostrovsky
2014-06-21 10:08 ` Borislav Petkov
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=1acfd8b6-48f1-4324-9723-224a7f4f7367@default \
--to=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mattieu.souchaud@free.fr \
--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