diff options
| author |   Jason Xing <kerneljasonxing@gmail.com> | 2025-02-20 15:29:33 +0800 |
|---|---|---|
| committer |   Martin KaFai Lau <martin.lau@kernel.org> | 2025-02-20 14:29:15 -0800 |
| commit | aa290f93a4af662b8d2d9e9df65798f9f24cecf3 (patch) | |
| tree | d0c448f8450d202852d38c200361bf8c5d8e779f /net/core/dev.c | |
| parent | bpf: Disable unsafe helpers in TX timestamping callbacks (diff) | |
| download | wireguard-linux-aa290f93a4af662b8d2d9e9df65798f9f24cecf3.tar.xz wireguard-linux-aa290f93a4af662b8d2d9e9df65798f9f24cecf3.zip | |
net-timestamp: Prepare for isolating two modes of SO_TIMESTAMPING
No functional changes here. Only add test to see if the orig_skb
matches the usage of application SO_TIMESTAMPING.
In this series, bpf timestamping and previous socket timestamping
are implemented in the same function __skb_tstamp_tx(). To test
the socket enables socket timestamping feature, this function
skb_tstamp_tx_report_so_timestamping() is added.
In the next patch, another check for bpf timestamping feature
will be introduced just like the above report function, namely,
skb_tstamp_tx_report_bpf_timestamping(). Then users will be able
to know the socket enables either or both of features.
Signed-off-by: Jason Xing <kerneljasonxing@gmail.com>
Signed-off-by: Martin KaFai Lau <martin.lau@kernel.org>
Reviewed-by: Willem de Bruijn <willemb@google.com>
Link: https://patch.msgid.link/20250220072940.99994-6-kerneljasonxing@gmail.com
Diffstat (limited to 'net/core/dev.c')
0 files changed, 0 insertions, 0 deletions