Daniel Borkmann writes:
> On 8/13/20 9:52 PM, Toke Høiland-Jørgensen wrote:
>> Andrii Nakryiko writes:
>>> On Thu, Aug 13, 2020 at 7:29 AM Toke Høiland-Jørgensen
>>> wrote:
Turns out there were a few more instances where libbpf didn't save the
errno before writing an error messa
On 8/13/20 9:52 PM, Toke Høiland-Jørgensen wrote:
Andrii Nakryiko writes:
On Thu, Aug 13, 2020 at 7:29 AM Toke Høiland-Jørgensen wrote:
Turns out there were a few more instances where libbpf didn't save the
errno before writing an error message, causing errno to be overridden by
the printf()
Andrii Nakryiko writes:
> On Thu, Aug 13, 2020 at 7:29 AM Toke Høiland-Jørgensen
> wrote:
>>
>> Turns out there were a few more instances where libbpf didn't save the
>> errno before writing an error message, causing errno to be overridden by
>> the printf() return and the error disappearing if
On Thu, Aug 13, 2020 at 7:29 AM Toke Høiland-Jørgensen wrote:
>
> Turns out there were a few more instances where libbpf didn't save the
> errno before writing an error message, causing errno to be overridden by
> the printf() return and the error disappearing if logging is enabled.
>
> Signed-off
Turns out there were a few more instances where libbpf didn't save the
errno before writing an error message, causing errno to be overridden by
the printf() return and the error disappearing if logging is enabled.
Signed-off-by: Toke Høiland-Jørgensen
---
tools/lib/bpf/libbpf.c | 12 +++-