From: Vince Weaver <vincent.weaver@maine.edu>
To: linux-kernel@vger.kernel.org
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>
Subject: [perf] fuzzer triggers unchecked MSR access error: WRMSR to 0x318
Date: Wed, 28 Jul 2021 12:49:43 -0400 (EDT) [thread overview]
Message-ID: <37881148-a43e-5fd4-817c-a875adc7a15f@maine.edu> (raw)
Hello
ther perf_fuzzer on current linux-git on a Haswell system triggers the
following.
I've truncated the call chain, as it goes on for quite a while, let me
know if you want/need more information.
Vince
[32694.087403] unchecked MSR access error: WRMSR to 0x318 (tried to write 0x0000000000000000) at rIP: 0xffffffff8106f854 (native_write_msr+0x4/0x20)
[32694.101374] Call Trace:
[32694.103974] perf_clear_dirty_counters+0x86/0x100
[32694.109027] switch_mm_irqs_off+0x1d0/0x430
[32694.113498] __schedule+0x29f/0x1490
[32694.117300] ? cr4_update_irqsoff+0x2a/0x30
[32694.121762] ? switch_mm_irqs_off+0x1ba/0x430
[32694.126418] ? rcu_eqs_exit.constprop.0+0x2e/0x60
[32694.131515] ? cpuidle_enter_state+0xb7/0x350
[32694.136152] schedule_idle+0x26/0x40
[32694.139974] do_idle+0x16e/0x280
[32694.143421] cpu_startup_entry+0x19/0x20
[32694.147643] secondary_startup_64_no_verify+0xb0/0xbb
[32694.973583] Call Trace:
[32694.976215] perf_clear_dirty_counters+0x86/0x100
[32694.981290] switch_mm_irqs_off+0x1d0/0x430
[32694.985797] __schedule+0x29f/0x1490
[32694.989664] ? cr4_update_irqsoff+0x2a/0x30
[32694.994134] ? switch_mm_irqs_off+0x1ba/0x430
[32694.998789] ? rcu_eqs_exit.constprop.0+0x2e/0x60
[32695.003831] ? cpuidle_enter_state+0xb7/0x350
[32695.008521] schedule_idle+0x26/0x40
[32695.012362] do_idle+0x16e/0x280
[32695.015838] cpu_startup_entry+0x19/0x20
[32695.020041] secondary_startup_64_no_verify+0xb0/0xbb
[32695.126530] Call Trace:
[32695.129184] perf_clear_dirty_counters+0x86/0x100
[32695.134268] switch_mm_irqs_off+0x1d0/0x430
[32695.138757] __schedule+0x29f/0x1490
[32695.142577] ? tick_nohz_get_sleep_length+0x6b/0xa0
[32695.147806] ? rcu_eqs_exit.constprop.0+0x2e/0x60
[32695.152806] ? cpuidle_enter_state+0xb7/0x350
[32695.157500] schedule_idle+0x26/0x40
[32695.161342] do_idle+0x16e/0x280
[32695.164798] cpu_startup_entry+0x19/0x20
[32695.169010] secondary_startup_64_no_verify+0xb0/0xbb
next reply other threads:[~2021-07-28 16:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-28 16:49 Vince Weaver [this message]
2021-07-29 9:14 ` [perf] fuzzer triggers unchecked MSR access error: WRMSR to 0x318 Peter Zijlstra
2021-07-29 13:21 ` Liang, Kan
2021-07-29 15:30 ` Peter Zijlstra
2021-08-02 11:40 ` Like Xu
2021-07-29 16:54 ` Vince Weaver
2021-08-05 9:34 ` [tip: perf/urgent] perf/x86: Fix out of bound MSR access tip-bot2 for Peter Zijlstra
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=37881148-a43e-5fd4-817c-a875adc7a15f@maine.edu \
--to=vincent.weaver@maine.edu \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.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;
as well as URLs for NNTP newsgroup(s).