From: Peter Zijlstra <peterz@infradead.org>
To: Esme <esploit@protonmail.ch>
Cc: Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
JJiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: PROBLEM: syzkaller found / reduced C repro for non-fatal unchecked MSR access error
Date: Fri, 11 Jan 2019 11:02:53 +0100 [thread overview]
Message-ID: <20190111100253.GO30894@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <z3BgwrH88cXG8bH06po3hzY6vkYpdvZWqzSGl4lLXojvzk-33tKzdK1NWsTL1Ta-CBG7GKAWYziBAfPKsGA2CV6MVkXT93Al3SUfArOnUQE=@protonmail.ch>
On Thu, Jan 10, 2019 at 11:21:16PM +0000, Esme wrote:
> Attached is a fairly small C repro I did not see any references to
> this possible flaw (unchecked MSR access) in relation to
> __NR_perf_event_open
>
> Attached is the config directly extracted from proc. This is the call
> stack in relation to the MSR access error (5.0.0-rc1+), I get a very
> similar stack running this test case on a stock Ubuntu
> "4.18.0-11-generic" (pasted after this one).
> -- Esme
>
> [ 70.228744] unchecked MSR access error: WRMSR to 0xc0010000 (tried to write 0x0000020000130076) at rIP: 0xffffffff812dde28 (native_write_msr+0x8/0x30)
That's K7_EVNTSEL0. What kind of hardware are you running this on?
next prev parent reply other threads:[~2019-01-11 10:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-10 23:21 PROBLEM: syzkaller found / reduced C repro for non-fatal unchecked MSR access error Esme
2019-01-11 10:02 ` Peter Zijlstra [this message]
2019-01-11 13:37 ` Esme
2019-01-11 13:59 ` Peter Zijlstra
2019-01-11 14:21 ` Esme
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=20190111100253.GO30894@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=esploit@protonmail.ch \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox