fix valgrind errors of uninitialised byte during call to nfq_unbind_pf
authorTamas Lengyel <tamas.k.lengyel@gmail.com>
Fri, 31 May 2013 12:20:57 +0000 (12:20 +0000)
committerr.kubiak <r.kubiak@samsung.com>
Mon, 16 Nov 2015 13:12:06 +0000 (14:12 +0100)
commit9ceeab6f658301427872e8d18c1b5af5c21d279a
treec14a4b6567f8a293a8fd1bda3c96c90beb057ae3
parent26b2ef901a4094a056b83d08f4145317066c8ec4
fix valgrind errors of uninitialised byte during call to nfq_unbind_pf

Valgrind generates error reports during a call
to the nfq_unbind_pf function:

==00:00:00:08.662 22111== 4 errors in context 1 of 1:
==00:00:00:08.662 22111== Syscall param socketcall.sendto(msg) points
to uninitialised byte(s)
...
==00:00:00:08.662 22111== Uninitialised value was created by a stack allocation
==00:00:00:08.662 22111== at 0x679C30B: __build_send_cfg_msg
(libnetfilter_queue.c:178

Signed-off-by: Tamas K Lengyel <tamas.k.lengyel@gmail.com>
Signed-off-by: Florian Westphal <fw@strlen.de>
src/libnetfilter_queue.c