diff mbox series

[bpf-next,v2,1/5] libbpf: add new strict flag for .text subprograms

Message ID b107f56787c89464ab52828b885e1a208312d20b.1646957399.git.delyank@fb.com (mailing list archive)
State Superseded
Delegated to: BPF
Headers show
Series Subskeleton support for BPF libraries | expand

Checks

Context Check Description
netdev/tree_selection success Clearly marked for bpf-next
netdev/fixes_present success Fixes tag not required for -next series
netdev/subject_prefix success Link
netdev/cover_letter success Series has a cover letter
netdev/patch_count success Link
netdev/header_inline success No static functions without inline keyword in header files
netdev/build_32bit success Errors and warnings before: 0 this patch: 0
netdev/cc_maintainers warning 6 maintainers not CCed: kpsingh@kernel.org john.fastabend@gmail.com kafai@fb.com songliubraving@fb.com yhs@fb.com netdev@vger.kernel.org
netdev/build_clang success Errors and warnings before: 0 this patch: 0
netdev/module_param success Was 0 now: 0
netdev/verify_signedoff success Signed-off-by tag matches author and committer
netdev/verify_fixes success No Fixes tag
netdev/build_allmodconfig_warn success Errors and warnings before: 0 this patch: 0
netdev/checkpatch success total: 0 errors, 0 warnings, 0 checks, 26 lines checked
netdev/kdoc success Errors and warnings before: 0 this patch: 0
netdev/source_inline success Was 0 now: 0
bpf/vmtest-bpf-next-PR success PR summary
bpf/vmtest-bpf-next success VM_Test

Commit Message

Delyan Kratunov March 11, 2022, 12:11 a.m. UTC
Currently, libbpf considers a single routine in .text as a program. This
is particularly confusing when it comes to library objects - a single routine
meant to be used as an extern will instead be considered a bpf_program.

This patch hides this compatibility behavior behind a libbpf_mode strict
mode flag.

Signed-off-by: Delyan Kratunov <delyank@fb.com>
---
 tools/lib/bpf/libbpf.c        | 7 +++++++
 tools/lib/bpf/libbpf_legacy.h | 6 ++++++
 2 files changed, 13 insertions(+)

Comments

Andrii Nakryiko March 11, 2022, 10:30 p.m. UTC | #1
On Thu, Mar 10, 2022 at 4:12 PM Delyan Kratunov <delyank@fb.com> wrote:
>
> Currently, libbpf considers a single routine in .text as a program. This
> is particularly confusing when it comes to library objects - a single routine
> meant to be used as an extern will instead be considered a bpf_program.
>
> This patch hides this compatibility behavior behind a libbpf_mode strict
> mode flag.
>
> Signed-off-by: Delyan Kratunov <delyank@fb.com>
> ---
>  tools/lib/bpf/libbpf.c        | 7 +++++++
>  tools/lib/bpf/libbpf_legacy.h | 6 ++++++
>  2 files changed, 13 insertions(+)
>
> diff --git a/tools/lib/bpf/libbpf.c b/tools/lib/bpf/libbpf.c
> index 43161fdd44bb..b6f11ce0d6bc 100644
> --- a/tools/lib/bpf/libbpf.c
> +++ b/tools/lib/bpf/libbpf.c
> @@ -3832,7 +3832,14 @@ static bool prog_is_subprog(const struct bpf_object *obj,
>          * .text programs are subprograms (even if they are not called from
>          * other programs), because libbpf never explicitly supported mixing
>          * SEC()-designated BPF programs and .text entry-point BPF programs.
> +        *
> +        * In libbpf 1.0 strict mode, we always consider .text
> +        * programs to be subprograms.
>          */
> +
> +       if (libbpf_mode & LIBBPF_STRICT_TEXT_ONLY_SUBPROGRAMS)
> +               return prog->sec_idx == obj->efile.text_shndx;
> +
>         return prog->sec_idx == obj->efile.text_shndx && obj->nr_programs > 1;
>  }
>
> diff --git a/tools/lib/bpf/libbpf_legacy.h b/tools/lib/bpf/libbpf_legacy.h
> index a283cf031665..388384ea97a7 100644
> --- a/tools/lib/bpf/libbpf_legacy.h
> +++ b/tools/lib/bpf/libbpf_legacy.h
> @@ -78,6 +78,12 @@ enum libbpf_strict_mode {
>          * in favor of BTF-defined map definitions in SEC(".maps").
>          */
>         LIBBPF_STRICT_MAP_DEFINITIONS = 0x20,
> +       /*
> +        * When enabled, always consider routines in the .text section to
> +        * be sub-programs. Previously, single routines in the .text section
> +        * would be considered a program on their own.
> +        */
> +       LIBBPF_STRICT_TEXT_ONLY_SUBPROGRAMS = 0x40,

We have LIBBPF_STRICT_SEC_NAME, we can probably just rely on that one.
STRICT_SEC_NAME means (among other things) that there has to be
SEC("abc"), so there can't be BPF program in .text section. We don't
enforce that yet, but that's a separate thing.

>
>         __LIBBPF_STRICT_LAST,
>  };

> --
> 2.34.1
diff mbox series

Patch

diff --git a/tools/lib/bpf/libbpf.c b/tools/lib/bpf/libbpf.c
index 43161fdd44bb..b6f11ce0d6bc 100644
--- a/tools/lib/bpf/libbpf.c
+++ b/tools/lib/bpf/libbpf.c
@@ -3832,7 +3832,14 @@  static bool prog_is_subprog(const struct bpf_object *obj,
 	 * .text programs are subprograms (even if they are not called from
 	 * other programs), because libbpf never explicitly supported mixing
 	 * SEC()-designated BPF programs and .text entry-point BPF programs.
+	 *
+	 * In libbpf 1.0 strict mode, we always consider .text
+	 * programs to be subprograms.
 	 */
+
+	if (libbpf_mode & LIBBPF_STRICT_TEXT_ONLY_SUBPROGRAMS)
+		return prog->sec_idx == obj->efile.text_shndx;
+
 	return prog->sec_idx == obj->efile.text_shndx && obj->nr_programs > 1;
 }
 
diff --git a/tools/lib/bpf/libbpf_legacy.h b/tools/lib/bpf/libbpf_legacy.h
index a283cf031665..388384ea97a7 100644
--- a/tools/lib/bpf/libbpf_legacy.h
+++ b/tools/lib/bpf/libbpf_legacy.h
@@ -78,6 +78,12 @@  enum libbpf_strict_mode {
 	 * in favor of BTF-defined map definitions in SEC(".maps").
 	 */
 	LIBBPF_STRICT_MAP_DEFINITIONS = 0x20,
+	/*
+	 * When enabled, always consider routines in the .text section to
+	 * be sub-programs. Previously, single routines in the .text section
+	 * would be considered a program on their own.
+	 */
+	LIBBPF_STRICT_TEXT_ONLY_SUBPROGRAMS = 0x40,
 
 	__LIBBPF_STRICT_LAST,
 };