From: patchwork-bot+netdevbpf@kernel.org
To: Eduard Zingerman <eddyz87@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, martin.lau@linux.dev, kernel-team@fb.com,
yhs@fb.com
Subject: Re: [PATCH bpf-next v2 0/3] bpf: allow ctx writes using BPF_ST_MEM instruction
Date: Sat, 04 Mar 2023 05:50:42 +0000 [thread overview]
Message-ID: <167790904214.20348.10430967873113079924.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230304011247.566040-1-eddyz87@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Sat, 4 Mar 2023 03:12:44 +0200 you wrote:
> Changes v1 -> v2, suggested by Alexei:
> - Resolved conflict with recent commit:
> 6fcd486b3a0a ("bpf: Refactor RCU enforcement in the verifier");
> - Variable `ctx_access` removed in function `convert_ctx_accesses()`;
> - Macro `BPF_COPY_STORE` renamed to `BPF_EMIT_STORE` and fixed to
> correctly extract original store instruction class from code.
>
> [...]
Here is the summary with links:
- [bpf-next,v2,1/3] bpf: allow ctx writes using BPF_ST_MEM instruction
https://git.kernel.org/bpf/bpf-next/c/0d80a619c113
- [bpf-next,v2,2/3] selftests/bpf: test if pointer type is tracked for BPF_ST_MEM
https://git.kernel.org/bpf/bpf-next/c/806f81cd1ee3
- [bpf-next,v2,3/3] selftests/bpf: Disassembler tests for verifier.c:convert_ctx_access()
https://git.kernel.org/bpf/bpf-next/c/71cf4d027ad5
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-03-04 5:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-04 1:12 [PATCH bpf-next v2 0/3] bpf: allow ctx writes using BPF_ST_MEM instruction Eduard Zingerman
2023-03-04 1:12 ` [PATCH bpf-next v2 1/3] " Eduard Zingerman
2023-03-04 1:12 ` [PATCH bpf-next v2 2/3] selftests/bpf: test if pointer type is tracked for BPF_ST_MEM Eduard Zingerman
2023-03-04 1:12 ` [PATCH bpf-next v2 3/3] selftests/bpf: Disassembler tests for verifier.c:convert_ctx_access() Eduard Zingerman
2023-03-04 5: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=167790904214.20348.10430967873113079924.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=eddyz87@gmail.com \
--cc=kernel-team@fb.com \
--cc=martin.lau@linux.dev \
--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