From: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
To: Neil Horman <nhorman@tuxdriver.com>
Cc: Xin Long <lucien.xin@gmail.com>,
network dev <netdev@vger.kernel.org>,
linux-sctp@vger.kernel.org, davem@davemloft.net
Subject: Re: [PATCH net] sctp: do not check port in sctp_inet6_cmp_addr
Date: Wed, 11 Apr 2018 11:59:10 -0300 [thread overview]
Message-ID: <20180411145910.GC3711@localhost.localdomain> (raw)
In-Reply-To: <20180411143607.GA4141@hmswarspite.think-freely.org>
On Wed, Apr 11, 2018 at 10:36:07AM -0400, Neil Horman wrote:
> On Wed, Apr 11, 2018 at 08:58:05PM +0800, Xin Long wrote:
> > pf->cmp_addr() is called before binding a v6 address to the sock. It
> > should not check ports, like in sctp_inet_cmp_addr.
> >
> > But sctp_inet6_cmp_addr checks the addr by invoking af(6)->cmp_addr,
> > sctp_v6_cmp_addr where it also compares the ports.
> >
> > This would cause that setsockopt(SCTP_SOCKOPT_BINDX_ADD) could bind
> > multiple duplicated IPv6 addresses after Commit 40b4f0fd74e4 ("sctp:
> > lack the check for ports in sctp_v6_cmp_addr").
> >
> > This patch is to remove af->cmp_addr called in sctp_inet6_cmp_addr,
> > but do the proper check for both v6 addrs and v4mapped addrs.
> >
> > Fixes: 40b4f0fd74e4 ("sctp: lack the check for ports in sctp_v6_cmp_addr")
> > Reported-by: Jianwen Ji <jiji@redhat.com>
> > Signed-off-by: Xin Long <lucien.xin@gmail.com>
> > ---
> > net/sctp/ipv6.c | 27 ++++++++++++++++++++++++---
> > 1 file changed, 24 insertions(+), 3 deletions(-)
> >
> > diff --git a/net/sctp/ipv6.c b/net/sctp/ipv6.c
> > index f1fc48e..be4b72c 100644
> > --- a/net/sctp/ipv6.c
> > +++ b/net/sctp/ipv6.c
> > @@ -846,8 +846,8 @@ static int sctp_inet6_cmp_addr(const union sctp_addr *addr1,
> > const union sctp_addr *addr2,
> > struct sctp_sock *opt)
> > {
> > - struct sctp_af *af1, *af2;
> > struct sock *sk = sctp_opt2sk(opt);
> > + struct sctp_af *af1, *af2;
> >
> > af1 = sctp_get_af_specific(addr1->sa.sa_family);
> > af2 = sctp_get_af_specific(addr2->sa.sa_family);
> > @@ -863,10 +863,31 @@ static int sctp_inet6_cmp_addr(const union sctp_addr *addr1,
> > if (sctp_is_any(sk, addr1) || sctp_is_any(sk, addr2))
> > return 1;
> >
> > - if (addr1->sa.sa_family != addr2->sa.sa_family)
> > + if (addr1->sa.sa_family != addr2->sa.sa_family) {
> > + if (addr1->sa.sa_family == AF_INET &&
> > + addr2->sa.sa_family == AF_INET6 &&
> > + ipv6_addr_v4mapped(&addr2->v6.sin6_addr))
> > + if (addr2->v6.sin6_addr.s6_addr32[3] ==
> > + addr1->v4.sin_addr.s_addr)
> > + return 1;
> > + if (addr2->sa.sa_family == AF_INET &&
> > + addr1->sa.sa_family == AF_INET6 &&
> > + ipv6_addr_v4mapped(&addr1->v6.sin6_addr))
> > + if (addr1->v6.sin6_addr.s6_addr32[3] ==
> > + addr2->v4.sin_addr.s_addr)
> > + return 1;
> > + return 0;
> > + }
> > +
> > + if (!ipv6_addr_equal(&addr1->v6.sin6_addr, &addr2->v6.sin6_addr))
> > + return 0;
> > +
> > + if ((ipv6_addr_type(&addr1->v6.sin6_addr) & IPV6_ADDR_LINKLOCAL) &&
> > + addr1->v6.sin6_scope_id && addr2->v6.sin6_scope_id &&
> > + addr1->v6.sin6_scope_id != addr2->v6.sin6_scope_id)
> > return 0;
> >
> > - return af1->cmp_addr(addr1, addr2);
> > + return 1;
> > }
> >
> > /* Verify that the provided sockaddr looks bindable. Common verification,
> > --
> > 2.1.0
> >
> This looks correct to me, but is it worth duplicating the comparison code like
> this from the cmp_addr function? It might be more worthwhile to add a flag to
> the cmp_addr method to direct weather it needs to check port values or not.
> That way you could continue to use the cmp_addr function here.
Adding a flag into sctp_v6_cmp_addr will get us a terrible code to
read. It's already not one of the best looking part of it. Maybe
still duplicate part of it it, but at 'af' level? As in:
- af->cmp_addr
- af->cmp_addr_port
Marcelo
next prev parent reply other threads:[~2018-04-11 14:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-11 12:58 [PATCH net] sctp: do not check port in sctp_inet6_cmp_addr Xin Long
2018-04-11 14:36 ` Neil Horman
2018-04-11 14:59 ` Marcelo Ricardo Leitner [this message]
2018-04-11 16:16 ` Xin Long
2018-04-11 16:40 ` David Miller
2018-04-11 19:59 ` Neil Horman
2018-04-11 14:42 ` Marcelo Ricardo Leitner
2018-04-11 14:51 ` Marcelo Ricardo Leitner
2018-04-11 14:51 ` David Miller
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=20180411145910.GC3711@localhost.localdomain \
--to=marcelo.leitner@gmail.com \
--cc=davem@davemloft.net \
--cc=linux-sctp@vger.kernel.org \
--cc=lucien.xin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.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).