[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CACdoK4+h6SjPe9XGbC5WWLcAhZoq9C3zcPEOe4PQ0TVzrDxiCA@mail.gmail.com>
Date: Sat, 25 Apr 2020 11:19:18 +0100
From: Quentin Monnet <quentin@...valent.com>
To: Andrii Nakryiko <andrii.nakryiko@...il.com>
Cc: Andrii Nakryiko <andriin@...com>, bpf <bpf@...r.kernel.org>,
Networking <netdev@...r.kernel.org>,
Alexei Starovoitov <ast@...com>,
Daniel Borkmann <daniel@...earbox.net>,
Kernel Team <kernel-team@...com>
Subject: Re: [PATCH bpf-next 07/10] bpftool: expose attach_type-to-string
array to non-cgroup code
On Sat, 25 Apr 2020 at 01:12, Andrii Nakryiko <andrii.nakryiko@...il.com> wrote:
>
> Ah, I see what you are saying... I can just declare array as
>
> const char *attach_type_strings[__MAX_BPF_ATTACH_TYPE] = { ... }
>
That would address my concern, thanks!
> to prevent this. There is still this issue of potentially getting back
> NULL pointer. But that warrants separate "audit" of the code usage and
> fixing appropriately, I don't think it belongs in this patch set.
Agreed, we can keep that for later. My main concern for this review
was the other point above anyway.
Thank you,
Quentin
Powered by blists - more mailing lists