History

bpf: move BPF_F_QUERY_EFFECTIVE after map flags

BPF_F_QUERY_EFFECTIVE is in the middle of the flags valid for BPF_MAP_CREATE. Move it to its own section to reduce confusion.

Lorenz Bauer committed 8 years ago

Commit 2f183361 parent 96b3b6c1 file · +3 −3Browse files

Showing the changes to include/uapi/linux (1 of 1 file). Show all

Unified · Split

include/uapi/linux/bpf.h+3−3
@@ -257,9 +257,6 @@ enum bpf_attach_type { · 256 unmodified lines
257257 /* Specify numa node during map creation */
258258 #define BPF_F_NUMA_NODE (1U << 2)
259259
260−/* flags for BPF_PROG_QUERY */
261−#define BPF_F_QUERY_EFFECTIVE (1U << 0)
262−
263260 #define BPF_OBJ_NAME_LEN 16U
264261
265262 /* Flags for accessing BPF object */
@@ -272,6 +269,9 @@ enum bpf_attach_type { · 6 unmodified lines
272269 /* Zero-initialize hash function seed. This should only be used for testing. */
273270 #define BPF_F_ZERO_SEED (1U << 6)
274271
272+/* flags for BPF_PROG_QUERY */
273+#define BPF_F_QUERY_EFFECTIVE (1U << 0)
274+
275275 enum bpf_stack_build_id_status {
276276 /* user space need an empty entry to identify end of a trace */
277277 BPF_STACK_BUILD_ID_EMPTY = 0,

Keyboard shortcuts

General

Show keyboard shortcuts
?
Focus the current search
/

Issues and pull requests

Open filters
f

Issues, pull requests and Inbox

Select next item
j↓
Select previous item
k↑
Open selected item
Enter
Dismiss filters or clear selection
Esc

Repository code

Go to file
t