[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6e1205c8-dd63-8866-9b9a-7db3bd432186@fb.com>
Date: Wed, 24 Apr 2019 22:37:45 +0000
From: Yonghong Song <yhs@...com>
To: Matt Mullins <mmullins@...com>, Andrew Hall <hall@...com>,
"ast@...nel.org" <ast@...nel.org>,
"bpf@...r.kernel.org" <bpf@...r.kernel.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Daniel Borkmann" <daniel@...earbox.net>,
Martin Lau <kafai@...com>, Song Liu <songliubraving@...com>,
Steven Rostedt <rostedt@...dmis.org>,
Ingo Molnar <mingo@...hat.com>
Subject: Re: [PATCH bpf-next v4 1/5] bpf: add writable context for raw
tracepoints
On 4/24/19 12:07 PM, Matt Mullins wrote:
> This is an opt-in interface that allows a tracepoint to provide a safe
> buffer that can be written from a BPF_PROG_TYPE_RAW_TRACEPOINT program.
> The size of the buffer must be a compile-time constant, and is checked
> before allowing a BPF program to attach to a tracepoint that uses this
> feature.
>
> The pointer to this buffer will be the first argument of tracepoints
> that opt in; the pointer is valid and can be bpf_probe_read() by both
> BPF_PROG_TYPE_RAW_TRACEPOINT and BPF_PROG_TYPE_RAW_TRACEPOINT_WRITABLE
> programs that attach to such a tracepoint, but the buffer to which it
> points may only be written by the latter.
>
> Signed-off-by: Matt Mullins <mmullins@...com>
Acked-by: Yonghong Song <yhs@...com>
Powered by blists - more mailing lists