From: patchwork-bot+netdevbpf@kernel.org
To: Kumar Kartikeya Dwivedi <memxor@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, yhs@fb.com
Subject: Re: [PATCH bpf-next v3 0/2] Ensure type tags are always ordered first in BTF
Date: Wed, 20 Apr 2022 01:00:11 +0000 [thread overview]
Message-ID: <165041641191.4464.2434468387244993266.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220419164608.1990559-1-memxor@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Tue, 19 Apr 2022 22:16:06 +0530 you wrote:
> When iterating over modifiers, ensure that type tags can only occur at head of
> the chain, and don't occur later, such that checking for them once in the start
> tells us there are no more type tags in later modifiers. Clang already ensures
> to emit such BTF, but user can craft their own BTF which violates such
> assumptions if relied upon in the kernel.
>
> Changelog:
>
> [...]
Here is the summary with links:
- [bpf-next,v3,1/2] bpf: Ensure type tags precede modifiers in BTF
https://git.kernel.org/bpf/bpf-next/c/eb596b090558
- [bpf-next,v3,2/2] selftests/bpf: Add tests for type tag order validation
https://git.kernel.org/bpf/bpf-next/c/24fe983abe01
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:[~2022-04-20 1:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-19 16:46 [PATCH bpf-next v3 0/2] Ensure type tags are always ordered first in BTF Kumar Kartikeya Dwivedi
2022-04-19 16:46 ` [PATCH bpf-next v3 1/2] bpf: Ensure type tags precede modifiers " Kumar Kartikeya Dwivedi
2022-04-19 16:46 ` [PATCH bpf-next v3 2/2] selftests/bpf: Add tests for type tag order validation Kumar Kartikeya Dwivedi
2022-04-20 1:00 ` 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=165041641191.4464.2434468387244993266.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=memxor@gmail.com \
--cc=yhs@fb.com \
/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