netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vlad Yasevich <vladislav.yasevich@hp.com>
To: Paolo Galtieri <pgaltieri@mvista.com>
Cc: netdev@vger.kernel.org, sri@us.ibm.com
Subject: Re: Bug in SCTP with SCTP_BINDX_REM_ADDR
Date: Thu, 05 Apr 2007 13:07:18 -0600	[thread overview]
Message-ID: <461548E6.4030008@hp.com> (raw)
In-Reply-To: <4614FAE6.3070409@mvista.com>

Hi Paolo

Paolo Galtieri wrote:
> What is happening is that the check for IPV6_ADDR_MAPPED that occurs
> during the add is missing when you do the remove and hence the IPv6
> address is never mapped to the IPv4 address causing the lookup to
> fail.  Below is the patch to add the necessary checks to do the
> mapping.  This patch is against 2.6.21-rc5
> 
> Does this make sense?  Any comments are appreciated.
>

Yes, it makes perfect sense; however, I think you can just use
af->addr_valid() instead of adding a special case below.

If that works, can you regenerate the patch and provide a
Signed-off-by line so I can incorporate that.

Thanks
-vlad

> Thank you,
> Paolo
> 
> I've attached the test program - compile as gcc -o bindx-test-ipv6 
> bindx-test-ipv6.c -lsctp
> ================================ >8 
> ==========================================
> --- net/sctp/socket.c.orig      2007-04-04 13:22:59.000000000 -0700
> +++ net/sctp/socket.c   2007-04-04 13:25:35.000000000 -0700
> @@ -627,6 +627,27 @@ int sctp_bindx_rem(struct sock *sk, stru
>                        retval = -EINVAL;
>                        goto err_bindx_rem;
>                }
> +               /*
> +                * It's possible that we mapped an IPV6 addr to an IPV4 
> addr
> +                * during the sctp_bindx_add() operation.  This will 
> happen if
> +                * the IPV6 address we assigned to an interface is a mapped
> +                * address, e.g. ::ffff:192.0.2.128.  If we have mapped 
> an IPV6
> +                * address to an IPV4 address during the add we need to 
> make
> +                * sure we do the same thing during the remove, 
> otherwise we
> +                * wont find a match on the address_list.
> +                */
> +
> +               if (af->sa_family == AF_INET6) {
> +                       struct in6_addr *in6;
> +                       int type;
> +
> +                       in6 = (struct in6_addr *)&sa_addr->v6.sin6_addr;
> +                       type = ipv6_addr_type(in6);
> +
> +                       if (type == IPV6_ADDR_MAPPED)
> +                               sctp_v6_map_v4(sa_addr);
> +               }
> +
>                if (sa_addr->v4.sin_port != htons(bp->port)) {
>                        retval = -EINVAL;
>                        goto err_bindx_rem;
> 
> 


  reply	other threads:[~2007-04-05 19:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-05 13:34 Bug in SCTP with SCTP_BINDX_REM_ADDR Paolo Galtieri
2007-04-05 19:07 ` Vlad Yasevich [this message]
2007-04-05 20:25   ` Paolo Galtieri
2007-04-05 21:08     ` Paolo Galtieri

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=461548E6.4030008@hp.com \
    --to=vladislav.yasevich@hp.com \
    --cc=netdev@vger.kernel.org \
    --cc=pgaltieri@mvista.com \
    --cc=sri@us.ibm.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).