From: Ingo Molnar <mingo@elte.hu>
To: Andi Kleen <andi@firstfloor.org>
Cc: Shaohua Li <shaohua.li@intel.com>,
lkml <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [PATCH] x86 MCE: shut up lockdep warning
Date: Fri, 8 May 2009 11:10:15 +0200 [thread overview]
Message-ID: <20090508091015.GA2038@elte.hu> (raw)
In-Reply-To: <20090508064517.GX23223@one.firstfloor.org>
* Andi Kleen <andi@firstfloor.org> wrote:
> On Fri, May 08, 2009 at 11:47:09AM +0800, Shaohua Li wrote:
> > lockdep report below warning when I try to offline one cpu:
> > [ 110.835487] =================================
> > [ 110.835616] [ INFO: inconsistent lock state ]
> > [ 110.835688] 2.6.30-rc4-00336-g8c9ed89 #52
> > [ 110.835757] ---------------------------------
> > [ 110.835828] inconsistent {HARDIRQ-ON-W} -> {IN-HARDIRQ-W} usage.
> > [ 110.835908] swapper/0 [HC1[1]:SC0[0]:HE0:SE1] takes:
> > [ 110.835982] (cmci_discover_lock){?.+...}, at: [<ffffffff80236dc0>] cmci_clear+0x30/0x9b
> >
> > smp_call_function_single() will disable interrupt. moving mce reenable/disable
> > to workqueue, so no irq is disabled.
>
> Looks good. Thanks.
>
> Acked-by: Andi Kleen <ak@linux.intel.com>
The report is useful, but the fix does not look good at all, and you
should never have acked it:
- it works around a lockdep warning
- you did not realize the real bug while the warning was plain
- plus the patch introduces a fragile (because complex)
work_on_cpu() call into the CPU hotplug path, which could have
caused followup regressions.
Please also Cc: the relevant upstream subsystem maintainers in such
cases (the x86 maintaiers in this case).
Thanks,
Ingo
next prev parent reply other threads:[~2009-05-08 9:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-08 3:47 [PATCH] x86 MCE: shut up lockdep warning Shaohua Li
2009-05-08 6:45 ` Andi Kleen
2009-05-08 9:10 ` Ingo Molnar [this message]
2009-05-08 9:37 ` Andi Kleen
2009-05-08 12:14 ` Shaohua Li
2009-05-08 8:17 ` Hidetoshi Seto
2009-05-08 8:28 ` [PATCH] x86 MCE: yet another " Hidetoshi Seto
2009-05-08 9:07 ` [tip:x86/urgent] x86: MCE: make cmci_discover_lock irq-safe tip-bot for Hidetoshi Seto
2009-05-08 8:34 ` [PATCH] x86 MCE: shut up lockdep warning Peter Zijlstra
2009-05-08 19:11 ` Andi Kleen
2009-05-08 9:04 ` Ingo Molnar
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=20090508091015.GA2038@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shaohua.li@intel.com \
--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