diff options
| author | Daniel Borkmann <[email protected]> | 2019-07-15 23:15:53 +0200 |
|---|---|---|
| committer | Daniel Borkmann <[email protected]> | 2019-07-15 23:15:53 +0200 |
| commit | 6da193569cbe2127faa7a934a3c18fffe32c6041 (patch) | |
| tree | 19a9b4bec904d9838fbfdc8fa585632e0805da87 /include/uapi/linux | |
| parent | 81f522f96f788ba978f505d5a03a039f75360b8b (diff) | |
| parent | 073a4834a81368c8af9cc9e99ff83245600a8f6b (diff) | |
Merge branch 'bpf-fix-wide-loads-sockaddr'
Stanislav Fomichev says:
====================
When fixing selftests by adding support for wide stores, Yonghong
reported that he had seen some examples where clang generates
single u64 loads for two adjacent u32s as well:
http://lore.kernel.org/netdev/[email protected]
Fix this to support aligned u64 reads for some bpf_sock_addr fields
as well.
====================
Acked-by: Andrii Narkyiko <[email protected]>
Acked-by: Yonghong Song <[email protected]>
Signed-off-by: Daniel Borkmann <[email protected]>
Diffstat (limited to 'include/uapi/linux')
| -rw-r--r-- | include/uapi/linux/bpf.h | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/include/uapi/linux/bpf.h b/include/uapi/linux/bpf.h index 6f68438aa4ed..81be929b89fc 100644 --- a/include/uapi/linux/bpf.h +++ b/include/uapi/linux/bpf.h @@ -3248,7 +3248,7 @@ struct bpf_sock_addr { __u32 user_ip4; /* Allows 1,2,4-byte read and 4-byte write. * Stored in network byte order. */ - __u32 user_ip6[4]; /* Allows 1,2,4-byte read and 4,8-byte write. + __u32 user_ip6[4]; /* Allows 1,2,4,8-byte read and 4,8-byte write. * Stored in network byte order. */ __u32 user_port; /* Allows 4-byte read and write. @@ -3260,7 +3260,7 @@ struct bpf_sock_addr { __u32 msg_src_ip4; /* Allows 1,2,4-byte read and 4-byte write. * Stored in network byte order. */ - __u32 msg_src_ip6[4]; /* Allows 1,2,4-byte read and 4,8-byte write. + __u32 msg_src_ip6[4]; /* Allows 1,2,4,8-byte read and 4,8-byte write. * Stored in network byte order. */ __bpf_md_ptr(struct bpf_sock *, sk); |