Add the necessary header definitions to tools for new msg_pop_data_helper.
Showing the changes to tools/include/uapi (1 of 2 files). Show all
Unified · Split
| @@ -2268,6 +2268,19 @@ union bpf_attr { · 2267 unmodified lines | ||
| 2268 | 2268 | * |
| 2269 | 2269 | * Return |
| 2270 | 2270 | * 0 on success, or a negative error in case of failure. |
| 2271 | + * | |
| 2272 | + * int bpf_msg_pop_data(struct sk_msg_buff *msg, u32 start, u32 pop, u64 flags) | |
| 2273 | + * Description | |
| 2274 | + * Will remove *pop* bytes from a *msg* starting at byte *start*. | |
| 2275 | + * This may result in **ENOMEM** errors under certain situations if | |
| 2276 | + * an allocation and copy are required due to a full ring buffer. | |
| 2277 | + * However, the helper will try to avoid doing the allocation | |
| 2278 | + * if possible. Other errors can occur if input parameters are | |
| 2279 | + * invalid either due to *start* byte not being valid part of msg | |
| 2280 | + * payload and/or *pop* value being to large. | |
| 2281 | + * | |
| 2282 | + * Return | |
| 2283 | + * 0 on success, or a negative erro in case of failure. | |
| 2271 | 2284 | */ |
| 2272 | 2285 | #define __BPF_FUNC_MAPPER(FN) \ |
| 2273 | 2286 | FN(unspec), \ |
| @@ -2360,7 +2373,8 @@ union bpf_attr { · 86 unmodified lines | ||
| 2360 | 2373 | FN(map_push_elem), \ |
| 2361 | 2374 | FN(map_pop_elem), \ |
| 2362 | 2375 | FN(map_peek_elem), \ |
| 2363 | − FN(msg_push_data), | |
| 2376 | + FN(msg_push_data), \ | |
| 2377 | + FN(msg_pop_data), | |
| 2364 | 2378 | |
| 2365 | 2379 | /* integer value in 'imm' field of BPF_CALL instruction selects which helper |
| 2366 | 2380 | * function eBPF program intends to call |