Messages in this thread | | | From | Vince Weaver <> | Date | Wed, 28 Jul 2021 12:49:43 -0400 (EDT) | Subject | [perf] fuzzer triggers unchecked MSR access error: WRMSR to 0x318 |
| |
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
| |