From: patchwork-bot+netdevbpf@kernel.org
To: Stanislav Fomichev <sdf@google.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, martin.lau@linux.dev, song@kernel.org,
yhs@fb.com, john.fastabend@gmail.com, kpsingh@kernel.org,
haoluo@google.com, jolsa@kernel.org
Subject: Re: [PATCH bpf-next v2 1/2] bpf: clarify error expectations from bpf_clone_redirect
Date: Mon, 11 Sep 2023 20:40:29 +0000 [thread overview]
Message-ID: <169446482902.4154.9987772850452271859.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230911194731.286342-1-sdf@google.com>
Hello:
This series was applied to bpf/bpf.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Mon, 11 Sep 2023 12:47:30 -0700 you wrote:
> Commit 151e887d8ff9 ("veth: Fixing transmit return status for dropped
> packets") exposed the fact that bpf_clone_redirect is capable of
> returning raw NET_XMIT_XXX return codes.
>
> This is in the conflict with its UAPI doc which says the following:
> "0 on success, or a negative error in case of failure."
>
> [...]
Here is the summary with links:
- [bpf-next,v2,1/2] bpf: clarify error expectations from bpf_clone_redirect
https://git.kernel.org/bpf/bpf/c/7cb779a6867f
- [bpf-next,v2,2/2] selftests/bpf: update bpf_clone_redirect expected return code
https://git.kernel.org/bpf/bpf/c/b772b70b6904
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-09-11 20:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-11 19:47 [PATCH bpf-next v2 1/2] bpf: clarify error expectations from bpf_clone_redirect Stanislav Fomichev
2023-09-11 19:47 ` [PATCH bpf-next v2 2/2] selftests/bpf: update bpf_clone_redirect expected return code Stanislav Fomichev
2023-09-11 20: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=169446482902.4154.9987772850452271859.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=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=martin.lau@linux.dev \
--cc=sdf@google.com \
--cc=song@kernel.org \
--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 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.