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: Fri, 24 Jan 2025 08:33:57 +0100 [thread overview]
Message-ID: <afad8fa2-344f-4253-b929-a888b99e90a9@redhat.com> (raw)
In-Reply-To: <20250115185937.1324-8-ouster@cs.stanford.edu>
On 1/15/25 7:59 PM, John Ousterhout wrote:
> +/**
> + * 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);
> + atomic_set(&hsk->protect_count, 0);
> + spin_lock_init(&hsk->lock);
> + hsk->last_locker = "none";
> + atomic_set(&hsk->protect_count, 0);
> + hsk->homa = homa;
> + hsk->ip_header_length = (hsk->inet.sk.sk_family == AF_INET)
> + ? HOMA_IPV4_HEADER_LENGTH : HOMA_IPV6_HEADER_LENGTH;
> + hsk->shutdown = false;
> + starting_port = homa->prev_default_port;
> + while (1) {
> + homa->prev_default_port++;
> + if (homa->prev_default_port < HOMA_MIN_DEFAULT_PORT)
> + homa->prev_default_port = HOMA_MIN_DEFAULT_PORT;
> + if (!homa_sock_find(socktab, homa->prev_default_port))
> + break;
> + if (homa->prev_default_port == starting_port) {
> + spin_unlock_bh(&socktab->write_lock);
> + hsk->shutdown = true;
> + return -EADDRNOTAVAIL;
> + }
> + }
> + hsk->port = homa->prev_default_port;
> + hsk->inet.inet_num = hsk->port;
> + hsk->inet.inet_sport = htons(hsk->port);
> + hsk->socktab_links.sock = hsk;
> + hlist_add_head_rcu(&hsk->socktab_links.hash_links,
> + &socktab->buckets[homa_port_hash(hsk->port)]);
At this point the socket is apparently exposed to lookup from incoming
packets, but it's only partially initialized: bad things could happen.
> +/**
> + * homa_sock_find() - Returns the socket associated with a given port.
> + * @socktab: Hash table in which to perform lookup.
> + * @port: The port of interest.
> + * Return: The socket that owns @port, or NULL if none.
> + *
> + * Note: this function uses RCU list-searching facilities, but it doesn't
> + * call rcu_read_lock. The caller should do that, if the caller cares (this
> + * way, the caller's use of the socket will also be protected).
> + */
> +struct homa_sock *homa_sock_find(struct homa_socktab *socktab, __u16 port)
It would help the review if you reorder the code defining first the
basic helpers like this one and after the functions using them
> +{
> + struct homa_socktab_links *link;
> + struct homa_sock *result = NULL;
> +
> + hlist_for_each_entry_rcu(link, &socktab->buckets[homa_port_hash(port)],
> + hash_links) {
This require the caller owing the rcu read lock, which is not always the
case in this patchset.
> + struct homa_sock *hsk = link->sock;
> +
> + if (hsk->port == port) {
> + result = hsk;
The local port is the full key of the socket lookup? not even the
address? This simplify the code a bit, but is quite against user
expectation.
/P
next prev parent reply other threads:[~2025-01-24 7:34 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
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 [this message]
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=afad8fa2-344f-4253-b929-a888b99e90a9@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).