Re: [PATCH v2 net-next 0/5] Add bpf support to set sk_bound_dev_if

2016-10-31 Thread Thomas Graf
On 10/31/16 at 11:16am, David Ahern wrote: > On 10/31/16 11:01 AM, David Miller wrote: > > Also, any reason why you don't allow the cgroup bpf sk filter to return > > an error code so that the sock creation could be cancelled if the eBPF > > program desires that? It could be useful, I suppose. >

Re: [PATCH v2 net-next 0/5] Add bpf support to set sk_bound_dev_if

2016-10-31 Thread David Ahern
On 10/31/16 11:01 AM, David Miller wrote: > From: David Ahern > Date: Wed, 26 Oct 2016 17:58:37 -0700 > >> The recently added VRF support in Linux leverages the bind-to-device >> API for programs to specify an L3 domain for a socket. While >> SO_BINDTODEVICE has been around for ages, not every ip

Re: [PATCH v2 net-next 0/5] Add bpf support to set sk_bound_dev_if

2016-10-31 Thread David Miller
From: David Ahern Date: Wed, 26 Oct 2016 17:58:37 -0700 > The recently added VRF support in Linux leverages the bind-to-device > API for programs to specify an L3 domain for a socket. While > SO_BINDTODEVICE has been around for ages, not every ipv4/ipv6 capable > program has support for it. Even

[PATCH v2 net-next 0/5] Add bpf support to set sk_bound_dev_if

2016-10-26 Thread David Ahern
The recently added VRF support in Linux leverages the bind-to-device API for programs to specify an L3 domain for a socket. While SO_BINDTODEVICE has been around for ages, not every ipv4/ipv6 capable program has support for it. Even for those programs that do support it, the API requires processes