From: patchwork-bot+netdevbpf@kernel.org
To: Matteo Croce <mcroce@linux.microsoft.com>
Cc: alexei.starovoitov@gmail.com, bpf@vger.kernel.org,
daniel@iogearbox.net, andrii@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next v3 0/2] limit bpf_core_types_are_compat recursion
Date: Fri, 04 Feb 2022 19:40:08 +0000 [thread overview]
Message-ID: <164400360849.5213.7518261706290398971.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220204005519.60361-1-mcroce@linux.microsoft.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Fri, 4 Feb 2022 01:55:17 +0100 you wrote:
> From: Matteo Croce <mcroce@microsoft.com>
>
> As formerly discussed on the BPF mailing list:
> https://lore.kernel.org/bpf/CAADnVQJDax2j0-7uyqdqFEnpB57om_z+Cqmi1O2QyLpHqkVKwA@mail.gmail.com/
>
> changes from v2:
> test the bpf_core_type_exists() return value, and check that the recursion
> limit is enforced.
>
> [...]
Here is the summary with links:
- [bpf-next,v3,1/2] bpf: limit bpf_core_types_are_compat() recursion
https://git.kernel.org/bpf/bpf-next/c/e70e13e7d4ab
- [bpf-next,v3,2/2] selftests/bpf: test maximum recursion depth for bpf_core_types_are_compat()
https://git.kernel.org/bpf/bpf-next/c/976a38e05a49
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-02-04 19:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 0:55 [PATCH bpf-next v3 0/2] limit bpf_core_types_are_compat recursion Matteo Croce
2022-02-04 0:55 ` [PATCH bpf-next v3 1/2] bpf: limit bpf_core_types_are_compat() recursion Matteo Croce
2022-02-04 19:32 ` Alexei Starovoitov
2022-02-04 0:55 ` [PATCH bpf-next v3 2/2] selftests/bpf: test maximum recursion depth for bpf_core_types_are_compat() Matteo Croce
2022-02-04 19:37 ` Alexei Starovoitov
2022-02-06 22:27 ` Matteo Croce
2022-02-04 19:40 ` 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=164400360849.5213.7518261706290398971.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mcroce@linux.microsoft.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