From: Martin KaFai Lau <martin.lau@linux.dev>
To: Pauli Virtanen <pav@iki.fi>
Cc: netdev@vger.kernel.org, bpf@vger.kernel.org,
linux-bluetooth@vger.kernel.org, willemdebruijn.kernel@gmail.com,
kerneljasonxing@gmail.com
Subject: Re: [PATCH 3/3] [RFC] Bluetooth: enable bpf TX timestamping
Date: Tue, 1 Apr 2025 18:34:00 -0700 [thread overview]
Message-ID: <3546b79d-a09b-4971-abd7-ce18696a9536@linux.dev> (raw)
In-Reply-To: <bbd7fa454ed03ebba9bfe79590fb78a75d4f07db.1743337403.git.pav@iki.fi>
On 3/30/25 5:23 AM, Pauli Virtanen wrote:
> Emit timestamps also for BPF timestamping.
>
> ***
>
> The tskey management here is not quite right: see cover letter.
> ---
> include/net/bluetooth/bluetooth.h | 1 +
> net/bluetooth/hci_conn.c | 21 +++++++++++++++++++--
> 2 files changed, 20 insertions(+), 2 deletions(-)
>
> diff --git a/include/net/bluetooth/bluetooth.h b/include/net/bluetooth/bluetooth.h
> index bbefde319f95..3b2e59cedd2d 100644
> --- a/include/net/bluetooth/bluetooth.h
> +++ b/include/net/bluetooth/bluetooth.h
> @@ -383,6 +383,7 @@ struct bt_sock {
> struct list_head accept_q;
> struct sock *parent;
> unsigned long flags;
> + atomic_t bpf_tskey;
> void (*skb_msg_name)(struct sk_buff *, void *, int *);
> void (*skb_put_cmsg)(struct sk_buff *, struct msghdr *, struct sock *);
> };
> diff --git a/net/bluetooth/hci_conn.c b/net/bluetooth/hci_conn.c
> index 95972fd4c784..7430df1c5822 100644
> --- a/net/bluetooth/hci_conn.c
> +++ b/net/bluetooth/hci_conn.c
> @@ -28,6 +28,7 @@
> #include <linux/export.h>
> #include <linux/debugfs.h>
> #include <linux/errqueue.h>
> +#include <linux/bpf-cgroup.h>
>
> #include <net/bluetooth/bluetooth.h>
> #include <net/bluetooth/hci_core.h>
> @@ -3072,6 +3073,7 @@ void hci_setup_tx_timestamp(struct sk_buff *skb, size_t key_offset,
> const struct sockcm_cookie *sockc)
> {
> struct sock *sk = skb ? skb->sk : NULL;
> + bool have_tskey = false;
>
> /* This shall be called on a single skb of those generated by user
> * sendmsg(), and only when the sendmsg() does not return error to
> @@ -3096,6 +3098,20 @@ void hci_setup_tx_timestamp(struct sk_buff *skb, size_t key_offset,
>
> skb_shinfo(skb)->tskey = key - 1;
> }
> + have_tskey = true;
> + }
> +
> + if (cgroup_bpf_enabled(CGROUP_SOCK_OPS) &&
> + SK_BPF_CB_FLAG_TEST(sk, SK_BPF_CB_TX_TIMESTAMPING)) {
> + struct bt_sock *bt_sk = container_of(sk, struct bt_sock, sk);
> + int key = atomic_inc_return(&bt_sk->bpf_tskey);
I don't think it needs to add "atomic_t bpf_tskey". Allow the bpf to decide what
the skb_shinfo(skb)->tskey should be if it is not set by the userspace.
> +
> + if (!have_tskey)
> + skb_shinfo(skb)->tskey = key - 1;
> +
> + bpf_skops_tx_timestamping(sk, skb,
> + BPF_SOCK_OPS_TSTAMP_SENDMSG_CB);
> +
> }
> }
>
next prev parent reply other threads:[~2025-04-02 1:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-30 12:23 [PATCH 0/3] bpf: TSTAMP_COMPLETION_CB timestamping + enable it for Bluetooth Pauli Virtanen
2025-03-30 12:23 ` [PATCH 1/3] bpf: Add BPF_SOCK_OPS_TSTAMP_COMPLETION_CB callback Pauli Virtanen
2025-03-30 12:23 ` [PATCH 2/3] [RFC] bpf: allow non-TCP skbs for bpf_sock_ops_enable_tx_tstamp Pauli Virtanen
2025-03-30 12:23 ` [PATCH 3/3] [RFC] Bluetooth: enable bpf TX timestamping Pauli Virtanen
2025-04-02 1:34 ` Martin KaFai Lau [this message]
2025-04-02 16:56 ` Pauli Virtanen
2025-04-07 22:30 ` Martin KaFai Lau
2025-03-31 0:39 ` [PATCH 0/3] bpf: TSTAMP_COMPLETION_CB timestamping + enable it for Bluetooth Jason Xing
2025-03-31 8:37 ` Pauli Virtanen
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=3546b79d-a09b-4971-abd7-ce18696a9536@linux.dev \
--to=martin.lau@linux.dev \
--cc=bpf@vger.kernel.org \
--cc=kerneljasonxing@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pav@iki.fi \
--cc=willemdebruijn.kernel@gmail.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).