[BPF] Fix a bug in BTF_KIND_TYPE_TAG generation
authorYonghong Song <yhs@fb.com>
Sun, 13 Feb 2022 00:56:17 +0000 (16:56 -0800)
committerYonghong Song <yhs@fb.com>
Tue, 15 Feb 2022 03:43:57 +0000 (19:43 -0800)
commitf419029fcdace7673c42ac01703eaaf36813356a
treef64f7a88cb5a2dfdd65f02d2589ca3359ecddc48
parent50713461d45eea2fd5521b665d213d72c796d7fc
[BPF] Fix a bug in BTF_KIND_TYPE_TAG generation

Kumar Kartikeya Dwivedi reported a bug ([1]) where BTF_KIND_TYPE_TAG types
are not generated.

Currently, BPF backend only generates BTF types which are used by
the program, e.g., global variables, functions and some builtin functions.
For example, suppose we have
  struct task_struct {
    ...
    struct task_group               *sched_task_group;
    struct mm_struct                *mm;
    ...
    pid_t                           pid;
    pid_t                           tgid;
    ...
  }
If BPF program intends to access task_struct->pid and task_struct->tgid,
there really no need to generate BTF types for struct task_group
and mm_struct.

In BPF backend, during BTF generation, when generating BTF for struct
task_struct, if types for task_group and mm_struct have not been generated
yet, a Fixup structure will be created, which will be reexamined later
to instantiate into either a full type or a forward type.

In current implementation, if we have something like
  struct foo {
     struct bar  __tag1    *f;
  };
and when generating types for struct foo, struct bar type
has not been generated, the __tag1 will be lost during later
Fixup instantiation. This patch fixed this issue by properly
handling btf_type_tag's during Fixup instantiation stage.

  [1] https://lore.kernel.org/bpf/20220210232411.pmhzj7v5uptqby7r@apollo.legion/

Differential Revision: https://reviews.llvm.org/D119799
llvm/lib/Target/BPF/BTFDebug.cpp
llvm/lib/Target/BPF/BTFDebug.h
llvm/test/CodeGen/BPF/BTF/type-tag-fixup-fwd.ll [new file with mode: 0644]
llvm/test/CodeGen/BPF/BTF/type-tag-fixup-resolved.ll [new file with mode: 0644]