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

2019-10-13 Thread Ilya Maximets
On 13.10.2019 1:24, Alexei Starovoitov wrote: On Wed, Oct 09, 2019 at 06:49:29PM +0200, 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() poi

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

2019-10-12 Thread Alexei Starovoitov
On Wed, Oct 09, 2019 at 06:49:29PM +0200, 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 0x

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

2019-10-09 Thread Alexei Starovoitov
On Wed, Oct 9, 2019 at 9:49 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:

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

2019-10-09 Thread Andrii Nakryiko
On Wed, Oct 9, 2019 at 9:49 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:

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

2019-10-09 Thread Ilya Maximets
'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: setsockopt (in /usr/lib64/libc-2.29.so) by 0x4BDE035: xsk_umem