From: patchwork-bot+netdevbpf@kernel.org
To: Andrii Nakryiko <andrii@kernel.org>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
martin.lau@kernel.org, kernel-team@meta.com
Subject: Re: [PATCH v3 bpf-next 0/8] BPF verifier log improvements
Date: Sat, 18 Nov 2023 19:50:30 +0000 [thread overview]
Message-ID: <170033703014.19891.11451927195007871211.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231118034623.3320920-1-andrii@kernel.org>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Fri, 17 Nov 2023 19:46:15 -0800 you wrote:
> This patch set moves a big chunk of verifier log related code from gigantic
> verifier.c file into more focused kernel/bpf/log.c. This is not essential to
> the rest of functionality in this patch set, so I can undo it, but it felt
> like it's good to start chipping away from 20K+ verifier.c whenever we can.
>
> The main purpose of the patch set, though, is in improving verifier log
> further.
>
> [...]
Here is the summary with links:
- [v3,bpf-next,1/8] bpf: move verbose_linfo() into kernel/bpf/log.c
https://git.kernel.org/bpf/bpf-next/c/db840d389bad
- [v3,bpf-next,2/8] bpf: move verifier state printing code to kernel/bpf/log.c
https://git.kernel.org/bpf/bpf-next/c/42feb6620acc
- [v3,bpf-next,3/8] bpf: extract register state printing
https://git.kernel.org/bpf/bpf-next/c/009f5465be36
- [v3,bpf-next,4/8] bpf: print spilled register state in stack slot
https://git.kernel.org/bpf/bpf-next/c/67d43dfbb42d
- [v3,bpf-next,5/8] bpf: emit map name in register state if applicable and available
https://git.kernel.org/bpf/bpf-next/c/0c95c9fdb696
- [v3,bpf-next,6/8] bpf: omit default off=0 and imm=0 in register state log
https://git.kernel.org/bpf/bpf-next/c/1db747d75b1d
- [v3,bpf-next,7/8] bpf: smarter verifier log number printing logic
https://git.kernel.org/bpf/bpf-next/c/0f8dbdbc641b
- [v3,bpf-next,8/8] bpf: emit frameno for PTR_TO_STACK regs if it differs from current one
https://git.kernel.org/bpf/bpf-next/c/46862ee854b4
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-11-18 19:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-18 3:46 [PATCH v3 bpf-next 0/8] BPF verifier log improvements Andrii Nakryiko
2023-11-18 3:46 ` [PATCH v3 bpf-next 1/8] bpf: move verbose_linfo() into kernel/bpf/log.c Andrii Nakryiko
2023-11-18 3:46 ` [PATCH v3 bpf-next 2/8] bpf: move verifier state printing code to kernel/bpf/log.c Andrii Nakryiko
2023-11-18 3:46 ` [PATCH v3 bpf-next 3/8] bpf: extract register state printing Andrii Nakryiko
2023-11-18 3:46 ` [PATCH v3 bpf-next 4/8] bpf: print spilled register state in stack slot Andrii Nakryiko
2023-11-18 3:46 ` [PATCH v3 bpf-next 5/8] bpf: emit map name in register state if applicable and available Andrii Nakryiko
2023-11-18 3:46 ` [PATCH v3 bpf-next 6/8] bpf: omit default off=0 and imm=0 in register state log Andrii Nakryiko
2023-11-18 3:46 ` [PATCH v3 bpf-next 7/8] bpf: smarter verifier log number printing logic Andrii Nakryiko
2023-11-18 3:46 ` [PATCH v3 bpf-next 8/8] bpf: emit frameno for PTR_TO_STACK regs if it differs from current one Andrii Nakryiko
2023-11-18 19:50 ` patchwork-bot+netdevbpf [this message]
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=170033703014.19891.11451927195007871211.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kernel-team@meta.com \
--cc=martin.lau@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox