Hello:
This series was applied to bpf/bpf-next.git (master)
by Martin KaFai Lau <martin.lau@xxxxxxxxxx>:
On Tue, 30 Apr 2024 13:19:51 -0700 you wrote:
> ringbuf_process_ring() return int64_t, while ring__consume_n() assigns
> it to int. It's highly unlikely, but possible for ringbuf_process_ring()
> to return value larger than INT_MAX, so use int64_t. ring__consume_n()
> does check INT_MAX before returning int result to the user.
>
> Fixes: 4d22ea94ea33 ("libbpf: Add ring__consume_n / ring_buffer__consume_n")
> Signed-off-by: Andrii Nakryiko <andrii@xxxxxxxxxx>
>
> [...]
Here is the summary with links:
- [bpf-next,1/2] libbpf: fix potential overflow in ring__consume_n()
https://git.kernel.org/bpf/bpf-next/c/00f0e08f23fc
- [bpf-next,2/2] libbpf: fix ring_buffer__consume_n() return result logic
https://git.kernel.org/bpf/bpf-next/c/087d757fb473
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
