From: Yonghong Song <yhs@fb.com>
To: Matt Mullins <mmullins@fb.com>, Andrew Hall <hall@fb.com>,
"ast@kernel.org" <ast@kernel.org>,
"bpf@vger.kernel.org" <bpf@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Daniel Borkmann" <daniel@iogearbox.net>,
Martin Lau <kafai@fb.com>, Song Liu <songliubraving@fb.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ingo Molnar <mingo@redhat.com>
Subject: Re: [PATCH bpf-next v4 1/5] bpf: add writable context for raw tracepoints
Date: Wed, 24 Apr 2019 22:37:45 +0000 [thread overview]
Message-ID: <6e1205c8-dd63-8866-9b9a-7db3bd432186@fb.com> (raw)
In-Reply-To: <20190424190721.24453-2-mmullins@fb.com>
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@fb.com>
Acked-by: Yonghong Song <yhs@fb.com>
next prev parent reply other threads:[~2019-04-24 22:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-24 19:07 [PATCH bpf-next v4 0/5] writable contexts for bpf raw tracepoints Matt Mullins
2019-04-24 19:07 ` [PATCH bpf-next v4 1/5] bpf: add writable context for " Matt Mullins
2019-04-24 22:37 ` Yonghong Song [this message]
2019-04-24 19:07 ` [PATCH bpf-next v4 2/5] nbd: trace sending nbd requests Matt Mullins
2019-04-24 19:07 ` [PATCH bpf-next v4 3/5] nbd: add tracepoints for send/receive timing Matt Mullins
2019-04-24 19:07 ` [PATCH bpf-next v4 4/5] tools: sync bpf.h Matt Mullins
2019-04-24 22:38 ` Yonghong Song
2019-04-24 19:07 ` [PATCH bpf-next v4 5/5] selftests: bpf: test writable buffers in raw tps Matt Mullins
2019-04-24 22:56 ` Yonghong Song
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6e1205c8-dd63-8866-9b9a-7db3bd432186@fb.com \
--to=yhs@fb.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=hall@fb.com \
--cc=kafai@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mmullins@fb.com \
--cc=netdev@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=songliubraving@fb.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).