All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Ahern <dsa@cumulusnetworks.com>
To: Hannes Frederic Sowa <hannes@stressinduktion.org>,
	"Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: Netdev <netdev@vger.kernel.org>,
	WireGuard mailing list <wireguard@lists.zx2c4.com>,
	LKML <linux-kernel@vger.kernel.org>,
	YOSHIFUJI Hideaki <hideaki.yoshifuji@miraclelinux.com>
Subject: Re: [PATCH v3] ip6_output: ensure flow saddr actually belongs to device
Date: Tue, 15 Nov 2016 08:26:42 -0700	[thread overview]
Message-ID: <4285324b-c396-dfc1-caad-c961a6564e94@cumulusnetworks.com> (raw)
In-Reply-To: <7543fa0f-a053-8387-1862-d78ffadba688@stressinduktion.org>

On 11/15/16 7:45 AM, Hannes Frederic Sowa wrote:

>> @@ -1012,6 +1013,16 @@ static int ip6_dst_lookup_tail(struct net *net,
>> const struct sock *sk,
>>          }
>>  #endif
>>
>> +        addr_type = ipv6_addr_type(&fl6->saddr);
>> +        if (addr_type == IPv6_ADDR_ANY)
>> +                return 0;
>> +
>> +        err = -EINVAL;
>> +        bind_to_dev = __ipv6_addr_src_scope(addr_type) <=
>> IPV6_ADDR_SCOPE_LINKLOCAL;
>> +        if (!ipv6_chk_addr(net, &fl6->saddr, bind_to_dev ?
>> (*dst)->dev : NULL, 0) &&
>> +            !ipv6_chk_acast_addr_src(net, (*dst)->dev, &fl6->saddr))
>> +                goto out_err_release;
>> +
>>          return 0;
>>
>>  out_err_release:
>>
> 
> We should not use (*dst)->dev, as this is the resulting device after the
> lookup and not necessarily corresponds to the device the user asked for.

To be consistent with IPv4 the saddr check is done before the lookup and dst and flow oif should not be used. Handling LL addresses are trickier and perhaps this is not the right place to enforce that check since it requires a specific device which is only really known after lookup. Why not add the if saddr is LL verification as part of the route selection? e.g, add something like rt6_device_match to ip6_pol_route (the device match call is only used for ip6_pol_route_lookup and not ip6_pol_route - why is that?).

WARNING: multiple messages have this Message-ID (diff)
From: David Ahern <dsa@cumulusnetworks.com>
To: Hannes Frederic Sowa <hannes@stressinduktion.org>,
	"Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: Netdev <netdev@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	WireGuard mailing list <wireguard@lists.zx2c4.com>,
	YOSHIFUJI Hideaki <hideaki.yoshifuji@miraclelinux.com>
Subject: Re: [PATCH v3] ip6_output: ensure flow saddr actually belongs to device
Date: Tue, 15 Nov 2016 08:26:42 -0700	[thread overview]
Message-ID: <4285324b-c396-dfc1-caad-c961a6564e94@cumulusnetworks.com> (raw)
In-Reply-To: <7543fa0f-a053-8387-1862-d78ffadba688@stressinduktion.org>

On 11/15/16 7:45 AM, Hannes Frederic Sowa wrote:

>> @@ -1012,6 +1013,16 @@ static int ip6_dst_lookup_tail(struct net *net,
>> const struct sock *sk,
>>          }
>>  #endif
>>
>> +        addr_type = ipv6_addr_type(&fl6->saddr);
>> +        if (addr_type == IPv6_ADDR_ANY)
>> +                return 0;
>> +
>> +        err = -EINVAL;
>> +        bind_to_dev = __ipv6_addr_src_scope(addr_type) <=
>> IPV6_ADDR_SCOPE_LINKLOCAL;
>> +        if (!ipv6_chk_addr(net, &fl6->saddr, bind_to_dev ?
>> (*dst)->dev : NULL, 0) &&
>> +            !ipv6_chk_acast_addr_src(net, (*dst)->dev, &fl6->saddr))
>> +                goto out_err_release;
>> +
>>          return 0;
>>
>>  out_err_release:
>>
> 
> We should not use (*dst)->dev, as this is the resulting device after the
> lookup and not necessarily corresponds to the device the user asked for.

To be consistent with IPv4 the saddr check is done before the lookup and dst and flow oif should not be used. Handling LL addresses are trickier and perhaps this is not the right place to enforce that check since it requires a specific device which is only really known after lookup. Why not add the if saddr is LL verification as part of the route selection? e.g, add something like rt6_device_match to ip6_pol_route (the device match call is only used for ip6_pol_route_lookup and not ip6_pol_route - why is that?).

WARNING: multiple messages have this Message-ID (diff)
From: David Ahern <dsa@cumulusnetworks.com>
To: Hannes Frederic Sowa <hannes@stressinduktion.org>,
	"Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: Netdev <netdev@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	WireGuard mailing list <wireguard@lists.zx2c4.com>,
	YOSHIFUJI Hideaki <hideaki.yoshifuji@miraclelinux.com>
Subject: Re: [WireGuard] [PATCH v3] ip6_output: ensure flow saddr actually belongs to device
Date: Tue, 15 Nov 2016 08:26:42 -0700	[thread overview]
Message-ID: <4285324b-c396-dfc1-caad-c961a6564e94@cumulusnetworks.com> (raw)
In-Reply-To: <7543fa0f-a053-8387-1862-d78ffadba688@stressinduktion.org>

On 11/15/16 7:45 AM, Hannes Frederic Sowa wrote:

>> @@ -1012,6 +1013,16 @@ static int ip6_dst_lookup_tail(struct net *net,
>> const struct sock *sk,
>>          }
>>  #endif
>>
>> +        addr_type = ipv6_addr_type(&fl6->saddr);
>> +        if (addr_type == IPv6_ADDR_ANY)
>> +                return 0;
>> +
>> +        err = -EINVAL;
>> +        bind_to_dev = __ipv6_addr_src_scope(addr_type) <=
>> IPV6_ADDR_SCOPE_LINKLOCAL;
>> +        if (!ipv6_chk_addr(net, &fl6->saddr, bind_to_dev ?
>> (*dst)->dev : NULL, 0) &&
>> +            !ipv6_chk_acast_addr_src(net, (*dst)->dev, &fl6->saddr))
>> +                goto out_err_release;
>> +
>>          return 0;
>>
>>  out_err_release:
>>
> 
> We should not use (*dst)->dev, as this is the resulting device after the
> lookup and not necessarily corresponds to the device the user asked for.

To be consistent with IPv4 the saddr check is done before the lookup and dst and flow oif should not be used. Handling LL addresses are trickier and perhaps this is not the right place to enforce that check since it requires a specific device which is only really known after lookup. Why not add the if saddr is LL verification as part of the route selection? e.g, add something like rt6_device_match to ip6_pol_route (the device match call is only used for ip6_pol_route_lookup and not ip6_pol_route - why is that?).

  reply	other threads:[~2016-11-15 15:26 UTC|newest]

Thread overview: 78+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-11 19:29 Source address fib invalidation on IPv6 Jason A. Donenfeld
2016-11-11 19:29 ` [WireGuard] " Jason A. Donenfeld
2016-11-11 19:29 ` Jason A. Donenfeld
2016-11-11 22:14 ` David Ahern
2016-11-11 22:14   ` [WireGuard] " David Ahern
2016-11-11 22:14   ` David Ahern
2016-11-12  2:18   ` Jason A. Donenfeld
2016-11-12  2:18     ` [WireGuard] " Jason A. Donenfeld
2016-11-12  2:18     ` Jason A. Donenfeld
2016-11-12 15:40     ` Jason A. Donenfeld
2016-11-12 15:40       ` [WireGuard] " Jason A. Donenfeld
2016-11-12 15:40       ` Jason A. Donenfeld
2016-11-12 18:14       ` David Ahern
2016-11-12 18:14         ` [WireGuard] " David Ahern
2016-11-12 18:14         ` David Ahern
2016-11-12 19:08         ` Jason A. Donenfeld
2016-11-12 19:08           ` [WireGuard] " Jason A. Donenfeld
2016-11-12 19:08           ` Jason A. Donenfeld
2016-11-13  0:43           ` Jason A. Donenfeld
2016-11-13  0:43             ` [WireGuard] " Jason A. Donenfeld
2016-11-13  0:51             ` Hannes Frederic Sowa
2016-11-13  0:51               ` [WireGuard] " Hannes Frederic Sowa
2016-11-13  0:51               ` Hannes Frederic Sowa
2016-11-13  1:00               ` Jason A. Donenfeld
2016-11-13  1:00                 ` [WireGuard] " Jason A. Donenfeld
2016-11-13  1:00                 ` Jason A. Donenfeld
2016-11-13 13:23                 ` [PATCH] ip6_output: ensure flow saddr actually belongs to device Jason A. Donenfeld
2016-11-13 13:23                   ` [WireGuard] " Jason A. Donenfeld
2016-11-13 13:23                   ` Jason A. Donenfeld
2016-11-13 16:30                   ` David Ahern
2016-11-13 16:30                     ` [WireGuard] " David Ahern
2016-11-13 19:02                     ` [PATCH v2] " Jason A. Donenfeld
2016-11-13 19:02                       ` [WireGuard] " Jason A. Donenfeld
2016-11-13 19:02                       ` Jason A. Donenfeld
2016-11-13 20:45                       ` David Ahern
2016-11-13 20:45                         ` [WireGuard] " David Ahern
2016-11-13 23:28                         ` [PATCH v3] " Jason A. Donenfeld
2016-11-13 23:28                           ` [WireGuard] " Jason A. Donenfeld
2016-11-13 23:28                           ` Jason A. Donenfeld
2016-11-14  1:36                           ` [WireGuard] Debugging AllowedIps John Huttley
2016-11-14  1:39                             ` Jason A. Donenfeld
2016-11-14  2:28                               ` John Huttley
2016-11-14  2:59                                 ` Jason A. Donenfeld
2016-11-14  3:10                                   ` John Huttley
2016-11-14 16:19                           ` [PATCH v3] ip6_output: ensure flow saddr actually belongs to device David Ahern
2016-11-14 16:19                             ` [WireGuard] " David Ahern
     [not found]                             ` <CAHmME9p6-mLSs84AwwfRXe8U3Z2sy6Dp9W9H0gKh0rcZuQAfZA@mail.gmail.com>
     [not found]                               ` <CAHmME9qC4xqGOwJnauXrJBDkAtmmuJ+kJKL6ufuU9_XWKNFdSA@mail.gmail.com>
2016-11-14 16:54                                 ` Jason A. Donenfeld
2016-11-14 16:54                                   ` [WireGuard] " Jason A. Donenfeld
2016-11-14 16:44                           ` Hannes Frederic Sowa
2016-11-14 16:44                             ` [WireGuard] " Hannes Frederic Sowa
2016-11-14 16:55                             ` David Ahern
2016-11-14 16:55                               ` [WireGuard] " David Ahern
2016-11-14 17:04                               ` Hannes Frederic Sowa
2016-11-14 17:04                                 ` [WireGuard] " Hannes Frederic Sowa
2016-11-14 17:17                                 ` David Ahern
2016-11-14 17:17                                   ` [WireGuard] " David Ahern
2016-11-14 17:33                                   ` Hannes Frederic Sowa
2016-11-14 17:33                                     ` [WireGuard] " Hannes Frederic Sowa
2016-11-14 17:48                                     ` David Ahern
2016-11-14 17:48                                       ` [WireGuard] " David Ahern
2016-11-14 18:33                                       ` Hannes Frederic Sowa
2016-11-14 18:33                                         ` [WireGuard] " Hannes Frederic Sowa
2016-11-15  0:45                                         ` Jason A. Donenfeld
2016-11-15  0:45                                           ` [WireGuard] " Jason A. Donenfeld
2016-11-15  0:45                                           ` Jason A. Donenfeld
2016-11-15 14:45                                           ` Hannes Frederic Sowa
2016-11-15 14:45                                             ` [WireGuard] " Hannes Frederic Sowa
2016-11-15 15:26                                             ` David Ahern [this message]
2016-11-15 15:26                                               ` David Ahern
2016-11-15 15:26                                               ` David Ahern
2016-11-13 20:19                     ` [PATCH] " Jason A. Donenfeld
2016-11-13 20:19                       ` [WireGuard] " Jason A. Donenfeld
2016-11-13 20:39                       ` David Ahern
2016-11-13 20:39                         ` [WireGuard] " David Ahern
2016-11-13 20:39                         ` David Ahern
2016-11-13  0:51             ` Source address fib invalidation on IPv6 Jason A. Donenfeld
2016-11-13  0:51               ` [WireGuard] " Jason A. Donenfeld
2016-11-13  0:51               ` Jason A. Donenfeld

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=4285324b-c396-dfc1-caad-c961a6564e94@cumulusnetworks.com \
    --to=dsa@cumulusnetworks.com \
    --cc=Jason@zx2c4.com \
    --cc=hannes@stressinduktion.org \
    --cc=hideaki.yoshifuji@miraclelinux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=wireguard@lists.zx2c4.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.