All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Olsa <olsajiri@gmail.com>
To: Alan Maguire <alan.maguire@oracle.com>
Cc: ast@kernel.org, andrii@kernel.org, eddyz87@gmail.com,
	qmo@kernel.org, daniel@iogearbox.net, ihor.solodrai@linux.dev,
	yonghong.song@linux.dev, song@kernel.org, martin.lau@linux.dev,
	memxor@gmail.com, emil@etsalapatis.com, bpf@vger.kernel.org,
	nsc@kernel.org, puranjay@kernel.org, yatsenko@meta.com
Subject: Re: [PATCH v3 bpf-next 0/3] BTF inline functionality followups
Date: Mon, 28 Sep 2026 11:39:31 +0200	[thread overview]
Message-ID: <aro109AFzQhPyC7B@krava> (raw)
In-Reply-To: <20260926175113.2368566-1-alan.maguire@oracle.com>

On Sat, Sep 26, 2026 at 06:51:10PM +0100, Alan Maguire wrote:
> Include additional vlen/flags verification for BTF_KIND_LOC_PARAM
> (patch 1), and add function signatures to LOCSEC entries (patch 2),
> adjusting test to cover these (patch 3).
> 
> Changes since v2 [1]
> 
> - Improved flag/vlen verification to check combinations (Alexei,
>   patch 1)
> - Simplified overrun ellipsis printing (Quentin, patch 2)

Acked-by: Jiri Olsa <jolsa@kernel.org>

jirka

> 
> Changes since v1 [2]
> 
> - Fixed sign to appear after const (bots, patch 2)
> - Simplified loc printing to remove vsnprintf() logic, updated
>   to retain name in json (Quentin, patch 2)
> - For oversized signature strings, append "..." (Quentin, patch 2)
> 
> [1] https://lore.kernel.org/bpf/20260925170854.1240637-1-alan.maguire@oracle.com/
> [2] https://lore.kernel.org/bpf/20260925095231.879708-1-alan.maguire@oracle.com/
> 
> Alan Maguire (3):
>   bpf: Verify BTF_KIND_LOC_PARAM vlen, flags
>   bpftool: Update func representation to include function signature
>   selftests/bpf: Fix up bpftool btf dump test for signatures
> 
>  kernel/bpf/btf.c                              |  43 ++++++
>  tools/bpf/bpftool/btf.c                       | 123 ++++++++++++++++--
>  .../bpf/prog_tests/bpftool_btf_dump.c         |  14 +-
>  3 files changed, 165 insertions(+), 15 deletions(-)
> 
> -- 
> 2.43.5
> 

  parent reply	other threads:[~2026-09-28  9:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-26 17:51 [PATCH v3 bpf-next 0/3] BTF inline functionality followups Alan Maguire
2026-09-26 17:51 ` [PATCH v3 bpf-next 1/3] bpf: Verify BTF_KIND_LOC_PARAM vlen, flags Alan Maguire
2026-09-29 10:43   ` Alexei Starovoitov
2026-09-29 10:50     ` Alan Maguire
2026-09-26 17:51 ` [PATCH v3 bpf-next 2/3] bpftool: Update func representation to include function signature Alan Maguire
2026-09-28  9:39   ` Jiri Olsa
2026-09-28  9:50     ` Alan Maguire
2026-09-28 11:46   ` Quentin Monnet
2026-09-26 17:51 ` [PATCH v3 bpf-next 3/3] selftests/bpf: Fix up bpftool btf dump test for signatures Alan Maguire
2026-09-28  9:39 ` Jiri Olsa [this message]
2026-09-28 11:46   ` [PATCH v3 bpf-next 0/3] BTF inline functionality followups Quentin Monnet
2026-09-29 10:50 ` patchwork-bot+netdevbpf

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=aro109AFzQhPyC7B@krava \
    --to=olsajiri@gmail.com \
    --cc=alan.maguire@oracle.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=emil@etsalapatis.com \
    --cc=ihor.solodrai@linux.dev \
    --cc=martin.lau@linux.dev \
    --cc=memxor@gmail.com \
    --cc=nsc@kernel.org \
    --cc=puranjay@kernel.org \
    --cc=qmo@kernel.org \
    --cc=song@kernel.org \
    --cc=yatsenko@meta.com \
    --cc=yonghong.song@linux.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.