linux-kernel - RE: [PATCH 1/8] perf/x86/intel: Fix memory corruption

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <BC9B17E68BB84346BEE0B491BDB7D8AE28A6A801@ORSMSX101.amr.corp.intel.com>
Date:   Thu, 21 Mar 2019 23:16:17 +0000
From:   "DSouza, Nelson" <nelson.dsouza@...el.com>
To:     Peter Zijlstra <peterz@...radead.org>
CC:     Tony Jones <tonyj@...e.com>, Thomas Gleixner <tglx@...utronix.de>,
        Stephane Eranian <eranian@...gle.com>,
        Ingo Molnar <mingo@...nel.org>, "Jiri Olsa" <jolsa@...hat.com>,
        LKML <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH 1/8] perf/x86/intel: Fix memory corruption

Attached cpu hotplug test output while perf is running in the background. No WARN messages seen.

When I run the kexec command, it boots to bios. Haven't used kexec before. Still trying to figure that one out.

-----Original Message-----
From: Peter Zijlstra [mailto:peterz@...radead.org] 
Sent: Thursday, March 21, 2019 1:07 PM
To: DSouza, Nelson <nelson.dsouza@...el.com>
Cc: Tony Jones <tonyj@...e.com>; Thomas Gleixner <tglx@...utronix.de>; Stephane Eranian <eranian@...gle.com>; Ingo Molnar <mingo@...nel.org>; Jiri Olsa <jolsa@...hat.com>; LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/8] perf/x86/intel: Fix memory corruption

On Thu, Mar 21, 2019 at 07:47:50PM +0000, DSouza, Nelson wrote:
> Is the request to check whether the msr gets reset to default upon reboot of the machine ?

basically:

 - apply patch
 - start workload with 4 counter (on all CPUs), such that tfa-msr=1
 - try the following:
   o cpu hotplug
   o kexec

to see if the new WARN will trigger -- it should not.

View attachment "cpu_hotplug.txt" of type "text/plain" (921 bytes)