linux-kernel - Re: perf: perf_fuzzer quickly locks up on 4.15-rc7

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

Message-ID: <20180109130957.52b8d9ce@vmware.local.home>
Date:   Tue, 9 Jan 2018 13:09:57 -0500
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Peter Zijlstra <peterz@...radead.org>
Cc:     Vince Weaver <vincent.weaver@...ne.edu>,
        Ingo Molnar <mingo@...nel.org>, linux-kernel@...r.kernel.org,
        Ingo Molnar <mingo@...hat.com>,
        Arnaldo Carvalho de Melo <acme@...nel.org>,
        Thomas Gleixner <tglx@...utronix.de>
Subject: Re: perf: perf_fuzzer quickly locks up on 4.15-rc7

On Tue, 9 Jan 2018 19:02:07 +0100
Peter Zijlstra <peterz@...radead.org> wrote:

> This would globally serialize all perf_ioctl()'s, also that event_mutex
> is for trace_events and really does not belong in perf.
> 
> So no, I really rather would not do this.
> 
> The alternative I was thinking of was lifting the cpuhp lock out from
> under event_mutex, that would also break the chain, but would probably
> be lots of work for trace bits.

I think we tried that once, and it became an never ending whack a mole
process. I prefer not to do that either. 

How bad is your work around patch that you posted?

-- Steve