From: Paolo Abeni <pabeni@redhat.com>
To: Xin Long <lucien.xin@gmail.com>, network dev <netdev@vger.kernel.org>
Cc: davem@davemloft.net, kuba@kernel.org,
Eric Dumazet <edumazet@google.com>,
Simon Horman <horms@kernel.org>,
Stefan Metzmacher <metze@samba.org>,
Moritz Buhl <mbuhl@openbsd.org>,
Tyler Fanelli <tfanelli@redhat.com>,
Pengtao He <hepengtao@xiaomi.com>,
linux-cifs@vger.kernel.org, Steve French <smfrench@gmail.com>,
Namjae Jeon <linkinjeon@kernel.org>,
Paulo Alcantara <pc@manguebit.com>, Tom Talpey <tom@talpey.com>,
kernel-tls-handshake@lists.linux.dev,
Chuck Lever <chuck.lever@oracle.com>,
Jeff Layton <jlayton@kernel.org>,
Benjamin Coddington <bcodding@redhat.com>,
Steve Dickson <steved@redhat.com>, Hannes Reinecke <hare@suse.de>,
Alexander Aring <aahringo@redhat.com>,
David Howells <dhowells@redhat.com>,
Cong Wang <xiyou.wangcong@gmail.com>,
"D . Wythe" <alibuda@linux.alibaba.com>,
Jason Baron <jbaron@akamai.com>,
illiliti <illiliti@protonmail.com>,
Sabrina Dubroca <sd@queasysnail.net>,
Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>,
Daniel Stenberg <daniel@haxx.se>,
Andy Gospodarek <andrew.gospodarek@broadcom.com>
Subject: Re: [PATCH net-next v2 07/15] quic: add connection id management
Date: Thu, 21 Aug 2025 15:55:04 +0200 [thread overview]
Message-ID: <1cf31726-bfb9-4909-a077-6c2c45e0720a@redhat.com> (raw)
In-Reply-To: <e7d5e3954c0d779e999dc50a9b03d9f7ed94dbd2.1755525878.git.lucien.xin@gmail.com>
On 8/18/25 4:04 PM, Xin Long wrote:
> This patch introduces 'struct quic_conn_id_set' for managing Connection
> IDs (CIDs), which are represented by 'struct quic_source_conn_id'
> and 'struct quic_dest_conn_id'.
>
> It provides helpers to add and remove CIDs from the set, and handles
> insertion of source CIDs into the global connection ID hash table
> when necessary.
>
> - quic_conn_id_add(): Add a new Connection ID to the set, and inserts
> it to conn_id hash table if it is a source conn_id.
>
> - quic_conn_id_remove(): Remove connection IDs the set with sequence
> numbers less than or equal to a number.
It's unclear how many connections are expected to be contained in each
set. If more than an handful you should consider using RB-tree instead
of lists.
[...]
> +static void quic_source_conn_id_free(struct quic_source_conn_id *s_conn_id)
> +{
> + u8 *data = s_conn_id->common.id.data;
> + struct quic_hash_head *head;
> +
> + if (!hlist_unhashed(&s_conn_id->node)) {
> + head = quic_source_conn_id_head(sock_net(s_conn_id->sk), data);
> + spin_lock_bh(&head->s_lock);
> + hlist_del_init(&s_conn_id->node);
> + spin_unlock_bh(&head->s_lock);
> + }
> +
> + /* Freeing is deferred via RCU to avoid use-after-free during concurrent lookups. */
> + call_rcu(&s_conn_id->rcu, quic_source_conn_id_free_rcu);
> +}
> +
> +static void quic_conn_id_del(struct quic_common_conn_id *common)
> +{
> + list_del(&common->list);
> + if (!common->hashed) {
> + kfree(common);
> + return;
> + }
> + quic_source_conn_id_free((struct quic_source_conn_id *)common);
It looks like the above cast is not needed.
> +}
> +
> +/* Add a connection ID with sequence number and associated private data to the connection ID set. */
> +int quic_conn_id_add(struct quic_conn_id_set *id_set,
> + struct quic_conn_id *conn_id, u32 number, void *data)
> +{
> + struct quic_source_conn_id *s_conn_id;
> + struct quic_dest_conn_id *d_conn_id;
> + struct quic_common_conn_id *common;
> + struct quic_hash_head *head;
> + struct list_head *list;
> +
> + /* Locate insertion point to keep list ordered by number. */
> + list = &id_set->head;
> + list_for_each_entry(common, list, list) {
> + if (number == common->number)
> + return 0; /* Ignore if it is already exists on the list. */
> + if (number < common->number) {
> + list = &common->list;
> + break;
> + }
> + }
> +
> + if (conn_id->len > QUIC_CONN_ID_MAX_LEN)
> + return -EINVAL;
> + common = kzalloc(id_set->entry_size, GFP_ATOMIC);
> + if (!common)
> + return -ENOMEM;
> + common->id = *conn_id;
> + common->number = number;
> + if (id_set->entry_size == sizeof(struct quic_dest_conn_id)) {
> + /* For destination connection IDs, copy the stateless reset token if available. */
> + if (data) {
> + d_conn_id = (struct quic_dest_conn_id *)common;
> + memcpy(d_conn_id->token, data, QUIC_CONN_ID_TOKEN_LEN);
> + }
> + } else {
> + /* For source connection IDs, mark as hashed and insert into the global source
> + * connection ID hashtable.
> + */
> + common->hashed = 1;
> + s_conn_id = (struct quic_source_conn_id *)common;
> + s_conn_id->sk = data;
> +
> + head = quic_source_conn_id_head(sock_net(s_conn_id->sk), common->id.data);
> + spin_lock_bh(&head->s_lock);
> + hlist_add_head(&s_conn_id->node, &head->head);
> + spin_unlock_bh(&head->s_lock);
> + }
> + list_add_tail(&common->list, list);
It's unclear if/how id_set->list is protected vs concurrent accesses.
/P
next prev parent reply other threads:[~2025-08-21 13:55 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-18 14:04 [PATCH net-next v2 00/15] net: introduce QUIC infrastructure and core subcomponents Xin Long
2025-08-18 14:04 ` [PATCH net-next v2 01/15] net: define IPPROTO_QUIC and SOL_QUIC constants Xin Long
2025-08-18 14:31 ` Stefan Metzmacher
2025-08-18 16:20 ` Matthieu Baerts
2025-08-18 18:37 ` Xin Long
2025-08-19 8:10 ` Namjae Jeon
2025-08-21 8:24 ` Stefan Metzmacher
2025-08-18 14:04 ` [PATCH net-next v2 02/15] net: build socket infrastructure for QUIC protocol Xin Long
2025-08-21 11:17 ` Paolo Abeni
2025-08-23 18:38 ` Xin Long
2025-08-18 14:04 ` [PATCH net-next v2 03/15] quic: provide common utilities and data structures Xin Long
2025-08-21 12:58 ` Paolo Abeni
2025-08-23 18:15 ` Xin Long
2025-08-18 14:04 ` [PATCH net-next v2 04/15] quic: provide family ops for address and protocol Xin Long
2025-08-21 13:17 ` Paolo Abeni
2025-08-23 17:22 ` Xin Long
2025-08-18 14:04 ` [PATCH net-next v2 05/15] quic: provide quic.h header files for kernel and userspace Xin Long
2025-08-18 14:04 ` [PATCH net-next v2 06/15] quic: add stream management Xin Long
2025-08-21 13:43 ` Paolo Abeni
2025-08-23 17:14 ` Xin Long
2025-08-18 14:04 ` [PATCH net-next v2 07/15] quic: add connection id management Xin Long
2025-08-21 13:55 ` Paolo Abeni [this message]
2025-08-23 15:57 ` Xin Long
2025-08-22 17:10 ` Jason Baron
2025-08-23 16:15 ` Xin Long
2025-08-18 14:04 ` [PATCH net-next v2 08/15] quic: add path management Xin Long
2025-08-21 14:18 ` Paolo Abeni
2025-08-23 15:40 ` Xin Long
2025-08-18 14:04 ` [PATCH net-next v2 09/15] quic: add congestion control Xin Long
2025-08-18 14:04 ` [PATCH net-next v2 10/15] quic: add packet number space Xin Long
2025-08-18 14:04 ` [PATCH net-next v2 11/15] quic: add crypto key derivation and installation Xin Long
2025-08-18 14:04 ` [PATCH net-next v2 12/15] quic: add crypto packet encryption and decryption Xin Long
2025-08-18 14:04 ` [PATCH net-next v2 13/15] quic: add timer management Xin Long
2025-08-18 14:04 ` [PATCH net-next v2 14/15] quic: add frame encoder and decoder base Xin Long
2025-08-18 14:04 ` [PATCH net-next v2 15/15] quic: add packet builder and parser base Xin Long
2025-08-23 15:20 ` [PATCH net-next v2 00/15] net: introduce QUIC infrastructure and core subcomponents John Ericson
2025-08-24 17:57 ` Xin Long
2025-08-26 21:48 ` Xin Long
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=1cf31726-bfb9-4909-a077-6c2c45e0720a@redhat.com \
--to=pabeni@redhat.com \
--cc=aahringo@redhat.com \
--cc=alibuda@linux.alibaba.com \
--cc=andrew.gospodarek@broadcom.com \
--cc=bcodding@redhat.com \
--cc=chuck.lever@oracle.com \
--cc=daniel@haxx.se \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=edumazet@google.com \
--cc=hare@suse.de \
--cc=hepengtao@xiaomi.com \
--cc=horms@kernel.org \
--cc=illiliti@protonmail.com \
--cc=jbaron@akamai.com \
--cc=jlayton@kernel.org \
--cc=kernel-tls-handshake@lists.linux.dev \
--cc=kuba@kernel.org \
--cc=linkinjeon@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=lucien.xin@gmail.com \
--cc=marcelo.leitner@gmail.com \
--cc=mbuhl@openbsd.org \
--cc=metze@samba.org \
--cc=netdev@vger.kernel.org \
--cc=pc@manguebit.com \
--cc=sd@queasysnail.net \
--cc=smfrench@gmail.com \
--cc=steved@redhat.com \
--cc=tfanelli@redhat.com \
--cc=tom@talpey.com \
--cc=xiyou.wangcong@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).