From: Jason Xing <kerneljasonxing@xxxxxxxxx>
Date: Tue, 8 Oct 2024 17:51:01 +0800
> From: Jason Xing <kernelxing@xxxxxxxxxxx>
>
> Implement basic codes so that we later can easily add each tx points.
> Introducing BPF_SOCK_OPS_ALL_CB_FLAGS used as a test statement can help use
> control whether to output or not.
>
> Signed-off-by: Jason Xing <kernelxing@xxxxxxxxxxx>
> ---
> include/uapi/linux/bpf.h | 5 ++++-
> net/core/skbuff.c | 18 ++++++++++++++++++
> tools/include/uapi/linux/bpf.h | 5 ++++-
> 3 files changed, 26 insertions(+), 2 deletions(-)
>
> diff --git a/include/uapi/linux/bpf.h b/include/uapi/linux/bpf.h
> index c6cd7c7aeeee..157e139ed6fc 100644
> --- a/include/uapi/linux/bpf.h
> +++ b/include/uapi/linux/bpf.h
> @@ -6900,8 +6900,11 @@ enum {
> * options first before the BPF program does.
> */
> BPF_SOCK_OPS_WRITE_HDR_OPT_CB_FLAG = (1<<6),
> + /* Call bpf when the kernel is generating tx timestamps.
> + */
> + BPF_SOCK_OPS_TX_TIMESTAMPING_OPT_CB_FLAG = (1<<7),
> /* Mask of all currently supported cb flags */
> - BPF_SOCK_OPS_ALL_CB_FLAGS = 0x7F,
> + BPF_SOCK_OPS_ALL_CB_FLAGS = 0xFF,
I remember this change makes two selftests fail and needs diff
in this link.
https://lore.kernel.org/bpf/20231016161134.25365-1-kuniyu@xxxxxxxxxx/
Also, adding a bpf selftest or extending some for this series
would be nice.
