wireguard-linux - WireGuard for the Linux kernel

Age	Commit message (Collapse)	Author	Files	Lines
2023-01-25	tracing: Add NULL checks for buffer in ring_buffer_free_read_page()	Jia-Ju Bai	1	-1/+6
	In a previous commit 7433632c9ff6, buffer, buffer->buffers and buffer->buffers[cpu] in ring_buffer_wake_waiters() can be NULL, and thus the related checks are added. However, in the same call stack, these variables are also used in ring_buffer_free_read_page(): tracing_buffers_release() ring_buffer_wake_waiters(iter->array_buffer->buffer) cpu_buffer = buffer->buffers[cpu] -> Add checks by previous commit ring_buffer_free_read_page(iter->array_buffer->buffer) cpu_buffer = buffer->buffers[cpu] -> No check Thus, to avod possible null-pointer derefernces, the related checks should be added. These results are reported by a static tool designed by myself. Link: https://lkml.kernel.org/r/20230113125501.760324-1-baijiaju1990@gmail.com Reported-by: TOTE Robot <oslab@tsinghua.edu.cn> Signed-off-by: Jia-Ju Bai <baijiaju1990@gmail.com> Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>
2023-01-25	ftrace: Add sample with custom ops	Mark Rutland	4	-0/+261
	When reworking core ftrace code or architectural ftrace code, it's often necessary to test/analyse/benchmark a number of ftrace_ops configurations. This patch adds a module which can be used to explore some of those configurations. I'm using this to benchmark various options for changing the way trampolines and handling of ftrace_ops work on arm64, and ensuring other architectures aren't adversely affected. For example, in a QEMU+KVM VM running on a 2GHz Xeon E5-2660 workstation, loading the module in various configurations produces: \| # insmod ftrace-ops.ko \| ftrace_ops: registering: \| relevant ops: 1 \| tracee: tracee_relevant [ftrace_ops] \| tracer: ops_func_nop [ftrace_ops] \| irrelevant ops: 0 \| tracee: tracee_irrelevant [ftrace_ops] \| tracer: ops_func_nop [ftrace_ops] \| saving registers: NO \| assist recursion: NO \| assist RCU: NO \| ftrace_ops: Attempted 100000 calls to tracee_relevant [ftrace_ops] in 1681558ns (16ns / call) \| # insmod ftrace-ops.ko nr_ops_irrelevant=5 \| ftrace_ops: registering: \| relevant ops: 1 \| tracee: tracee_relevant [ftrace_ops] \| tracer: ops_func_nop [ftrace_ops] \| irrelevant ops: 5 \| tracee: tracee_irrelevant [ftrace_ops] \| tracer: ops_func_nop [ftrace_ops] \| saving registers: NO \| assist recursion: NO \| assist RCU: NO \| ftrace_ops: Attempted 100000 calls to tracee_relevant [ftrace_ops] in 1693042ns (16ns / call) \| # insmod ftrace-ops.ko nr_ops_relevant=2 \| ftrace_ops: registering: \| relevant ops: 2 \| tracee: tracee_relevant [ftrace_ops] \| tracer: ops_func_nop [ftrace_ops] \| irrelevant ops: 0 \| tracee: tracee_irrelevant [ftrace_ops] \| tracer: ops_func_nop [ftrace_ops] \| saving registers: NO \| assist recursion: NO \| assist RCU: NO \| ftrace_ops: Attempted 100000 calls to tracee_relevant [ftrace_ops] in 11965582ns (119ns / call) \| # insmod ftrace-ops.ko save_regs=true \| ftrace_ops: registering: \| relevant ops: 1 \| tracee: tracee_relevant [ftrace_ops] \| tracer: ops_func_nop [ftrace_ops] \| irrelevant ops: 0 \| tracee: tracee_irrelevant [ftrace_ops] \| tracer: ops_func_nop [ftrace_ops] \| saving registers: YES \| assist recursion: NO \| assist RCU: NO \| ftrace_ops: Attempted 100000 calls to tracee_relevant [ftrace_ops] in 4459624ns (44ns / call) Link: https://lkml.kernel.org/r/20230103124912.2948963-4-mark.rutland@arm.com Cc: Florent Revest <revest@chromium.org> Acked-by: Masami Hiramatsu (Google) <mhiramat@kernel.org> Signed-off-by: Mark Rutland <mark.rutland@arm.com> Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>