[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3828cf04-1bf8-92d2-dfc4-184bd615fe10@gmail.com>
Date: Fri, 12 May 2017 10:26:08 -0700
From: David Ahern <dsahern@...il.com>
To: David Miller <davem@...emloft.net>, mq@....cz
Cc: netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
dsa@...ulusnetworks.com, kuznet@....inr.ac.ru, jmorris@...ei.org,
yoshfuji@...ux-ipv6.org, kaber@...sh.net
Subject: Re: [PATCH] net: ipv6: Truncate single route when it doesn't fit into
dump buffer.
On 5/12/17 8:24 AM, David Miller wrote:
> From: Jan Moskyto Matejka <mq@....cz>
> Date: Fri, 12 May 2017 13:15:10 +0200
>
>> -int rt6_dump_route(struct rt6_info *rt, void *p_arg);
>> +int rt6_dump_route(struct rt6_info *rt, void *p_arg, int truncate);
>
> Please use "bool" and "true"/"false" for boolean values.
>
> What does ipv4 do in this situation?
>
> I'm hesitant to be OK with adding a new nlmsg flag just for this case
> if we solve this problem differently and using existing mechanisms
> elsewhere.
>
I'll take a look at this later today or this weekend; we can't just
truncate the route returned to userspace.
Powered by blists - more mailing lists