[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAADnVQ+6xhGRj=SRPXTx9XoNHaJ4Uut0DCQ4=wLa7G8b9j4_ow@mail.gmail.com>
Date: Tue, 3 Mar 2020 16:42:34 -0800
From: Alexei Starovoitov <alexei.starovoitov@...il.com>
To: Andrii Nakryiko <andriin@...com>
Cc: bpf <bpf@...r.kernel.org>,
Network Development <netdev@...r.kernel.org>,
Alexei Starovoitov <ast@...com>,
Daniel Borkmann <daniel@...earbox.net>,
Andrii Nakryiko <andrii.nakryiko@...il.com>,
Kernel Team <kernel-team@...com>
Subject: Re: [PATCH bpf-next] libbpf: fix handling of optional field_name in btf_dump__emit_type_decl
On Tue, Mar 3, 2020 at 10:13 AM Andrii Nakryiko <andriin@...com> wrote:
>
> Internal functions, used by btf_dump__emit_type_decl(), assume field_name is
> never going to be NULL. Ensure it's always the case.
>
> Fixes: 9f81654eebe8 ("libbpf: Expose BTF-to-C type declaration emitting API")
> Signed-off-by: Andrii Nakryiko <andriin@...com>
Applied. Thanks
Powered by blists - more mailing lists