From: Martin KaFai Lau <martin.lau@linux.dev>
To: bpf@vger.kernel.org
Cc: 'Alexei Starovoitov ' <ast@kernel.org>,
'Andrii Nakryiko ' <andrii@kernel.org>,
'Daniel Borkmann ' <daniel@iogearbox.net>,
netdev@vger.kernel.org, kernel-team@meta.com
Subject: [PATCH v2 bpf-next 0/3] bpf: Add hwtstamp field for the sockops prog
Date: Mon, 7 Nov 2022 15:04:17 -0800 [thread overview]
Message-ID: <20221107230420.4192307-1-martin.lau@linux.dev> (raw)
From: Martin KaFai Lau <martin.lau@kernel.org>
The bpf-tc prog has already been able to access the
skb_hwtstamps(skb)->hwtstamp. This set extends the same hwtstamp
access to the sockops prog.
v2:
- Fixed the btf_dump selftest which depends on the
last member of 'struct bpf_sock_ops'.
Martin KaFai Lau (3):
bpf: Add hwtstamp field for the sockops prog
selftests/bpf: Fix incorrect ASSERT in the tcp_hdr_options test
selftests/bpf: Test skops->skb_hwtstamp
include/uapi/linux/bpf.h | 1 +
net/core/filter.c | 39 +++++++++++++++----
tools/include/uapi/linux/bpf.h | 1 +
.../selftests/bpf/prog_tests/btf_dump.c | 4 +-
.../bpf/prog_tests/tcp_hdr_options.c | 6 ++-
.../bpf/progs/test_misc_tcp_hdr_options.c | 4 ++
6 files changed, 43 insertions(+), 12 deletions(-)
--
2.30.2
next reply other threads:[~2022-11-07 23:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-07 23:04 Martin KaFai Lau [this message]
2022-11-07 23:04 ` [PATCH v2 bpf-next 1/3] bpf: Add hwtstamp field for the sockops prog Martin KaFai Lau
2022-11-07 23:04 ` [PATCH v2 bpf-next 2/3] selftests/bpf: Fix incorrect ASSERT in the tcp_hdr_options test Martin KaFai Lau
2022-11-08 3:07 ` wangyufen
2022-11-07 23:04 ` [PATCH v2 bpf-next 3/3] selftests/bpf: Test skops->skb_hwtstamp Martin KaFai Lau
2022-11-08 1:03 ` [PATCH v2 bpf-next 0/3] bpf: Add hwtstamp field for the sockops prog Yonghong Song
2022-11-11 21:20 ` patchwork-bot+netdevbpf
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=20221107230420.4192307-1-martin.lau@linux.dev \
--to=martin.lau@linux.dev \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kernel-team@meta.com \
--cc=netdev@vger.kernel.org \
/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).