Hi Ivan, On Mon, Feb 03, 2014 at 10:54:23AM +0100, Ivan Homoliak wrote: > Uninitialized values in libnetfilter.log.c which were discovered by > valgrind and ulogd. > > Signed-off-by: Ivan Homoliak > --- > > Valgrinds output: > [...] > ==13821== Syscall param socketcall.sendto(msg) points to uninitialised byte(s) > ==13821== at 0x3E93AF6E83: __sendto_nocancel (in /usr/lib64/libc-2.17.so) > ==13821== by 0x5433E81: nfnl_send (libnfnetlink.c:391) > ==13821== by 0x5435C0E: nfnl_query (libnfnetlink.c:1569) > ==13821== by 0x522E9A0: nflog_set_mode (libnetfilter_log.c:481) > ==13821== by 0x5029FA2: start (ulogd_inppkt_NFLOG.c:581) > ==13821== by 0x403E5D: create_stack_start_instances (ulogd.c:918) > ==13821== by 0x4041B4: create_stack (ulogd.c:1010) > ==13821== by 0x4078D6: config_parse_file (conffile.c:225) > ==13821== by 0x404411: parse_conffile (ulogd.c:1088) > ==13821== by 0x405478: main (ulogd.c:1573) > ==13821== Address 0x7feffff9d is on thread 1's stack > ==13821== Uninitialised value was created by a stack allocation > ==13821== at 0x50293D0: ??? (in /usr/lib/ulogd/ulogd_inppkt_NFLOG.so) I found some time to looking into this. I think this patch for *libnfnetlink* should fix this for all the libraries. Better do this in a generic way so we skip similar reports in other libnetfilter_* libraries. Valgrind does not report any warning anymore here. If you can give a try to this libnfnetlink patch to confirm you see no more valgrind warnings, I'd appreciate. Thanks.