From: Paolo Abeni <pabeni@redhat.com>
To: John Ousterhout <ouster@cs.stanford.edu>, netdev@vger.kernel.org
Cc: edumazet@google.com, horms@kernel.org, kuba@kernel.org
Subject: Re: [PATCH net-next v6 07/12] net: homa: create homa_sock.h and homa_sock.c
Date: Thu, 23 Jan 2025 20:01:57 +0100 [thread overview]
Message-ID: <028f492f-41db-4c70-9527-cf0db03da4df@redhat.com> (raw)
In-Reply-To: <20250115185937.1324-8-ouster@cs.stanford.edu>
On 1/15/25 7:59 PM, John Ousterhout wrote:
> + spin_unlock_bh(&socktab->write_lock);
> +
> + return homa_socktab_next(scan);
> +}
> +
> +/**
> + * homa_socktab_next() - Return the next socket in an iteration over a socktab.
> + * @scan: State of the scan.
> + *
> + * Return: The next socket in the table, or NULL if the iteration has
> + * returned all of the sockets in the table. Sockets are not
> + * returned in any particular order. It's possible that the
> + * returned socket has been destroyed.
> + */
> +struct homa_sock *homa_socktab_next(struct homa_socktab_scan *scan)
> +{
> + struct homa_socktab_links *links;
> + struct homa_sock *hsk;
> +
> + while (1) {
> + while (!scan->next) {
> + struct hlist_head *bucket;
> +
> + scan->current_bucket++;
> + if (scan->current_bucket >= HOMA_SOCKTAB_BUCKETS)
> + return NULL;
> + bucket = &scan->socktab->buckets[scan->current_bucket];
> + scan->next = (struct homa_socktab_links *)
> + rcu_dereference(hlist_first_rcu(bucket));
The only caller for this function so far is not under RCU lock: you
should see a splat here if you build and run this code with:
CONFIG_LOCKDEP=y
(which in turn is highly encouraged)
> + }
> + links = scan->next;
> + hsk = links->sock;
> + scan->next = (struct homa_socktab_links *)
> + rcu_dereference(hlist_next_rcu(&links->hash_links));
homa_socktab_links is embedded into the home sock; if the RCU protection
is released and re-acquired after a homa_socktab_next() call, there is
no guarantee links/hsk are still around and the above statement could
cause UaF.
This homa_socktab things looks quite complex. A simpler implementation
could use a simple RCU list _and_ acquire a reference to the hsk before
releasing the RCU lock.
> + return hsk;
> + }
> +}
> +
> +/**
> + * homa_socktab_end_scan() - Must be invoked on completion of each scan
> + * to clean up state associated with the scan.
> + * @scan: State of the scan.
> + */
> +void homa_socktab_end_scan(struct homa_socktab_scan *scan)
> +{
> + spin_lock_bh(&scan->socktab->write_lock);
> + list_del(&scan->scan_links);
> + spin_unlock_bh(&scan->socktab->write_lock);
> +}
> +
> +/**
> + * homa_sock_init() - Constructor for homa_sock objects. This function
> + * initializes only the parts of the socket that are owned by Homa.
> + * @hsk: Object to initialize.
> + * @homa: Homa implementation that will manage the socket.
> + *
> + * Return: 0 for success, otherwise a negative errno.
> + */
> +int homa_sock_init(struct homa_sock *hsk, struct homa *homa)
> +{
> + struct homa_socktab *socktab = homa->port_map;
> + int starting_port;
> + int result = 0;
> + int i;
> +
> + spin_lock_bh(&socktab->write_lock);
A single contended lock for the whole homa sock table? Why don't you use
per bucket locks?
[...]
> +struct homa_rpc_bucket {
> + /**
> + * @lock: serves as a lock both for this bucket (e.g., when
> + * adding and removing RPCs) and also for all of the RPCs in
> + * the bucket. Must be held whenever manipulating an RPC in
> + * this bucket. This dual purpose permits clean and safe
> + * deletion and garbage collection of RPCs.
> + */
> + spinlock_t lock;
> +
> + /** @rpcs: list of RPCs that hash to this bucket. */
> + struct hlist_head rpcs;
> +
> + /**
> + * @id: identifier for this bucket, used in error messages etc.
> + * It's the index of the bucket within its hash table bucket
> + * array, with an additional offset to separate server and
> + * client RPCs.
> + */
> + int id;
On 64 bit arches this struct will have 2 4-bytes holes. If you reorder
the field:
spinlock_t lock;
int id;
struct hlist_head rpcs;
the struct size will decrease by 8 bytes.
> +};
> +
> +/**
> + * define HOMA_CLIENT_RPC_BUCKETS - Number of buckets in hash tables for
> + * client RPCs. Must be a power of 2.
> + */
> +#define HOMA_CLIENT_RPC_BUCKETS 1024
> +
> +/**
> + * define HOMA_SERVER_RPC_BUCKETS - Number of buckets in hash tables for
> + * server RPCs. Must be a power of 2.
> + */
> +#define HOMA_SERVER_RPC_BUCKETS 1024
> +
> +/**
> + * struct homa_sock - Information about an open socket.
> + */
> +struct homa_sock {
> + /* Info for other network layers. Note: IPv6 info (struct ipv6_pinfo
> + * comes at the very end of the struct, *after* Homa's data, if this
> + * socket uses IPv6).
> + */
> + union {
> + /** @sock: generic socket data; must be the first field. */
> + struct sock sock;
> +
> + /**
> + * @inet: generic Internet socket data; must also be the
> + first field (contains sock as its first member).
> + */
> + struct inet_sock inet;
> + };
Why adding this union? Just
struct inet_sock inet;
would do.
/P
next prev parent reply other threads:[~2025-01-23 19:02 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-15 18:59 [PATCH net-next v6 00/12] Begin upstreaming Homa transport protocol John Ousterhout
2025-01-15 18:59 ` [PATCH net-next v6 01/12] net: homa: define user-visible API for Homa John Ousterhout
2025-01-15 18:59 ` [PATCH net-next v6 02/12] net: homa: create homa_wire.h John Ousterhout
2025-01-15 18:59 ` [PATCH net-next v6 03/12] net: homa: create shared Homa header files John Ousterhout
2025-01-23 11:01 ` Paolo Abeni
2025-01-24 21:21 ` John Ousterhout
2025-01-27 9:05 ` Paolo Abeni
2025-01-27 17:04 ` John Ousterhout
2025-01-15 18:59 ` [PATCH net-next v6 04/12] net: homa: create homa_pool.h and homa_pool.c John Ousterhout
2025-01-23 12:06 ` Paolo Abeni
2025-01-24 23:53 ` John Ousterhout
2025-01-25 0:46 ` Andrew Lunn
2025-01-26 5:33 ` John Ousterhout
2025-01-27 9:41 ` Paolo Abeni
2025-01-27 17:34 ` John Ousterhout
2025-01-27 18:28 ` Paolo Abeni
2025-01-27 19:12 ` John Ousterhout
2025-01-28 8:27 ` Paolo Abeni
2025-01-15 18:59 ` [PATCH net-next v6 05/12] net: homa: create homa_rpc.h and homa_rpc.c John Ousterhout
2025-01-23 14:29 ` Paolo Abeni
2025-01-27 5:22 ` John Ousterhout
2025-01-27 10:01 ` Paolo Abeni
2025-01-27 18:03 ` John Ousterhout
2025-01-28 8:19 ` Paolo Abeni
2025-01-29 1:23 ` John Ousterhout
[not found] ` <13345e2a-849d-4bd8-a95e-9cd7f287c7df@redhat.com>
2025-01-29 16:43 ` John Ousterhout
2025-01-29 16:49 ` Eric Dumazet
2025-01-29 16:54 ` John Ousterhout
2025-01-29 17:04 ` Eric Dumazet
2025-01-29 20:27 ` John Ousterhout
2025-01-29 20:40 ` Eric Dumazet
2025-01-29 21:08 ` John Ousterhout
2025-01-15 18:59 ` [PATCH net-next v6 06/12] net: homa: create homa_peer.h and homa_peer.c John Ousterhout
2025-01-23 17:45 ` Paolo Abeni
2025-01-28 0:06 ` John Ousterhout
2025-01-28 0:32 ` Jason Xing
2025-01-15 18:59 ` [PATCH net-next v6 07/12] net: homa: create homa_sock.h and homa_sock.c John Ousterhout
2025-01-23 19:01 ` Paolo Abeni [this message]
2025-01-28 0:40 ` John Ousterhout
2025-01-28 4:26 ` John Ousterhout
2025-01-28 15:10 ` Eric Dumazet
2025-01-28 17:04 ` John Ousterhout
2025-01-24 7:33 ` Paolo Abeni
2025-01-15 18:59 ` [PATCH net-next v6 08/12] net: homa: create homa_incoming.c John Ousterhout
2025-01-24 8:31 ` Paolo Abeni
2025-01-30 0:41 ` John Ousterhout
[not found] ` <991b5ad9-57cf-4e1d-8e01-9d0639fa4e49@redhat.com>
2025-01-31 22:48 ` John Ousterhout
2025-02-03 9:12 ` Paolo Abeni
2025-02-03 23:33 ` John Ousterhout
2025-02-04 8:50 ` Paolo Abeni
2025-02-04 16:30 ` John Ousterhout
2025-02-04 19:41 ` Andrew Lunn
2025-02-04 21:20 ` John Ousterhout
2025-01-27 10:19 ` Paolo Abeni
2025-01-30 0:48 ` John Ousterhout
2025-01-30 9:57 ` Paolo Abeni
2025-01-31 22:51 ` John Ousterhout
[not found] ` <CAGXJAmxLqnjnWr8sjooJRRyQ2-5BqPCQL8gnn0gzYoZ0MMoBSw@mail.gmail.com>
2025-02-03 9:17 ` Paolo Abeni
2025-02-03 17:33 ` John Ousterhout
2025-02-03 17:58 ` Andrew Lunn
2025-02-05 23:56 ` John Ousterhout
2025-02-06 1:49 ` Andrew Lunn
2025-01-15 18:59 ` [PATCH net-next v6 09/12] net: homa: create homa_outgoing.c John Ousterhout
2025-01-15 18:59 ` [PATCH net-next v6 10/12] net: homa: create homa_timer.c John Ousterhout
2025-01-15 18:59 ` [PATCH net-next v6 11/12] net: homa: create homa_plumbing.c and homa_utils.c John Ousterhout
2025-01-15 18:59 ` [PATCH net-next v6 12/12] net: homa: create Makefile and Kconfig John Ousterhout
2025-01-24 8:55 ` [PATCH net-next v6 00/12] Begin upstreaming Homa transport protocol Paolo Abeni
2025-02-10 19:19 ` John Ousterhout
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=028f492f-41db-4c70-9527-cf0db03da4df@redhat.com \
--to=pabeni@redhat.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ouster@cs.stanford.edu \
/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).