From: Yonghong Song <yhs@fb.com>
To: Jakub Sitnicki <jakub@cloudflare.com>, <bpf@vger.kernel.org>
Cc: <netdev@vger.kernel.org>, Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>, <kernel-team@cloudflare.com>
Subject: Re: [PATCH bpf-next 2/2] selftests/bpf: Cover 4-byte load from remote_port in bpf_sk_lookup
Date: Mon, 7 Feb 2022 11:20:30 -0800 [thread overview]
Message-ID: <36895526-cffc-c445-be54-e15481bdd3ec@fb.com> (raw)
In-Reply-To: <20220207131459.504292-3-jakub@cloudflare.com>
On 2/7/22 5:14 AM, Jakub Sitnicki wrote:
> Extend the context access tests for sk_lookup prog to cover the surprising
> case of a 4-byte load from the remote_port field, where the expected value
> is actually shifted by 16 bits.
>
> Signed-off-by: Jakub Sitnicki <jakub@cloudflare.com>
Acked-by: Yonghong Song <yhs@fb.com>
prev parent reply other threads:[~2022-02-07 19:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 13:14 [PATCH bpf-next 0/2] Split bpf_sk_lookup remote_port field Jakub Sitnicki
2022-02-07 13:14 ` [PATCH bpf-next 1/2] bpf: Make remote_port field in struct bpf_sk_lookup 16-bit wide Jakub Sitnicki
2022-02-07 19:14 ` Yonghong Song
2022-02-07 22:04 ` kernel test robot
2022-02-07 22:04 ` kernel test robot
2022-02-08 19:28 ` Alexei Starovoitov
2022-02-08 19:28 ` Alexei Starovoitov
2022-02-08 20:42 ` Jakub Sitnicki
2022-02-08 20:42 ` Jakub Sitnicki
2022-02-08 20:58 ` Alexei Starovoitov
2022-02-08 20:58 ` Alexei Starovoitov
2022-02-07 13:14 ` [PATCH bpf-next 2/2] selftests/bpf: Cover 4-byte load from remote_port in bpf_sk_lookup Jakub Sitnicki
2022-02-07 19:20 ` Yonghong Song [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=36895526-cffc-c445-be54-e15481bdd3ec@fb.com \
--to=yhs@fb.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=jakub@cloudflare.com \
--cc=kernel-team@cloudflare.com \
--cc=netdev@vger.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 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.