[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <70a46492-5d87-59fd-fa67-29c6d276c8a0@gmail.com>
Date: Tue, 9 Apr 2019 17:43:42 -0700
From: David Ahern <dsahern@...il.com>
To: Govindarajulu Varadarajan <govind.varadar@...il.com>,
David Ahern <dsahern@...nel.org>
Cc: davem@...emloft.net, netdev@...r.kernel.org, idosch@...lanox.com,
jiri@...lanox.com, benve@...co.com
Subject: Re: [PATCH v2 net-next 08/18] ipv4: Refactor fib_check_nh
On 4/9/19 5:08 PM, Govindarajulu Varadarajan wrote:
> On Fri, Apr 5, 2019 at 4:32 PM David Ahern <dsahern@...nel.org> wrote:
>>
>> From: David Ahern <dsahern@...il.com>
>>
>> fib_check_nh is currently huge covering multiple uses cases - device only,
>> device + gateway, and device + gateway with ONLINK. The next patch adds
>> validation checks for IPv6 which only further complicates it. So, break
>> fib_check_nh into 2 helpers - one for gateway validation and one for device
>> only.
>>
>> Signed-off-by: David Ahern <dsahern@...il.com>
>> Reviewed-by: Ido Schimmel <idosch@...lanox.com>
>
> With the latest net-next I am having issue with network traffic.
> git bisect points to this commit as the first bad commit.
> (448d7248191706cbbd7761e3bc72c2985c4d38a7 ipv4: Refactor fib_check_nh)
>
Thanks for the report. I'll take a look tonight.
Powered by blists - more mailing lists