From: David Miller <davem@davemloft.net>
To: yhs@fb.com
Cc: peterz@infradead.org, rostedt@goodmis.org, ast@fb.com,
daniel@iogearbox.net, netdev@vger.kernel.org, kernel-team@fb.com
Subject: Re: [PATCH net-next v4 0/2] bpf: add support for sys_{enter|exit}_* tracepoints
Date: Mon, 07 Aug 2017 14:10:12 -0700 (PDT) [thread overview]
Message-ID: <20170807.141012.1406184213867808884.davem@davemloft.net> (raw)
In-Reply-To: <20170804230010.2792119-1-yhs@fb.com>
From: Yonghong Song <yhs@fb.com>
Date: Fri, 4 Aug 2017 16:00:08 -0700
> Currently, bpf programs cannot be attached to sys_enter_* and sys_exit_*
> style tracepoints. The main reason is that syscalls/sys_enter_* and syscalls/sys_exit_*
> tracepoints are treated differently from other tracepoints and there
> is no bpf hook to it.
>
> This patch set adds bpf support for these syscalls tracepoints and also
> adds a test case for it.
>
> Changelogs:
> v3 -> v4:
> - Check the legality of ctx offset access for syscall tracepoint as well.
> trace_event_get_offsets will return correct max offset for each
> specific syscall tracepoint.
> - Use variable length array to avoid hardcode 6 as the maximum
> arguments beyond syscall_nr.
> v2 -> v3:
> - Fix a build issue
> v1 -> v2:
> - Do not use TRACE_EVENT_FL_CAP_ANY to identify syscall tracepoint.
> Instead use trace_event_call->class.
Series applied, thank you.
prev parent reply other threads:[~2017-08-07 21:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-04 23:00 [PATCH net-next v4 0/2] bpf: add support for sys_{enter|exit}_* tracepoints Yonghong Song
2017-08-04 23:00 ` [PATCH net-next v4 1/2] bpf: add support for sys_enter_* and sys_exit_* tracepoints Yonghong Song
2017-08-07 18:51 ` Alexei Starovoitov
2017-08-04 23:00 ` [PATCH net-next v4 2/2] bpf: add a test case for syscalls/sys_{enter|exit}_* tracepoints Yonghong Song
2017-08-07 18:12 ` Daniel Borkmann
2017-08-07 21:10 ` David Miller [this message]
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=20170807.141012.1406184213867808884.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ast@fb.com \
--cc=daniel@iogearbox.net \
--cc=kernel-team@fb.com \
--cc=netdev@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=yhs@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).