From: "Salih Gönüllü" <sag@open.ch>
To: netfilter@vger.kernel.org
Subject: ulogd2 segfault
Date: Fri, 31 Dec 2010 17:23:16 +0100 [thread overview]
Message-ID: <4D1E0374.3090008@open.ch> (raw)
Hi,
ulogd2 is segfaulting upon receipt of sigint or sigterm
Program received signal SIGTERM, Terminated.
0xb78c4430 in __kernel_vsyscall ()
(gdb) cont
Continuing.
Program received signal SIGSEGV, Segmentation fault.
0xb78b71ba in main_arena () from /lib/libc.so.6
(gdb) bt
#0 0xb78b71ba in main_arena () from /lib/libc.so.6
#1 0x0804a35d in ulogd_propagate_results ()
#2 0xb777256c in interp_packet (upi=0x80630f0, pf_family=2 '\002',
ldata=0xbff01390)
at ulogd_inppkt_NFLOG.c:400
#3 0xb7772149 in msg_cb (gh=0x8062f58, nfmsg=0xbff01470,
nfa=0xbff01390, data=0x805f270)
at ulogd_inppkt_NFLOG.c:472
#4 0xb78bf7d5 in __nflog_rcv_pkt () from /usr/lib/libnetfilter_log.so.1
#5 0xb7767b00 in nfnl_step () from /usr/lib/libnfnetlink.so.0
#6 0xbff013b0 in ?? ()
#7 0x08062f28 in ?? ()
#8 0x00000001 in ?? ()
#9 0xbff01474 in ?? ()
#10 0x00000000 in ?? ()
I have tried with beta4 and with git
4f652cc32aebeac20f46009f146ad973a1ed0e99
Is there a way to avoid this ?
#ulogd.conf
stack=log2:NFLOG,base1:BASE,ifi1:IFINDEX,ip2str1:IP2STR,print1:PRINTPKT,emu0:LOGEMU
[log2]
group=42
emu0]
file="/var/log/ulogd_sysemu.log"
Regards,
-salih
--
salih goenuellue
security engineer
open systems ag
raeffelstrasse 29
ch-8045 zurich
t +41 44 455 74 00
f +41 44 455 74 01
sag@open.ch
http://www.open.ch
next reply other threads:[~2010-12-31 16:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-31 16:23 Salih Gönüllü [this message]
2011-01-03 18:12 ` ulogd2 segfault Salih Gönüllü
2011-01-06 13:53 ` Pablo Neira Ayuso
2011-01-07 10:24 ` Salih Gönüllü
2011-01-07 13:37 ` Pablo Neira Ayuso
2011-01-07 16:40 ` Salih Gönüllü
2011-01-08 14:36 ` Pablo Neira Ayuso
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D1E0374.3090008@open.ch \
--to=sag@open.ch \
--cc=netfilter@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.