From: Vlad Yasevich <vladislav.yasevich@hp.com>
To: Dave Johnson <djohnson+linux-kernel@sw.starentnetworks.com>
Cc: lksctp-developers@lists.sourceforge.net,
linux-kernel@vger.kernel.org,
Srinivas Akkipeddi <sakkiped@starentnetworks.com>
Subject: Re: [PATCH] SCTP: IPv4 mapped addr not returned in SCTPv6 accept()
Date: Thu, 26 Jul 2007 13:55:51 -0400 [thread overview]
Message-ID: <46A8E027.10802@hp.com> (raw)
In-Reply-To: <18087.57737.908842.337891@zeus.sw.starentnetworks.com>
Dave Johnson wrote:
> An accept() call on a SCTPv6 socket that returns due to connection of
> a IPv4 mapped peer will fill out the 'struct sockaddr' with a zero
> IPv6 address instead of the IPv4 mapped address of the peer.
>
> This is due to the v4mapped flag not getting copied into the new
> socket on accept() as well as a missing check for INET6 socket type in
> sctp_v4_to_sk_*addr().
>
> Signed-off-by: Dave Johnson <djohnson+linux-kernel@sw.starentnetworks.com>
> Cc: Srinivas Akkipeddi <sakkiped@starentnetworks.com>
>
> ===== net/sctp/ipv6.c 1.108 vs edited =====
> --- 1.108/net/sctp/ipv6.c 2007-07-05 20:40:15 -04:00
> +++ edited/net/sctp/ipv6.c 2007-07-25 16:30:41 -04:00
> @@ -641,6 +641,8 @@
> newsctp6sk = (struct sctp6_sock *)newsk;
> inet_sk(newsk)->pinet6 = &newsctp6sk->inet6;
>
> + sctp_sk(newsk)->v4mapped = sctp_sk(sk)->v4mapped;
> +
> newinet = inet_sk(newsk);
> newnp = inet6_sk(newsk);
>
> ===== net/sctp/protocol.c 1.130 vs edited =====
> --- 1.130/net/sctp/protocol.c 2007-05-04 16:36:30 -04:00
> +++ edited/net/sctp/protocol.c 2007-07-25 16:28:21 -04:00
> @@ -257,13 +257,28 @@
> /* Initialize sk->sk_rcv_saddr from sctp_addr. */
> static void sctp_v4_to_sk_saddr(union sctp_addr *addr, struct sock *sk)
> {
> - inet_sk(sk)->rcv_saddr = addr->v4.sin_addr.s_addr;
> + if ((sk->sk_family == PF_INET6) && (sctp_sk(sk)->v4mapped)) {
> + inet6_sk(sk)->rcv_saddr.s6_addr32[0] = 0;
> + inet6_sk(sk)->rcv_saddr.s6_addr32[1] = 0;
> + inet6_sk(sk)->rcv_saddr.s6_addr32[2] = htonl(0x0000ffff);
> + inet6_sk(sk)->rcv_saddr.s6_addr32[3] =
> + addr->v4.sin_addr.s_addr;
> + } else {
> + inet_sk(sk)->rcv_saddr = addr->v4.sin_addr.s_addr;
> + }
> }
>
> /* Initialize sk->sk_daddr from sctp_addr. */
> static void sctp_v4_to_sk_daddr(union sctp_addr *addr, struct sock *sk)
> {
> - inet_sk(sk)->daddr = addr->v4.sin_addr.s_addr;
> + if ((sk->sk_family == PF_INET6) && (sctp_sk(sk)->v4mapped)) {
> + inet6_sk(sk)->daddr.s6_addr32[0] = 0;
> + inet6_sk(sk)->daddr.s6_addr32[1] = 0;
> + inet6_sk(sk)->daddr.s6_addr32[2] = htonl(0x0000ffff);
> + inet6_sk(sk)->daddr.s6_addr32[3] = addr->v4.sin_addr.s_addr;
> + } else {
> + inet_sk(sk)->daddr = addr->v4.sin_addr.s_addr;
> + }
> }
>
> /* Initialize a sctp_addr from an address parameter. */
> @@ -557,6 +572,8 @@
> newsk->sk_protocol = IPPROTO_SCTP;
> newsk->sk_backlog_rcv = sk->sk_prot->backlog_rcv;
> sock_reset_flag(newsk, SOCK_ZAPPED);
> +
> + sctp_sk(newsk)->v4mapped = sctp_sk(sk)->v4mapped;
>
> newinet = inet_sk(newsk);
>
>
Can you explain why the sctp_v4 changes are need for the this case?
I don't see how the code in sctp/protocol.c comes into play for this
particular bug.
Thanks
-vlad
next prev parent reply other threads:[~2007-07-26 17:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-25 23:49 [PATCH] SCTP: IPv4 mapped addr not returned in SCTPv6 accept() Dave Johnson
2007-07-26 17:55 ` Vlad Yasevich [this message]
2007-07-26 19:00 ` Dave Johnson
2007-07-26 19:42 ` Vlad Yasevich
2007-07-26 20:44 ` Dave Johnson
2007-07-26 20:49 ` Vlad Yasevich
2007-07-31 0:23 ` David Miller
2007-07-31 13:53 ` Vlad Yasevich
2007-08-06 20:48 ` [PATCH] SCTP: fix IPv4 addr in SCTPv6 accept()/getpeername() Dave Johnson
2007-08-06 20:48 ` [PATCH] SCTP: IPv4 mapped addr not returned in SCTPv6 accept() Dave Johnson
2007-08-06 20:55 ` Vlad Yasevich
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=46A8E027.10802@hp.com \
--to=vladislav.yasevich@hp.com \
--cc=djohnson+linux-kernel@sw.starentnetworks.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lksctp-developers@lists.sourceforge.net \
--cc=sakkiped@starentnetworks.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.