All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yonghong Song <yonghong.song@linux.dev>
To: bot+bpf-ci@kernel.org, bpf@vger.kernel.org
Cc: ast@kernel.org, andrii@kernel.org, daniel@iogearbox.net,
	eddyz87@gmail.com, kernel-team@fb.com, martin.lau@kernel.org,
	mason@kernel.org, ihor.solodrai@linux.dev
Subject: Re: [PATCH bpf-next v3 14/20] libbpf: Add cleanup_info to bpf_prog_load_opts
Date: Mon, 21 Sep 2026 08:00:35 -0700	[thread overview]
Message-ID: <58c6111a-dd36-4b59-85d6-6ab2576219b8@linux.dev> (raw)
In-Reply-To: <16900372d8d1bf2968c1cc9d6d16790243368ac169064fb9cdd6e90264e63bf9@mail.kernel.org>



On 9/19/26 11:31 PM, bot+bpf-ci@kernel.org wrote:
>> Let a caller hand the kernel an exception cleanup table. Extend struct
>> bpf_prog_load_opts with cleanup_info, cleanup_info_cnt and
>> cleanup_info_rec_size, pass them through to BPF_PROG_LOAD, and grow the
>> attr size bpf_prog_load() computes to cover the new fields.
>> Signed-off-by: Yonghong Song <yonghong.song@linux.dev>
> This isn't a bug, but would it help a future reader if the changelog
> noted that cleanup_info_cnt is the last field of the BPF_PROG_LOAD attr
> struct, so offsetofend() on it covers all three new fields, rather than
> restating the three edits?

Okay, will explicit mention cleanup_info_cnt is the last field.

>
> ---
> AI reviewed your patch. Please fix the bug or email reply why it's not a bug.
> See: https://github.com/kernel-patches/vmtest/blob/master/ci/claude/README.md
>
> CI run summary: https://github.com/kernel-patches/bpf/actions/runs/35492765538


  reply	other threads:[~2026-09-21 15:00 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-20  5:42 [PATCH bpf-next v3 00/20] bpf: Run exception cleanup landing pads when bpf_throw() unwinds Yonghong Song
2026-09-20  5:42 ` [PATCH bpf-next v3 01/20] bpf: Accept the compiler's exception cleanup table at program load Yonghong Song
2026-09-20  5:56   ` sashiko-bot
2026-09-21 15:43     ` Yonghong Song
2026-09-20  6:32   ` bot+bpf-ci
2026-09-21 15:28     ` Yonghong Song
2026-09-20  5:42 ` [PATCH bpf-next v3 02/20] bpf: Add the bpf_unwind_resume() kfunc Yonghong Song
2026-09-20  5:42 ` [PATCH bpf-next v3 03/20] bpf: Add lookups for exception cleanup resumes and landing pads Yonghong Song
2026-09-20  6:31   ` bot+bpf-ci
2026-09-21 14:06     ` Yonghong Song
2026-09-20  5:42 ` [PATCH bpf-next v3 04/20] bpf: Prepare for an exception cleanup table before the CFG walk Yonghong Song
2026-09-20  5:42 ` [PATCH bpf-next v3 05/20] bpf: Make exception landing pads reachable in the CFG Yonghong Song
2026-09-20  5:42 ` [PATCH bpf-next v3 06/20] bpf: Explore the landing pads no call site reaches Yonghong Song
2026-09-20  5:43 ` [PATCH bpf-next v3 07/20] bpf: Refuse exception cleanup shapes bpf_throw() cannot dispatch Yonghong Song
2026-09-20  6:32   ` bot+bpf-ci
2026-09-21 14:08     ` Yonghong Song
2026-09-20  5:43 ` [PATCH bpf-next v3 08/20] bpf: Walk the exception unwind in the verifier Yonghong Song
2026-09-20  5:43 ` [PATCH bpf-next v3 09/20] bpf: Refuse a private stack for a program with an exception cleanup table Yonghong Song
2026-09-20  5:43 ` [PATCH bpf-next v3 10/20] bpf: Dispatch exception cleanup pads from bpf_throw() Yonghong Song
2026-09-20  6:32   ` bot+bpf-ci
2026-09-21 15:55     ` Yonghong Song
2026-09-20  5:43 ` [PATCH bpf-next v3 11/20] bpf, x86: Dispatch exception cleanup pads at run time Yonghong Song
2026-09-20  5:43 ` [PATCH bpf-next v3 12/20] bpf, arm64: " Yonghong Song
2026-09-20  5:43 ` [PATCH bpf-next v3 13/20] libbpf: Resolve the compiler's _Unwind_Resume to the kernel's kfunc Yonghong Song
2026-09-20  5:43 ` [PATCH bpf-next v3 14/20] libbpf: Add cleanup_info to bpf_prog_load_opts Yonghong Song
2026-09-20  6:31   ` bot+bpf-ci
2026-09-21 15:00     ` Yonghong Song [this message]
2026-09-20  5:43 ` [PATCH bpf-next v3 15/20] libbpf: Collect .bpf_cleanup records and pass them to the kernel Yonghong Song
2026-09-20  5:43 ` [PATCH bpf-next v3 16/20] libbpf: Carry the exception cleanup table through the light skeleton Yonghong Song
2026-09-20  6:01   ` sashiko-bot
2026-09-21 14:14     ` Yonghong Song
2026-09-20  5:43 ` [PATCH bpf-next v3 17/20] libbpf: Let the static linker carry .bpf_cleanup relocations Yonghong Song
2026-09-20  6:00   ` sashiko-bot
2026-09-21 14:20     ` Yonghong Song
2026-09-20  6:31   ` bot+bpf-ci
2026-09-21 14:21     ` Yonghong Song
2026-09-20  5:43 ` [PATCH bpf-next v3 18/20] selftests/bpf: Add an end-to-end .bpf_cleanup exception test Yonghong Song
2026-09-20  5:59   ` sashiko-bot
2026-09-20  5:44 ` [PATCH bpf-next v3 19/20] selftests/bpf: Cover the exception cleanup shapes the chain does not reach Yonghong Song
2026-09-20  6:01   ` sashiko-bot
2026-09-20  6:46   ` bot+bpf-ci
2026-09-21 14:27     ` Yonghong Song
2026-09-20  5:44 ` [PATCH bpf-next v3 20/20] selftests/bpf: Load an exception cleanup program from a light skeleton Yonghong Song
2026-09-20  6:31   ` bot+bpf-ci
2026-09-21 14:30     ` Yonghong Song

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=58c6111a-dd36-4b59-85d6-6ab2576219b8@linux.dev \
    --to=yonghong.song@linux.dev \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bot+bpf-ci@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=ihor.solodrai@linux.dev \
    --cc=kernel-team@fb.com \
    --cc=martin.lau@kernel.org \
    --cc=mason@kernel.org \
    /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.