linux-kernel - Re: possible deadlock in __perf_install_in

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>] [day] [month] [year] [list]

Date:   Mon, 22 Aug 2022 15:30:59 +0200
From:   Peter Zijlstra <peterz@...radead.org>
To:     王海弛 <wanghaichi@....edu.cn>
Cc:     mingo@...hat.com, acme@...nel.org, mark.rutland@....com,
        alexander.shishkin@...ux.intel.com, jolsa@...hat.com,
        namhyung@...nel.org, ast@...nel.org, daniel@...earbox.net,
        andrii@...nel.org, kafai@...com, songliubraving@...com, yhs@...com,
        john.fastabend@...il.com, kpsingh@...nel.org,
        linux-perf-users@...r.kernel.org, linux-kernel@...r.kernel.org,
        netdev@...r.kernel.org, bpf@...r.kernel.org,
        syzkaller@...glegroups.com, lishuochuan@....edu.cn
Subject: Re: possible deadlock in __perf_install_in_context

On Mon, Aug 22, 2022 at 09:12:40PM +0800, 王海弛 wrote:
> Dear Linux maintainers and reviewers:
> We would like to report a linux kernel bug, found by a modified version of syzkaller.
> May affected file: arch/x86/events/core.c, include/linux/perf_event.h
> Kernel Version: 8fe31e0995f048d16b378b90926793a0aa4af1e5
> Kernel Config: see attach, linux.config
> Syzkaller Version: 3666edfeb55080ebe138d77417fa96fe2555d6bb
> reproducing program: see attach, reproducing.txt (There are syz-reproducing program, C reproducing program and crash report created by syzkaller, both of which can replay the crash)
> Feel free to  email us if any other infomations are needed. Hope the provided materials will help finding and fixing the bug.
> The full log crash log are as follows:(also in the attach, crash.report)
> -----------------
> 
> 
> unchecked MSR access error: WRMSR to 0x188 (tried to write 0x0000000300530000) at rIP: 0xffffffff810287de (__wrmsr arch/x86/include/asm/msr.h:103 [inline])
> unchecked MSR access error: WRMSR to 0x188 (tried to write 0x0000000300530000) at rIP: 0xffffffff810287de (native_write_msr arch/x86/include/asm/msr.h:160 [inline])
> unchecked MSR access error: WRMSR to 0x188 (tried to write 0x0000000300530000) at rIP: 0xffffffff810287de (wrmsrl arch/x86/include/asm/msr.h:281 [inline])
> unchecked MSR access error: WRMSR to 0x188 (tried to write 0x0000000300530000) at rIP: 0xffffffff810287de (__x86_pmu_enable_event arch/x86/events/intel/../perf_event.h:1120 [inline])
> unchecked MSR access error: WRMSR to 0x188 (tried to write 0x0000000300530000) at rIP: 0xffffffff810287de (intel_pmu_enable_event+0x3ce/0xfe0 arch/x86/events/intel/core.c:2693)

I'm guess this is some sort of broken virt setup?