From: Eric Dumazet <eric.dumazet@gmail.com>
To: Hoang Le <hoang.h.le@dektech.com.au>,
jon.maloy@ericsson.com, maloy@donjonn.com,
tipc-discussion@lists.sourceforge.net, netdev@vger.kernel.org
Subject: Re: [net-next] tipc: improve throughput between nodes in netns
Date: Mon, 21 Oct 2019 19:40:47 -0700 [thread overview]
Message-ID: <88e00511-ae7f-cbd3-46b1-df0f0509c04e@gmail.com> (raw)
In-Reply-To: <20191022022036.19961-1-hoang.h.le@dektech.com.au>
On 10/21/19 7:20 PM, Hoang Le wrote:
> n->net = net;
> n->capabilities = capabilities;
> + n->pnet = NULL;
> + for_each_net_rcu(tmp) {
This does not scale well, if say you have a thousand netns ?
> + tn_peer = net_generic(tmp, tipc_net_id);
> + if (!tn_peer)
> + continue;
> + /* Integrity checking whether node exists in namespace or not */
> + if (tn_peer->net_id != tn->net_id)
> + continue;
> + if (memcmp(peer_id, tn_peer->node_id, NODE_ID_LEN))
> + continue;
> +
> + hash_chk = tn_peer->random;
> + hash_chk ^= net_hash_mix(&init_net);
Why the xor with net_hash_mix(&init_net) is needed ?
> + hash_chk ^= net_hash_mix(tmp);
> + if (hash_chk ^ hash_mixes)
> + continue;
> + n->pnet = tmp;
> + break;
> + }
How can we set n->pnet without increasing netns ->count ?
Using check_net() later might trigger an use-after-free.
next prev parent reply other threads:[~2019-10-22 2:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-22 2:20 [net-next] tipc: improve throughput between nodes in netns Hoang Le
2019-10-22 2:40 ` Eric Dumazet [this message]
2019-10-22 3:33 ` Hoang Le
2019-10-22 3:57 ` Eric Dumazet
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=88e00511-ae7f-cbd3-46b1-df0f0509c04e@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=hoang.h.le@dektech.com.au \
--cc=jon.maloy@ericsson.com \
--cc=maloy@donjonn.com \
--cc=netdev@vger.kernel.org \
--cc=tipc-discussion@lists.sourceforge.net \
/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