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  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]
Date:   Wed, 30 Mar 2022 12:28:11 -0700
From:   Linus Torvalds <>
To:     Mathieu Desnoyers <>
Cc:     rostedt <>,
        linux-kernel <>,
        Beau Belgrave <>,
        Masami Hiramatsu <>,
        linux-trace-devel <>,
        bpf <>, netdev <>,
        Alexei Starovoitov <>
Subject: Re: [PATCH] tracing: Set user_events to BROKEN

On Wed, Mar 30, 2022 at 9:54 AM Mathieu Desnoyers
<> wrote:
> If we are not ready to commit to an ABI, perhaps it would be safer to ensure
> that include/uapi/linux/user_events.h is not installed with the uapi headers
> until it's ready.

I don't th8ink the uapi matters if the code then cannot be used.
There's no regression in that.

That said, if we leave the code in the kernel source tree, I feel like
we should probably at least compile-test it.

So maybe it should be marked as

        depends on BROKEN || COMPILE_TEST



Powered by blists - more mailing lists