From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755235AbdKAUHd (ORCPT ); Wed, 1 Nov 2017 16:07:33 -0400 Received: from mga14.intel.com ([192.55.52.115]:12127 "EHLO mga14.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754972AbdKAUHc (ORCPT ); Wed, 1 Nov 2017 16:07:32 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.44,330,1505804400"; d="scan'208";a="330730742" Date: Wed, 1 Nov 2017 13:07:31 -0700 From: "Luck, Tony" To: Borislav Petkov Cc: Laura Abbott , Andi Kleen , Jeremy Cline , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , "x86@kernel.org" , "linux-edac@vger.kernel.org" , "linux-kernel@vger.kernel.org" Subject: Re: x86/mce: suspicious RCU usage in 4.13.4 Message-ID: <20171101200730.dvfhyf6baqphhrtz@intel.com> References: <9840bf0d-6756-75eb-1a2d-d3aace235244@redhat.com> <20171010194426.s7keveirclglx6vh@pd.tnic> <20171010200841.uhniuwc7pulqgmic@intel.com> <871smasqux.fsf@linux.intel.com> <20171011115020.i4gkcy5pjifh2zsm@pd.tnic> <3908561D78D1C84285E8C5FCA982C28F770038E5@ORSMSX114.amr.corp.intel.com> <20171015094046.6477zglnee3s75lc@pd.tnic> <20171016182843.wrtcelsqf2y2onze@intel.com> <6c5bf4d7-3f9d-a05e-78f4-a4a46868a311@redhat.com> <20171101164754.xzzmskl4ngrqc5br@pd.tnic> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20171101164754.xzzmskl4ngrqc5br@pd.tnic> User-Agent: NeoMutt/20170113 (1.7.2) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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