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
| ||
|
Message-ID: <CAHk-=wgZ0RccFsUhgKpdh130ydsY57bqaCGRQS7w3-ckgHP=OA@mail.gmail.com> Date: Wed, 30 Mar 2022 12:28:11 -0700 From: Linus Torvalds <torvalds@...ux-foundation.org> To: Mathieu Desnoyers <mathieu.desnoyers@...icios.com> Cc: rostedt <rostedt@...dmis.org>, linux-kernel <linux-kernel@...r.kernel.org>, Beau Belgrave <beaub@...ux.microsoft.com>, Masami Hiramatsu <mhiramat@...nel.org>, linux-trace-devel <linux-trace-devel@...r.kernel.org>, bpf <bpf@...r.kernel.org>, netdev <netdev@...r.kernel.org>, Alexei Starovoitov <alexei.starovoitov@...il.com> Subject: Re: [PATCH] tracing: Set user_events to BROKEN On Wed, Mar 30, 2022 at 9:54 AM Mathieu Desnoyers <mathieu.desnoyers@...icios.com> 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 instead? Linus
Powered by blists - more mailing lists