linux-kernel - Re: possible deadlock in __perf_event_task_sched

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

Message-ID: <YT8HngbIcqA4Tfac@hirez.programming.kicks-ass.net>
Date:   Mon, 13 Sep 2021 10:11:10 +0200
From:   Peter Zijlstra <peterz@...radead.org>
To:     Hao Sun <sunhao.th@...il.com>
Cc:     acme@...nel.org, linux-perf-users@...r.kernel.org,
        mingo@...hat.com, alexander.shishkin@...ux.intel.com,
        andrii@...nel.org, ast@...nel.org, bpf@...r.kernel.org,
        daniel@...earbox.net, john.fastabend@...il.com, jolsa@...hat.com,
        kafai@...com, kpsingh@...nel.org, linux-kernel@...r.kernel.org,
        mark.rutland@....com, namhyung@...nel.org, netdev@...r.kernel.org,
        songliubraving@...com, yhs@...com
Subject: Re: possible deadlock in __perf_event_task_sched_out

On Mon, Sep 13, 2021 at 10:39:10AM +0800, Hao Sun wrote:
> Hello,
> 
> When using Healer to fuzz the latest Linux kernel, the following crash
> was triggered.
> 
> HEAD commit: 4b93c544e90e-thunderbolt: test: split up test cases
> git tree: upstream
> console output:
> https://drive.google.com/file/d/1Gy99NMo9JxZF6dHPdxnnb91n_jPJUQnA/view?usp=sharing
> kernel config: https://drive.google.com/file/d/1c0u2EeRDhRO-ZCxr9MP2VvAtJd6kfg-p/view?usp=sharing
> 
> Sorry, I don't have a reproducer for this crash, hope the symbolized
> report can help.
> If you fix this issue, please add the following tag to the commit:

This reads like a very badly configured VM, in part because the console
output is partial. That first Call trace: is ex_handler_wrmsr_unsafe,
but it is truncated, also the pr_warn_once() went missing.

Please take more care in configuring your VM before sending out more
bogus messages like this.