Files
kernel/include/uapi/linux
Jakub Sitnicki 4421a58271 bpf: Make dst_port field in struct bpf_sock 16-bit wide
Menglong Dong reports that the documentation for the dst_port field in
struct bpf_sock is inaccurate and confusing. From the BPF program PoV, the
field is a zero-padded 16-bit integer in network byte order. The value
appears to the BPF user as if laid out in memory as so:

  offsetof(struct bpf_sock, dst_port) + 0  <port MSB>
                                      + 8  <port LSB>
                                      +16  0x00
                                      +24  0x00

32-, 16-, and 8-bit wide loads from the field are all allowed, but only if
the offset into the field is 0.

32-bit wide loads from dst_port are especially confusing. The loaded value,
after converting to host byte order with bpf_ntohl(dst_port), contains the
port number in the upper 16-bits.

Remove the confusion by splitting the field into two 16-bit fields. For
backward compatibility, allow 32-bit wide loads from offsetof(struct
bpf_sock, dst_port).

While at it, allow loads 8-bit loads at offset [0] and [1] from dst_port.

Reported-by: Menglong Dong <imagedong@tencent.com>
Signed-off-by: Jakub Sitnicki <jakub@cloudflare.com>
Link: https://lore.kernel.org/r/20220130115518.213259-2-jakub@cloudflare.com
Signed-off-by: Alexei Starovoitov <ast@kernel.org>
2022-01-31 12:39:12 -08:00
..
2021-09-14 08:46:08 +02:00
2021-01-25 18:44:44 +01:00
2020-12-28 14:21:31 +00:00
2021-11-01 13:36:08 +00:00
2021-10-29 12:38:43 +02:00
2021-11-26 16:48:59 +01:00
2021-08-10 13:32:40 -04:00
2021-10-07 13:51:11 +02:00
2021-02-08 13:01:24 +01:00
2021-10-06 12:05:51 +00:00
2021-11-15 07:53:10 -08:00
2021-06-03 15:31:34 -07:00
2021-12-02 12:07:04 +00:00
2021-02-26 09:41:03 -08:00
2021-05-21 15:03:50 +02:00
2021-03-10 09:34:06 +01:00
2021-10-26 14:58:45 +01:00
2021-10-14 23:06:28 +02:00
2021-07-06 10:37:46 -05:00
2021-10-18 17:20:50 +02:00
2021-03-10 09:34:06 +01:00
2021-01-07 16:17:32 +01:00
2021-09-16 14:36:26 +01:00
2021-06-12 13:16:45 -07:00