[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a8fac40d-b46f-5c4f-f4c6-43d4c8a31ffe@mojatatu.com>
Date: Wed, 22 Apr 2020 13:07:54 -0400
From: Jamal Hadi Salim <jhs@...atatu.com>
To: Dominique Martinet <asmadeus@...ewreck.org>,
Andrea Claudi <aclaudi@...hat.com>
Cc: Stephen Hemminger <stephen@...workplumber.org>,
linux-netdev <netdev@...r.kernel.org>,
David Ahern <dsahern@...il.com>, daniel@...earbox.net,
Jamal Hadi Salim <hadi@...atatu.com>
Subject: Re: [PATCH iproute2 v2 1/2] bpf: Fix segfault when custom pinning is
used
On 2020-04-22 10:43 a.m., Dominique Martinet wrote:
[...]
> I'm actually not sure snprintf can return < 0...
Man page says it can (quick grep on iproute2 code shows some
invocations can check for <=0)
> wide character
> formatting functions can but basic ones not really, there's hardly any
> snprintf return checking in iproute2 code...
>
>
> Anyway, with all that said this patch currently technically works for
> me, despite being not so clear, so can add my reviewed-by on whatever
> final version you take (check < 0 or >= PATH_MAX or none or both), if
> you'd like :)
Will update the next chance i get to.
>
> Now I'm looking at this we're a bit inconsistent with return values in
> this function, other error paths return negative value + errno set,
> and this only returns -errno.
>
> Digging a bit into callers it looks like errno is the way to go, so
> while you're modifying this it might be worth setting errno
> to EINVALas
> well here?
>
Will do. I wanted to leave code that didnt affect me alone; but
granted it is reasonable for consistency..
>
> Cheers & sorry for nitpicking,
>
No sweat - we havent yet entered the realm where the color
of the bike shed begins to matter ;->
cheers,
jamal
Powered by blists - more mailing lists