Hello:
This patch was applied to bpf/bpf.git (refs/heads/master):
On Fri, 4 Dec 2020 15:20:01 -0800 you wrote:
> In case of having so many PID results that they don't fit into a singe page
> (4096) bytes, bpftool will erroneously conclude that it got corrupted data due
> to 4096 not being a multi
On 12/7/20 6:55 PM, Andrii Nakryiko wrote:
On Sat, Dec 5, 2020 at 11:11 AM Yonghong Song wrote:
On 12/4/20 3:20 PM, Andrii Nakryiko wrote:
In case of having so many PID results that they don't fit into a singe page
(4096) bytes, bpftool will erroneously conclude that it got corrupted dat
On Sat, Dec 5, 2020 at 11:11 AM Yonghong Song wrote:
>
>
>
> On 12/4/20 3:20 PM, Andrii Nakryiko wrote:
> > In case of having so many PID results that they don't fit into a singe page
> > (4096) bytes, bpftool will erroneously conclude that it got corrupted data
> > due
> > to 4096 not being a mu
On 12/4/20 3:20 PM, Andrii Nakryiko wrote:
In case of having so many PID results that they don't fit into a singe page
(4096) bytes, bpftool will erroneously conclude that it got corrupted data due
to 4096 not being a multiple of struct pid_iter_entry, so the last entry will
be partially trunc
In case of having so many PID results that they don't fit into a singe page
(4096) bytes, bpftool will erroneously conclude that it got corrupted data due
to 4096 not being a multiple of struct pid_iter_entry, so the last entry will
be partially truncated. Fix this by sizing the buffer to fit exact
