Re: [PATCH bpf] libbpf: fix passing uninitialized bytes to setsockopt

2019-10-13 Thread Ilya Maximets
On 13.10.2019 6:59, Alexei Starovoitov wrote: On Sat, Oct 12, 2019 at 9:52 PM Ilya Maximets wrote: 'struct xdp_umem_reg' has 4 bytes of padding at the end that makes valgrind complain about passing uninitialized stack memory to the syscall: Syscall param socketcall.setsockopt() points to u

Re: [PATCH bpf] libbpf: fix passing uninitialized bytes to setsockopt

2019-10-12 Thread Alexei Starovoitov
On Sat, Oct 12, 2019 at 9:52 PM Ilya Maximets wrote: > > 'struct xdp_umem_reg' has 4 bytes of padding at the end that makes > valgrind complain about passing uninitialized stack memory to the > syscall: > > Syscall param socketcall.setsockopt() points to uninitialised byte(s) > at 0x4E7AB7E:

Re: [PATCH bpf] libbpf: fix passing uninitialized bytes to setsockopt

2019-10-09 Thread Ilya Maximets
On 09.10.2019 18:29, Andrii Nakryiko wrote: On Wed, Oct 9, 2019 at 8:43 AM Ilya Maximets wrote: 'struct xdp_umem_reg' has 4 bytes of padding at the end that makes valgrind complain about passing uninitialized stack memory to the syscall: Syscall param socketcall.setsockopt() points to unin

Re: [PATCH bpf] libbpf: fix passing uninitialized bytes to setsockopt

2019-10-09 Thread Andrii Nakryiko
On Wed, Oct 9, 2019 at 8:43 AM Ilya Maximets wrote: > > 'struct xdp_umem_reg' has 4 bytes of padding at the end that makes > valgrind complain about passing uninitialized stack memory to the > syscall: > > Syscall param socketcall.setsockopt() points to uninitialised byte(s) > at 0x4E7AB7E: