From: Jakub Sitnicki <jakub@cloudflare.com>
To: Martin KaFai Lau <kafai@fb.com>
Cc: bpf@vger.kernel.org, netdev@vger.kernel.org,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
kernel-team@cloudflare.com, Ilya Leoshkevich <iii@linux.ibm.com>
Subject: Re: [PATCH bpf-next v2 3/3] selftests/bpf: Fix test for 4-byte load from dst_port on big-endian
Date: Thu, 03 Mar 2022 18:12:02 +0100 [thread overview]
Message-ID: <874k4fhre3.fsf@cloudflare.com> (raw)
In-Reply-To: <20220301062207.d3aqge5qg623asr6@kafai-mbp.dhcp.thefacebook.com>
On Mon, Feb 28, 2022 at 10:22 PM -08, Martin KaFai Lau wrote:
> On Sun, Feb 27, 2022 at 09:27:57PM +0100, Jakub Sitnicki wrote:
[...]
>> --- a/tools/testing/selftests/bpf/progs/test_sock_fields.c
>> +++ b/tools/testing/selftests/bpf/progs/test_sock_fields.c
>> @@ -256,10 +256,23 @@ int ingress_read_sock_fields(struct __sk_buff *skb)
>> return CG_OK;
>> }
>>
>> +/*
>> + * NOTE: 4-byte load from bpf_sock at dst_port offset is quirky. The
>> + * result is left shifted on little-endian architectures because the
>> + * access is converted to a 2-byte load. The quirky behavior is kept
>> + * for backward compatibility.
>> + */
>> static __noinline bool sk_dst_port__load_word(struct bpf_sock *sk)
>> {
>> +#if __BYTE_ORDER__ == __ORDER_LITTLE_ENDIAN__
>> + const __u8 SHIFT = 16;
>> +#elif __BYTE_ORDER__ == __ORDER_BIG_ENDIAN__
>> + const __u8 SHIFT = 0;
>> +#else
>> +#error "Unrecognized __BYTE_ORDER__"
>> +#endif
>> __u32 *word = (__u32 *)&sk->dst_port;
>> - return word[0] == bpf_htonl(0xcafe0000);
>> + return word[0] == bpf_htonl(0xcafe << SHIFT);
> I believe it should be fine. It is the behavior even before
> commit 4421a582718a ("bpf: Make dst_port field in struct bpf_sock 16-bit wide") ?
Yes, exactly. AFAICT there was no change in behavior in commit
4421a582718a, that is:
1. 4-byte load behaves like it did, in its quirky way,
2. 2-byte load at offset dst_port works the same
3. 2-byte load at offset dst_port+2 continues to be rejected.
> btw, is it the same as testing "return word[0] == bpf_hton's'(0xcafe);"
Right. Clever observation. I got the impression from the original
problem report [1] that the users were failing when trying to do:
bpf_htonl(sk->dst_port) == 0xcafe
Hence I the bpf_htonl() use here.
But perhaps it's better to promote this cleaner pattern in tests.
I will respin it once we hash out the details of what the access should
look like on big-endian with Ilya.
[1] https://lore.kernel.org/bpf/20220113070245.791577-1-imagedong@tencent.com/
[...]
prev parent reply other threads:[~2022-03-03 17:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-27 20:27 [PATCH bpf-next v2 0/3] Fixes for sock_fields selftests Jakub Sitnicki
2022-02-27 20:27 ` [PATCH bpf-next v2 1/3] selftests/bpf: Fix error reporting from sock_fields programs Jakub Sitnicki
2022-02-27 20:27 ` [PATCH bpf-next v2 2/3] selftests/bpf: Check dst_port only on the client socket Jakub Sitnicki
2022-03-01 6:25 ` Martin KaFai Lau
2022-03-03 17:34 ` Jakub Sitnicki
2022-02-27 20:27 ` [PATCH bpf-next v2 3/3] selftests/bpf: Fix test for 4-byte load from dst_port on big-endian Jakub Sitnicki
2022-03-01 6:22 ` Martin KaFai Lau
2022-03-03 17:12 ` Jakub Sitnicki [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=874k4fhre3.fsf@cloudflare.com \
--to=jakub@cloudflare.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=iii@linux.ibm.com \
--cc=kafai@fb.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).