[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6d1a324e-e29e-e2dd-a6fc-1e9b4455cb3d@cumulusnetworks.com>
Date: Sun, 27 Nov 2016 19:39:18 -0700
From: David Ahern <dsa@...ulusnetworks.com>
To: 张胜举 <zhangshengju@...s.chinamobile.com>,
netdev@...r.kernel.org
Subject: Re: [net,v2] neigh: fix the loop index error in neigh dump
On 11/27/16 7:34 PM, 张胜举 wrote:
>> -----Original Message-----
>> From: David Ahern [mailto:dsa@...ulusnetworks.com]
>> Sent: Monday, November 28, 2016 10:10 AM
>> To: Zhang Shengju <zhangshengju@...s.chinamobile.com>;
>> netdev@...r.kernel.org
>> Subject: Re: [net,v2] neigh: fix the loop index error in neigh dump
>>
>> On 11/27/16 6:32 PM, Zhang Shengju wrote:
>>> Loop index in neigh dump function is not updated correctly under some
>>> circumstances, this patch will fix it.
>>
>> What's an example?
>
> If dev is filtered out, the original code goes to next loop without updating
> loop index 'idx'.
And you have a use case with missing or redundant data? Or is your comment based on a review of code only?
>> You are completely rewriting the dump loops.
>
> I put 'idx++' into for loop, so I replace 'goto' with 'continue'. The
> other change is style related.
A "fixes" should not include 'style related' changes.
Powered by blists - more mailing lists