On Wed, May 29, 2019 at 9:04 PM David Ahern wrote:
>
> From: David Ahern
>
> Add rtnl_nexthopdump_req to initiate a dump request of nexthop objects.
>
> Signed-off-by: David Ahern
> ---
> include/libnetlink.h | 4
> lib/libnetlink.c | 27 +++
> 2 files changed,
On Wed, May 29, 2019 at 9:04 PM David Ahern wrote:
>
> From: David Ahern
>
> Add nhid option for routes to use nexthop objects by id.
>
> Signed-off-by: David Ahern
> ---
man page needs an update ? :)
> ip/iproute.c | 14 --
> 1 file changed, 12 insertions(+), 2 deletions(-)
>
>
On Wed, May 29, 2019 at 9:04 PM David Ahern wrote:
>
> From: David Ahern
>
> Add nexthop subcommand to ip. Implement basic commands for creating,
> deleting and dumping nexthop objects. Syntax follows 'nexthop' syntax
> from existing 'ip route' command.
>
> Signed-off-by: David Ahern
If you are
On Fri, Jul 19, 2019 at 4:00 AM Jiri Pirko wrote:
>
> From: Jiri Pirko
>
> Add two commands to add and delete alternative ifnames for net device.
> Each net device can have multiple alternative names.
>
> Signed-off-by: Jiri Pirko
> ---
> include/linux/netdevice.h | 4 ++
> include/uapi/
On Thu, Aug 8, 2019 at 11:25 PM Jiri Pirko wrote:
>
> Fri, Aug 09, 2019 at 06:11:30AM CEST, ro...@cumulusnetworks.com wrote:
> >On Fri, Jul 19, 2019 at 4:00 AM Jiri Pirko wrote:
> >>
> >> From: Jiri Pirko
> >>
> >> Add two commands to add and delete alternative ifnames for net device.
> >> Each
On Fri, Aug 9, 2019 at 8:46 AM Michal Kubecek wrote:
>
> On Fri, Aug 09, 2019 at 08:40:25AM -0700, Roopa Prabhu wrote:
> > to that point, I am also not sure why we have a new API For multiple
> > names. I mean why support more than two names (existing old name and
> >
On Sat, Aug 10, 2019 at 8:50 AM Michal Kubecek wrote:
>
> On Sat, Aug 10, 2019 at 06:46:57AM -0700, Roopa Prabhu wrote:
> > On Fri, Aug 9, 2019 at 8:46 AM Michal Kubecek wrote:
> > >
> > > On Fri, Aug 09, 2019 at 08:40:25AM -0700, Roopa Prabhu wrote:
> > >
On Mon, Aug 12, 2019 at 1:31 AM Jiri Pirko wrote:
>
> Mon, Aug 12, 2019 at 03:37:26AM CEST, dsah...@gmail.com wrote:
> >On 8/11/19 7:34 PM, David Ahern wrote:
> >> On 8/10/19 12:30 AM, Jiri Pirko wrote:
> >>> Could you please write me an example message of add/remove?
> >>
> >> altnames are for ex
On Sun, Aug 11, 2019 at 3:10 PM Michal Kubecek wrote:
>
> On Sat, Aug 10, 2019 at 12:39:31PM -0700, Roopa Prabhu wrote:
> > On Sat, Aug 10, 2019 at 8:50 AM Michal Kubecek wrote:
> > >
> > > On Sat, Aug 10, 2019 at 06:46:57AM -0700, Roopa Prabhu wrote:
> >
On Mon, Aug 12, 2019 at 8:40 AM Stephen Hemminger
wrote:
>
> On Mon, 12 Aug 2019 10:31:39 +0200
> Jiri Pirko wrote:
>
> > Mon, Aug 12, 2019 at 03:37:26AM CEST, dsah...@gmail.com wrote:
> > >On 8/11/19 7:34 PM, David Ahern wrote:
> > >> On 8/10/19 12:30 AM, Jiri Pirko wrote:
> > >>> Could you plea
On 8/11/20 5:44 AM, Michael S. Tsirkin wrote:
External email: Use caution opening links or attachments
On Tue, Aug 11, 2020 at 11:58:23AM +, Eli Cohen wrote:
On Tue, Aug 11, 2020 at 11:26:20AM +, Eli Cohen wrote:
Hi All
Currently, the only statistics we get for a VDPA instance come
On 8/13/20 8:08 AM, Adrian Pop wrote:
The Common Management Interface Specification (CMIS) for QSFP-DD shares
some similarities with other form factors such as QSFP or SFP, but due to
the fact that the module memory map is different, the current ethtool
version is not able to provide relevant i
From: Roopa Prabhu
This patch adds support for recently
added link IFLA_PROTO_DOWN_REASON attribute.
IFLA_PROTO_DOWN_REASON enumerates reasons
for the already existing IFLA_PROTO_DOWN link
attribute.
$ cat /etc/iproute2/protodown_reasons.d/r.conf
0 mlag
1 evpn
2 vrrp
3 psecurity
$ ip link set
On 8/20/20 9:36 PM, Stephen Hemminger wrote:
On Thu, 20 Aug 2020 20:52:02 -0700
Roopa Prabhu wrote:
+ if (tb[IFLA_PROTO_DOWN]) {
+ if (rta_getattr_u8(tb[IFLA_PROTO_DOWN]))
+ print_bool(PRINT_ANY,
+"proto
On 8/20/20 10:18 PM, Roopa Prabhu wrote:
On 8/20/20 9:36 PM, Stephen Hemminger wrote:
On Thu, 20 Aug 2020 20:52:02 -0700
Roopa Prabhu wrote:
+ if (tb[IFLA_PROTO_DOWN]) {
+ if (rta_getattr_u8(tb[IFLA_PROTO_DOWN]))
+ print_bool(PRINT_ANY
On Sun, Jun 23, 2019 at 7:18 PM Taehee Yoo wrote:
>
> On Mon, 24 Jun 2019 at 03:07, David Miller wrote:
> >
>
> Hi David,
>
> Thank you for the review!
>
> > From: Taehee Yoo
> > Date: Thu, 20 Jun 2019 20:51:08 +0900
> >
> > > __vxlan_dev_create() destroys FDB using specific pointer which indica
On Tue, Jun 25, 2019 at 9:08 AM Taehee Yoo wrote:
>
> On Tue, 25 Jun 2019 at 13:12, Roopa Prabhu wrote:
> >
>
> Hi Roopa,
>
> Thank you for the review!
>
> > On Sun, Jun 23, 2019 at 7:18 PM Taehee Yoo wrote:
> > >
> > > On Mon, 24 Jun 2019 at
From: Roopa Prabhu
This series adds a new test to test fib rules.
ip route get is used to test fib rule matches.
This series also extends ip route get to match on
sport and dport to test recent support of sport
and dport fib rule match.
v2 - address ido's commemt to make sport dport
ip
From: Roopa Prabhu
This is a followup to fib rules sport, dport match support.
Having them supported in getroute makes it easier to test
fib rule lookups. Used by fib rule self tests. Before this patch
getroute used same skb to pass through the route lookup and
for the netlink getroute reply msg
From: Roopa Prabhu
This is a followup to fib6 rules sport and dport
match support. Having them supported in getroute
makes it easier to test fib6 rule lookups. Used by fib6 rule
self tests.
Signed-off-by: Roopa Prabhu
---
net/ipv6/route.c | 25 +
1 file changed, 25
From: Roopa Prabhu
This adds a first set of tests for fib rule match/action for
ipv4 and ipv6. Initial tests only cover action lookup table.
can be extended to cover other actions in the future.
Uses ip route get to validate the rule lookup.
Signed-off-by: Roopa Prabhu
---
tools/testing
On Sun, May 6, 2018 at 6:46 PM, David Ahern wrote:
> On 5/6/18 6:59 PM, Roopa Prabhu wrote:
>> From: Roopa Prabhu
>>
>> This is a followup to fib rules sport, dport match support.
>> Having them supported in getroute makes it easier to test
>> fib rule loo
On Tue, Apr 17, 2018 at 1:10 AM, Ido Schimmel wrote:
> On Mon, Apr 16, 2018 at 01:41:36PM -0700, Roopa Prabhu wrote:
>> @@ -2757,6 +2796,12 @@ static int inet_rtm_getroute(struct sk_buff *in_skb,
>> struct nlmsghdr *nlh,
>> fl4.flowi4_oif = tb[RTA_OIF] ? nla_get
From: Roopa Prabhu
Signed-off-by: Roopa Prabhu
---
include/net/fib_rules.h | 3 ++-
net/core/fib_rules.c| 55 +
net/decnet/dn_rules.c | 7 +--
net/ipv4/fib_rules.c| 7 +--
net/ipv4/ipmr.c | 3 ++-
net/ipv6
From: Roopa Prabhu
First patch refactors code to move fib rule netlink handling
into a common function. This became obvious when adding
duplicate extack msgs in add and del paths. Second patch
adds extack msgs.
v2 - Dropped the ip route get support and selftests from
the series to look at
From: Roopa Prabhu
This reduces code duplication in the fib rule add and del paths.
Get rid of validate_rulemsg. This became obvious when adding duplicate
extack support in fib newrule/delrule error paths.
Signed-off-by: Roopa Prabhu
---
net/core/fib_rules.c | 436
On Sun, Apr 22, 2018 at 11:54 AM, David Miller wrote:
> From: Johannes Berg
> Date: Thu, 19 Apr 2018 17:26:57 +0200
>
>> On Thu, 2018-04-19 at 08:25 -0700, Ben Greear wrote:
>>>
>>> Maybe this could be in followup patches? It's going to touch a lot of
>>> files,
>>> and might be hell to get mer
From: Roopa Prabhu
Fixes: b16fb418b1bf ("net: fib_rules: add extack support")
Signed-off-by: Roopa Prabhu
---
Looks like I broke this when i split extack changes into a separate patch :(
net/core/fib_rules.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/net/core/fib_rules.c
On Mon, Apr 23, 2018 at 7:21 AM, David Miller wrote:
> From: Roopa Prabhu
> Date: Sat, 21 Apr 2018 09:41:29 -0700
>
>> From: Roopa Prabhu
>>
>> First patch refactors code to move fib rule netlink handling
>> into a common function. This became obvious when addin
> Signed-off-by: Florian Fainelli
Acked-by: Roopa Prabhu
Thanks Florian.
On Tue, Apr 24, 2018 at 2:46 AM, Anders Roxell wrote:
> Hi,
>
> fib-onlink-tests.sh (from kselftest) found a regression between
> next-20180424 [1] (worked with tag next-20180423 [2])
>
> here is tree commits that look suspicious specially this patch (sha:
> f9d4b0c1e969)
> rewrites fib_nl_newrule
From: Roopa Prabhu
This patch extends NTF_EXT_LEARNED support to the neighbour system.
Example use-case: An Ethernet VPN implementation (eg in FRR routing suite)
can use this flag to add dynamic reachable external neigh entires
learned via control plane. The use of neigh NTF_EXT_LEARNED in this
On Wed, Apr 25, 2018 at 10:20 AM, David Miller wrote:
> From: Roopa Prabhu
> Date: Tue, 24 Apr 2018 13:49:34 -0700
>
>> From: Roopa Prabhu
>>
>> This patch extends NTF_EXT_LEARNED support to the neighbour system.
>> Example use-case: An Ethernet VPN implem
On Thu, Mar 22, 2018 at 3:55 AM, Jiri Pirko wrote:
> From: Jiri Pirko
>
> This patchset resolves 2 issues we have right now:
> 1) There are many netdevices / ports in the system, for port, pf, vf
>represenatation but the user has no way to see which is which
> 2) The ndo_get_phys_port_name is
On Thu, Mar 22, 2018 at 8:34 AM, David Ahern wrote:
> On 3/22/18 4:55 AM, Jiri Pirko wrote:
>> From: Jiri Pirko
>>
>> This patchset resolves 2 issues we have right now:
>> 1) There are many netdevices / ports in the system, for port, pf, vf
>>represenatation but the user has no way to see whi
he user only needs to set a larger MTU on the member
> ports that are participating in the large MTU VLANS.
>
> Signed-off-by: Chas Williams <3ch...@gmail.com>
> ---
Acked-by: Roopa Prabhu
This or an equivalent fix is necessary: as stated above, today the
bridge mtu capped at min
On Thu, Mar 22, 2018 at 9:53 PM, Roopa Prabhu wrote:
> On Thu, Mar 22, 2018 at 8:34 AM, Chas Williams <3ch...@gmail.com> wrote:
>> If the bridge is allowing multiple VLANs, some VLANs may have
>> different MTUs. Instead of choosing the minimum MTU for the
>> bridge in
nl_newlink+0xb75/0x1180
> [ 213.554119] ? rtnl_link_unregister+0x230/0x230
> [ ... ]
>
> Fixes: 0241b836732f ("vxlan: fix default fdb entry netlink notify ordering
> during netdev create")
> Suggested-by: Roopa Prabhu
> Signed-off-by: Taehee Y
_rtnl_newlink+0xb75/0x1180
> [ 213.554119] ? rtnl_link_unregister+0x230/0x230
> [ ... ]
>
> Fixes: 0241b836732f ("vxlan: fix default fdb entry netlink notify ordering
> during netdev create")
> Suggested-by: Roopa Prabhu
> Signed-off-by: Taehee Yoo
Acke
On Mon, Jul 8, 2019 at 4:12 PM David Miller wrote:
>
> From: Petar Penkov
> Date: Fri, 5 Jul 2019 11:46:43 -0700
>
> > Rules matching on loopback iif do not need early flow dissection as the
> > packet originates from the host. Stop counting such rules in
> > fib_rule_requires_fldissect
> >
> >
On Tue, Aug 15, 2017 at 5:05 AM, Florian Westphal wrote:
> idaifish wrote:
>> Syzkaller hit 'general protection fault in fib_dump_info' bug on
>> commit 4.13-rc5..
>
> CC Roopa
>
>> Guilty file: net/ipv4/fib_semantics.c
>>
>> kasan: GPF could be caused by NULL-ptr deref or user memory access
>> g
From: Roopa Prabhu
Syzkaller hit 'general protection fault in fib_dump_info' bug on
commit 4.13-rc5..
Guilty file: net/ipv4/fib_semantics.c
kasan: GPF could be caused by NULL-ptr deref or user memory access
general protection fault: [#1] SMP KASAN
Modules linked in:
On Tue, Aug 15, 2017 at 7:56 PM, David Ahern wrote:
> On 8/15/17 8:50 PM, Roopa Prabhu wrote:
>> diff --git a/net/ipv4/route.c b/net/ipv4/route.c
>> index 7effa62..49a018f 100644
>> --- a/net/ipv4/route.c
>> +++ b/net/ipv4/route.c
>> @@ -2763,14 +2763,21 @@ st
On Tue, Aug 15, 2017 at 2:37 AM, David Lamparter wrote:
[snip]
> I think the reverse is the better option, removing the vpls device
> information and just going with the route table. My approach to this
> would be to add a new netlink route attribute "RTA_VPLS" which
> identifies the vpls devic
From: Roopa Prabhu
Syzkaller hit 'general protection fault in fib_dump_info' bug on
commit 4.13-rc5..
Guilty file: net/ipv4/fib_semantics.c
kasan: GPF could be caused by NULL-ptr deref or user memory access
general protection fault: [#1] SMP KASAN
Modules linked in:
CPU: 0 PID:
On Mon, Aug 21, 2017 at 10:15 AM, David Lamparter wrote:
> Hi all,
>
>
> this is an update on the earlier "[RFC net-next] VPLS support". Note
> I've changed the subject lines on some of the patches to better reflect
> what they really do (tbh the earlier subject lines were crap.)
>
> As previousl
From: Roopa Prabhu
current switchdev drivers dont seem to support offloading fdb
entries pointing to the bridge device which have fdb->dst
not set to any port. This patch adds a NULL fdb->dst check in
the switchdev notifier code.
This patch fixes the below NULL ptr dereference:
$bridge f
From: Roopa Prabhu
Tracepoints to trace bridge forwarding database updates.
Signed-off-by: Roopa Prabhu
---
include/trace/events/bridge.h | 98 +++
net/bridge/br_fdb.c | 7
net/core/net-traces.c | 6 +++
3 files changed, 111
On Sun, Aug 27, 2017 at 7:11 PM, Florian Fainelli wrote:
> On 08/27/2017 02:33 PM, Roopa Prabhu wrote:
>> From: Roopa Prabhu
>>
>> Tracepoints to trace bridge forwarding database updates.
>
> Thanks for adding this!
>
>>
>> Signed-off-by: Roopa Prabhu
On Sun, Aug 27, 2017 at 7:11 PM, Florian Fainelli wrote:
> On 08/27/2017 02:33 PM, Roopa Prabhu wrote:
>> From: Roopa Prabhu
>>
>> Tracepoints to trace bridge forwarding database updates.
>
> Thanks for adding this!
>
>>
>> Signed-off-by: Roopa Prabhu
On Sat, Aug 26, 2017 at 10:04 AM, Ido Schimmel wrote:
> On Fri, Aug 25, 2017 at 01:26:07PM -0700, David Ahern wrote:
>> Jiri / Ido:
>>
>>
[snip]
>
> Regarding the silent abort, that's intentional. You can look at the same
> code in v4.9 - when the chain was still blocking - and you'll see that
> w
On Tue, Aug 27, 2019 at 2:35 AM Jiri Pirko wrote:
>
> Tue, Aug 27, 2019 at 10:22:42AM CEST, da...@davemloft.net wrote:
> >From: Jiri Pirko
> >Date: Tue, 27 Aug 2019 09:08:08 +0200
> >
> >> Okay, so if I understand correctly, on top of separate commands for
> >> add/del of alternative names, you s
On Wed, Aug 28, 2019 at 12:07 AM Jiri Pirko wrote:
>
> Tue, Aug 27, 2019 at 05:14:49PM CEST, ro...@cumulusnetworks.com wrote:
> >On Tue, Aug 27, 2019 at 2:35 AM Jiri Pirko wrote:
> >>
> >> Tue, Aug 27, 2019 at 10:22:42AM CEST, da...@davemloft.net wrote:
> >> >From: Jiri Pirko
> >> >Date: Tue, 27
On Wed, Aug 28, 2019 at 10:26 PM Michal Kubecek wrote:
>
> On Wed, Aug 28, 2019 at 09:36:41PM -0700, Roopa Prabhu wrote:
> >
> > yes, correct. I mentioned that because I was wondering if we can
> > think along the same lines for this API.
> > eg
> > (a)
On Mon, Feb 18, 2019 at 6:17 PM Li RongQing wrote:
>
> br_ip4_multicast_mrd_rcv only return 0 and -ENOMSG,
> no other negative value
>
> Signed-off-by: Li RongQing
Acked-by: Roopa Prabhu
looks fine to me. CC Nikolay
> net/bridge/br_multicast.c | 7 +--
> 1 file
From: Roopa Prabhu
Also, extend neigh_state_str to include neigh dummy states
noarp and permanent
Fixes: 9c03b282badb ("trace: events: add a few neigh tracepoints")
Signed-off-by: Roopa Prabhu
---
include/trace/events/neigh.h | 8 +---
1 file changed, 5 insertions(+), 3 deletion
From: Roopa Prabhu
This series adds extack support to changelink paths.
In the process re-factors flag sets to a separate helper.
Also adds some changelink testcases to rtnetlink.sh
(This series was initially part of another series that
tried to support changelink for more attributes.
But after
From: Roopa Prabhu
This patch extends rtnetlink.sh to cover some vxlan flag
netlink attribute sets.
Signed-off-by: Roopa Prabhu
---
tools/testing/selftests/net/rtnetlink.sh | 52
1 file changed, 52 insertions(+)
diff --git a/tools/testing/selftests/net
From: Roopa Prabhu
This patch adds extack coverage in vxlan link
create and changelink paths. Introduces a new helper
vxlan_nl2flags to consolidate flag attribute validation.
thanks to Johannes Berg for some tips to construct the
generic vxlan flag extack strings.
Signed-off-by: Roopa Prabhu
On Tue, Feb 26, 2019 at 5:51 AM Petr Machata wrote:
>
>
> Roopa Prabhu writes:
>
> > From: Roopa Prabhu
> >
> > This patch adds extack coverage in vxlan link
> > create and changelink paths. Introduces a new helper
> > vxlan_nl2flags to consolidate fl
On Tue, Feb 26, 2019 at 9:45 AM Petr Machata wrote:
>
>
> Roopa Prabhu writes:
>
> > On Tue, Feb 26, 2019 at 5:51 AM Petr Machata wrote:
> >>
> >> Many of the flags for which you call this don't actually have the else
> >> branch. Howeve
From: Roopa Prabhu
We already print src_vni for a fdb entry when present.
This patch adds the ability to set src_vni on a fdb
entry. When not specified, kernel will use vni specified
on the vxlan device. This can be used on a vxlan fdb entry
when the vxlan device is in external or collect
On Fri, Mar 15, 2019 at 10:56 AM Petr Machata wrote:
>
> In general, after a port is put administratively up, certain handshake
> protocols have to finish successfully, otherwise the port is left in a
> NO-CARRIER or DORMANT state. When that happens, it would be useful to
> communicate the reasons
ow commit
already in the tree ?
commit 82cbb5c631a07b3aa6df6eab644d55da9de5a645
Author: Roopa Prabhu
Date: Wed Dec 19 12:51:38 2018 -0800
neighbour: register rtnl doit handler
On Wed, Oct 4, 2017 at 3:52 PM, David Miller wrote:
> From: Roopa Prabhu
> Date: Tue, 3 Oct 2017 22:12:31 -0700
>
>> BR_ARP_PROXY flag but has a few semantic differences to conform
>
> This should be "BR_PROXYARP".
ack, will fix.
>
> Otherwise this ser
On Thu, Oct 5, 2017 at 11:30 AM, Jakub Kicinski wrote:
> On Fri, 28 Jul 2017 23:28:26 -0700, Roopa Prabhu wrote:
>> On Fri, Jul 28, 2017 at 9:46 AM, Jakub Kicinski wrote:
>> > On Fri, 28 Jul 2017 07:53:01 -0700, Roopa Prabhu wrote:
>> >> On Thu, Jul 27, 2017 at
From: Roopa Prabhu
This series implements arp and nd suppression in the bridge
driver for ethernet vpns. It implements rfc7432, section 10
https://tools.ietf.org/html/rfc7432#section-10
for ethernet VPN deployments. It is similar to the existing
BR_PROXYARP* flags but has a few semantic
From: Roopa Prabhu
This patch avoids flooding and proxies ndisc packets
for BR_NEIGH_SUPPRESS ports.
Signed-off-by: Roopa Prabhu
---
net/bridge/br_arp_nd_proxy.c | 249 +++
net/bridge/br_device.c | 11 ++
net/bridge/br_input.c| 11
From: Roopa Prabhu
This patch avoids flooding and proxies arp packets
for BR_NEIGH_SUPPRESS ports.
Moves existing br_do_proxy_arp to br_do_proxy_suppress_arp
to support both proxy arp and neigh suppress.
Signed-off-by: Roopa Prabhu
---
net/bridge/br_arp_nd_proxy.c | 188
From: Roopa Prabhu
This patch adds a new bridge port flag BR_NEIGH_SUPPRESS to
suppress arp and nd flood on bridge ports. It implements
rfc7432, section 10.
https://tools.ietf.org/html/rfc7432#section-10
for ethernet VPN deployments. It is similar to the existing
BR_PROXYARP* flags but has a few
On Fri, Oct 6, 2017 at 11:34 AM, Roopa Prabhu wrote:
> From: Roopa Prabhu
>
> This series implements arp and nd suppression in the bridge
> driver for ethernet vpns. It implements rfc7432, section 10
> https://tools.ietf.org/html/rfc7432#section-10
> for ethernet VPN deployme
From: Roopa Prabhu
This patch adds a new bridge port flag BR_NEIGH_SUPPRESS to
suppress arp and nd flood on bridge ports. It implements
rfc7432, section 10.
https://tools.ietf.org/html/rfc7432#section-10
for ethernet VPN deployments. It is similar to the existing
BR_PROXYARP* flags but has a few
From: Roopa Prabhu
This series implements arp and nd suppression in the bridge
driver for ethernet vpns. It implements rfc7432, section 10
https://tools.ietf.org/html/rfc7432#section-10
for ethernet VPN deployments. It is similar to the existing
BR_PROXYARP* flags but has a few semantic
From: Roopa Prabhu
This patch avoids flooding and proxies arp packets
for BR_NEIGH_SUPPRESS ports.
Moves existing br_do_proxy_arp to br_do_proxy_suppress_arp
to support both proxy arp and neigh suppress.
Signed-off-by: Roopa Prabhu
---
net/bridge/br_arp_nd_proxy.c | 188
From: Roopa Prabhu
This patch avoids flooding and proxies ndisc packets
for BR_NEIGH_SUPPRESS ports.
Signed-off-by: Roopa Prabhu
---
net/bridge/br_arp_nd_proxy.c | 249 +++
net/bridge/br_device.c | 11 ++
net/bridge/br_input.c| 11
From: Roopa Prabhu
neigh suppression can be used to suppress arp and nd flood
to bridge ports. It maps to the recently added
kernel support for bridge port flag IFLA_BRPORT_NEIGH_SUPPRESS.
Signed-off-by: Roopa Prabhu
---
bridge/link.c| 13 +
ip/iplink_bridge_slave.c
On Thu, Oct 12, 2017 at 6:34 AM, Steve Lin wrote:
> Adds a devlink command for getting & setting device configuration
> parameters, and enumerates a bunch of those parameters as devlink
> attributes. Also introduces an attribute that can be set by a
> driver to indicate that the config change doe
On Thu, Oct 12, 2017 at 7:40 AM, Jiri Pirko wrote:
> Thu, Oct 12, 2017 at 04:35:10PM CEST, ro...@cumulusnetworks.com wrote:
>>On Thu, Oct 12, 2017 at 6:34 AM, Steve Lin wrote:
>>> Adds a devlink command for getting & setting device configuration
>>> parameters, and enumerates a bunch of those par
On Thu, Oct 12, 2017 at 7:45 AM, Steve Lin wrote:
> Hi Roopa,
>
> The attributes added in this patchset are not really the same type as
> ethtool - these are more device configuration type attributes. The
> speeds you saw, for example, affect the pre-OS [i.e. PXE boot time]
> configuration for a
On Thu, Oct 12, 2017 at 8:04 AM, Jiri Pirko wrote:
> Thu, Oct 12, 2017 at 04:46:24PM CEST, ro...@cumulusnetworks.com wrote:
>>On Thu, Oct 12, 2017 at 7:40 AM, Jiri Pirko wrote:
>>> Thu, Oct 12, 2017 at 04:35:10PM CEST, ro...@cumulusnetworks.com wrote:
On Thu, Oct 12, 2017 at 6:34 AM, Steve Li
On Thu, Oct 12, 2017 at 8:43 AM, Florian Fainelli wrote:
> On October 12, 2017 8:04:19 AM PDT, Jiri Pirko wrote:
>>Thu, Oct 12, 2017 at 04:46:24PM CEST, ro...@cumulusnetworks.com wrote:
>>>On Thu, Oct 12, 2017 at 7:40 AM, Jiri Pirko wrote:
Thu, Oct 12, 2017 at 04:35:10PM CEST, ro...@cumulus
On Thu, Oct 12, 2017 at 12:20 PM, Florian Fainelli wrote:
> On 10/12/2017 12:06 PM, David Miller wrote:
>> From: Florian Fainelli
>> Date: Thu, 12 Oct 2017 08:43:59 -0700
>>
>>> Once we move ethtool (or however we name its successor) over to
>>> netlink there is an opportunity for accessing objec
On Thu, Oct 12, 2017 at 2:45 PM, Ben Greear wrote:
> On 10/11/2017 01:49 PM, David Miller wrote:
>>
>> From: "John W. Linville"
>> Date: Wed, 11 Oct 2017 16:44:07 -0400
>>
>>> On Wed, Oct 11, 2017 at 09:51:56AM -0700, Ben Greear wrote:
I noticed today that setting some ethtool settings
On Fri, Oct 13, 2017 at 12:11 AM, Jiri Pirko wrote:
> Thu, Oct 12, 2017 at 11:53:56PM CEST, ro...@cumulusnetworks.com wrote:
>>On Thu, Oct 12, 2017 at 12:20 PM, Florian Fainelli
>>wrote:
>>> On 10/12/2017 12:06 PM, David Miller wrote:
From: Florian Fainelli
Date: Thu, 12 Oct 2017 08:4
On Sat, Jun 23, 2018 at 8:59 AM, Jason A. Donenfeld wrote:
> Two rules with different values of suppress_prefix or suppress_ifgroup
> are not the same. This fixes an -EEXIST when running:
>
>$ ip -4 rule add table main suppress_prefixlength 0
>
> Signed-off-by: Jason A. Donenfeld
> Fixes: f9d
On Sat, Jun 23, 2018 at 8:46 AM, Jason A. Donenfeld wrote:
> Hey Roopa,
>
> On a kernel with a minimal networking config,
> CONFIG_IP_MULTIPLE_TABLES appears to be broken for certain rules after
> f9d4b0c1e9695e3de7af3768205bacc27312320c.
>
> Try, for example, running:
>
> $ ip -4 rule add table m
On Mon, Jun 25, 2018 at 8:23 AM, Roopa Prabhu wrote:
> On Sat, Jun 23, 2018 at 8:46 AM, Jason A. Donenfeld wrote:
>> Hey Roopa,
>>
>> On a kernel with a minimal networking config,
>> CONFIG_IP_MULTIPLE_TABLES appears to be bro
From: Roopa Prabhu
In systems where neigh gc thresh holds are set to high values,
admin deleted neigh entries (eg ip neigh flush or ip neigh del) can
linger around in NUD_FAILED state for a long time until periodic gc kicks
in. This patch forces neigh_invalidate when NUD_FAILED neigh_update is
On Mon, Jun 25, 2018 at 4:39 PM, Jason A. Donenfeld wrote:
> Two rules with different values of suppress_prefix or suppress_ifgroup
> are not the same. This fixes an -EEXIST when running:
>
>$ ip -4 rule add table main suppress_prefixlength 0
>
> Signed-off-by: Jason A. Donenfeld
> Fixes: f9d
On Tue, Jun 26, 2018 at 6:34 PM, David Miller wrote:
> From: "Jason A. Donenfeld"
> Date: Tue, 26 Jun 2018 01:39:32 +0200
>
>> Two rules with different values of suppress_prefix or suppress_ifgroup
>> are not the same. This fixes an -EEXIST when running:
>>
>>$ ip -4 rule add table main suppr
From: Roopa Prabhu
After commit f9d4b0c1e969 ("fib_rules: move common handling of newrule
delrule msgs into fib_nl2rule"), rule_find is strict about checking
for an existing rule. rule_find must check against all
user given attributes, else it may match against a subset
of attributes
On Wed, Jun 27, 2018 at 6:27 PM, Roopa Prabhu wrote:
> From: Roopa Prabhu
>
> After commit f9d4b0c1e969 ("fib_rules: move common handling of newrule
> delrule msgs into fib_nl2rule"), rule_find is strict about checking
> for an existing rule. rule_find must check
On Thu, Jun 28, 2018 at 9:59 PM, Roopa Prabhu wrote:
> On Wed, Jun 27, 2018 at 6:27 PM, Roopa Prabhu
> wrote:
>> From: Roopa Prabhu
>>
>> After commit f9d4b0c1e969 ("fib_rules: move common handling of newrule
>> delrule msgs into fib_nl2rule"), rule
From: Roopa Prabhu
After commit f9d4b0c1e969 ("fib_rules: move common handling of newrule
delrule msgs into fib_nl2rule"), rule_exists got replaced by rule_find
for existing rule lookup in both the add and del paths. While this
is good for the delete path, it solves a few problems but
From: Roopa Prabhu
Problem:
In vxlan_newlink, a default fdb entry is added before register_netdev.
The default fdb creation function also notifies user-space of the
fdb entry on the vxlan device which user-space does not know about yet.
(RTM_NEWNEIGH goes before RTM_NEWLINK for the same ifindex
From: Roopa Prabhu
Add a new option do_notify to vxlan_fdb_destroy to make
sending netlink notify optional. Used by a later patch.
Signed-off-by: Roopa Prabhu
---
drivers/net/vxlan.c | 14 --
1 file changed, 8 insertions(+), 6 deletions(-)
diff --git a/drivers/net/vxlan.c b
From: Roopa Prabhu
rtnl_configure_link sets dev->rtnl_link_state to
RTNL_LINK_INITIALIZED and unconditionally calls
__dev_notify_flags to notify user-space of dev flags.
current call sequence for rtnl_configure_link
rtnetlink_newlink
rtnl_link_ops->newlink
rtnl_configur
From: Roopa Prabhu
Problem:
In vxlan_newlink, a default fdb entry is added before register_netdev.
The default fdb creation function notifies user-space of the
fdb entry on the vxlan device which user-space does not know about yet.
(RTM_NEWNEIGH goes before RTM_NEWLINK for the same ifindex
From: Roopa Prabhu
- Add new vxlan_fdb_alloc helper
- rename existing vxlan_fdb_create into vxlan_fdb_update:
because it really creates or updates an existing
fdb entry
- move new fdb creation into a separate vxlan_fdb_create
Main motivation for this change is to introduce the
On Sat, Jul 7, 2018 at 4:23 AM, David Miller wrote:
> From: Roopa Prabhu
> Date: Wed, 4 Jul 2018 16:46:28 -0700
>
>> From: Roopa Prabhu
>>
>> Problem:
>> In vxlan_newlink, a default fdb entry is added before register_netdev.
>> The default fdb creat
1 - 100 of 829 matches
Mail list logo
