From: "Luck, Tony" <tony.luck@intel.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Laura Abbott <labbott@redhat.com>,
Andi Kleen <ak@linux.intel.com>, Jeremy Cline <jcline@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
"x86@kernel.org" <x86@kernel.org>,
"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: x86/mce: suspicious RCU usage in 4.13.4
Date: Wed, 1 Nov 2017 13:07:31 -0700 [thread overview]
Message-ID: <20171101200730.dvfhyf6baqphhrtz@intel.com> (raw)
On Wed, Nov 01, 2017 at 05:47:54PM +0100, Borislav Petkov wrote:
> On Wed, Nov 01, 2017 at 07:56:20AM -0700, Laura Abbott wrote:
> > Did these get queued up somewhere? I know last week was OSSEU/Ksummit
> > so people may still be playing catch-up.
>
> Ah, thanks for the reminder.
>
> /me goes and dusts it off.
>
> Ok, here it is, injecting some MCEs in a guest seems to work fine,
> mcelog logs them.
>
> Tony?
Yup. I did a bit more testing on bare metal with injection:
1) Just one error
Worked
2) "kill -STOP `pgrep mcelog`" ; inject 5 errors ; "kill -CONT `pgrep mcelog`"
Worked (all five errors reported correctly)
3) "kill -STOP `pgrep mcelog`" ; inject 35 errors ; "kill -CONT `pgrep mcelog`"
mcelog reported Warning: MCE buffer is overflowed.
First 32 (MCE_LOG_LEN) errors reported correctly.
Reviewed-and-tested-by: Tony Luck <tony.luck@intel.com>
-Tony
---
To unsubscribe from this list: send the line "unsubscribe linux-edac" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: "Luck, Tony" <tony.luck@intel.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Laura Abbott <labbott@redhat.com>,
Andi Kleen <ak@linux.intel.com>, Jeremy Cline <jcline@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
"x86@kernel.org" <x86@kernel.org>,
"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: x86/mce: suspicious RCU usage in 4.13.4
Date: Wed, 1 Nov 2017 13:07:31 -0700 [thread overview]
Message-ID: <20171101200730.dvfhyf6baqphhrtz@intel.com> (raw)
In-Reply-To: <20171101164754.xzzmskl4ngrqc5br@pd.tnic>
On Wed, Nov 01, 2017 at 05:47:54PM +0100, Borislav Petkov wrote:
> On Wed, Nov 01, 2017 at 07:56:20AM -0700, Laura Abbott wrote:
> > Did these get queued up somewhere? I know last week was OSSEU/Ksummit
> > so people may still be playing catch-up.
>
> Ah, thanks for the reminder.
>
> /me goes and dusts it off.
>
> Ok, here it is, injecting some MCEs in a guest seems to work fine,
> mcelog logs them.
>
> Tony?
Yup. I did a bit more testing on bare metal with injection:
1) Just one error
Worked
2) "kill -STOP `pgrep mcelog`" ; inject 5 errors ; "kill -CONT `pgrep mcelog`"
Worked (all five errors reported correctly)
3) "kill -STOP `pgrep mcelog`" ; inject 35 errors ; "kill -CONT `pgrep mcelog`"
mcelog reported Warning: MCE buffer is overflowed.
First 32 (MCE_LOG_LEN) errors reported correctly.
Reviewed-and-tested-by: Tony Luck <tony.luck@intel.com>
-Tony
next reply other threads:[~2017-11-01 20:07 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-01 20:07 Luck, Tony [this message]
2017-11-01 20:07 ` x86/mce: suspicious RCU usage in 4.13.4 Luck, Tony
-- strict thread matches above, loose matches on Subject: below --
2017-11-01 16:47 Borislav Petkov
2017-11-01 16:47 ` Borislav Petkov
2017-11-01 20:28 ` [tip:ras/urgent] x86/mcelog: Get rid of RCU remnants tip-bot for Borislav Petkov
2017-11-01 14:56 x86/mce: suspicious RCU usage in 4.13.4 Laura Abbott
2017-11-01 14:56 ` Laura Abbott
2017-10-16 18:28 Luck, Tony
2017-10-16 18:28 ` Luck, Tony
2017-10-15 9:40 Borislav Petkov
2017-10-15 9:40 ` Borislav Petkov
2017-10-12 22:13 Andi Kleen
2017-10-12 22:13 ` Andi Kleen
2017-10-12 9:02 Borislav Petkov
2017-10-12 9:02 ` Borislav Petkov
2017-10-11 23:11 Andi Kleen
2017-10-11 23:11 ` Andi Kleen
2017-10-11 21:34 Luck, Tony
2017-10-11 21:34 ` Luck, Tony
2017-10-11 11:50 Borislav Petkov
2017-10-11 11:50 ` Borislav Petkov
2017-10-10 20:13 Andi Kleen
2017-10-10 20:13 ` Andi Kleen
2017-10-10 20:08 Luck, Tony
2017-10-10 20:08 ` Luck, Tony
2017-10-10 19:44 Borislav Petkov
2017-10-10 19:44 ` Borislav Petkov
2017-10-10 19:00 Jeremy Cline
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=20171101200730.dvfhyf6baqphhrtz@intel.com \
--to=tony.luck@intel.com \
--cc=ak@linux.intel.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=jcline@redhat.com \
--cc=labbott@redhat.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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.