All of lore.kernel.org
 help / color / mirror / Atom feed
From: Xin Long <lucien.xin@gmail.com>
To: network dev <netdev@vger.kernel.org>, linux-sctp@vger.kernel.org
Cc: davem@davemloft.net, kuba@kernel.org,
	Eric Dumazet <edumazet@google.com>,
	Paolo Abeni <pabeni@redhat.com>,
	Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>,
	Neil Horman <nhorman@tuxdriver.com>,
	David Ahern <dsahern@gmail.com>,
	Carlo Carraro <colrack@gmail.com>
Subject: [PATCH net-next 3/7] sctp: check sk_bound_dev_if when matching ep in get_port
Date: Sun, 13 Nov 2022 11:44:39 -0500	[thread overview]
Message-ID: <87135839695e35749206f2af03a53a9e03f184a3.1668357542.git.lucien.xin@gmail.com> (raw)
In-Reply-To: <cover.1668357542.git.lucien.xin@gmail.com>

In sctp_get_port_local(), when binding to IP and PORT, it should
also check sk_bound_dev_if to match listening sk if it's set by
SO_BINDTOIFINDEX, so that multiple sockets with the same IP and
PORT, but different sk_bound_dev_if can be listened at the same
time.

Signed-off-by: Xin Long <lucien.xin@gmail.com>
---
 net/sctp/socket.c | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/net/sctp/socket.c b/net/sctp/socket.c
index 3e83963d1b8a..4306164238ef 100644
--- a/net/sctp/socket.c
+++ b/net/sctp/socket.c
@@ -8398,6 +8398,7 @@ static int sctp_get_port_local(struct sock *sk, union sctp_addr *addr)
 		 * in an endpoint.
 		 */
 		sk_for_each_bound(sk2, &pp->owner) {
+			int bound_dev_if2 = READ_ONCE(sk2->sk_bound_dev_if);
 			struct sctp_sock *sp2 = sctp_sk(sk2);
 			struct sctp_endpoint *ep2 = sp2->ep;
 
@@ -8408,7 +8409,9 @@ static int sctp_get_port_local(struct sock *sk, union sctp_addr *addr)
 			     uid_eq(uid, sock_i_uid(sk2))))
 				continue;
 
-			if (sctp_bind_addr_conflict(&ep2->base.bind_addr,
+			if ((!sk->sk_bound_dev_if || !bound_dev_if2 ||
+			     sk->sk_bound_dev_if == bound_dev_if2) &&
+			    sctp_bind_addr_conflict(&ep2->base.bind_addr,
 						    addr, sp2, sp)) {
 				ret = 1;
 				goto fail_unlock;
-- 
2.31.1


  parent reply	other threads:[~2022-11-13 16:44 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-13 16:44 [PATCH net-next 0/7] sctp: support vrf processing Xin Long
2022-11-13 16:44 ` [PATCH net-next 1/7] sctp: verify the bind address with the tb_id from l3mdev Xin Long
2022-11-13 16:44 ` [PATCH net-next 2/7] sctp: check ipv6 addr with sk_bound_dev if set Xin Long
2022-11-13 16:44 ` Xin Long [this message]
2022-11-13 16:44 ` [PATCH net-next 4/7] sctp: add skb_sdif in struct sctp_af Xin Long
2022-11-13 16:44 ` [PATCH net-next 5/7] sctp: add dif and sdif check in asoc and ep lookup Xin Long
2022-11-13 20:14   ` kernel test robot
2022-11-15  2:38     ` Xin Long
2022-11-15 10:19       ` Paolo Abeni
2022-11-15 15:25         ` Xin Long
2022-11-13 16:44 ` [PATCH net-next 6/7] sctp: add sysctl net.sctp.l3mdev_accept Xin Long
2022-11-13 16:44 ` [PATCH net-next 7/7] selftests: add a selftest for sctp vrf Xin Long
2022-11-15 10:29   ` Paolo Abeni
2022-11-15 15:33     ` Xin Long
2022-11-15 18:07       ` Xin Long
2022-11-15 20:40       ` Paolo Abeni

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=87135839695e35749206f2af03a53a9e03f184a3.1668357542.git.lucien.xin@gmail.com \
    --to=lucien.xin@gmail.com \
    --cc=colrack@gmail.com \
    --cc=davem@davemloft.net \
    --cc=dsahern@gmail.com \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-sctp@vger.kernel.org \
    --cc=marcelo.leitner@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=nhorman@tuxdriver.com \
    --cc=pabeni@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.