From: Pablo Neira Ayuso <pablo@netfilter.org>
To: "Salih Gönüllü" <sag@open.ch>
Cc: netfilter@vger.kernel.org
Subject: Re: ulogd2 segfault
Date: Thu, 06 Jan 2011 14:53:09 +0100 [thread overview]
Message-ID: <4D25C945.7030502@netfilter.org> (raw)
In-Reply-To: <4D221173.3060009@open.ch>
On 03/01/11 19:12, Salih Gönüllü wrote:
> Hi,
>
> my last ulogd.conf was not complete. And I think I found out the cause:
>
> stack=log2:NFLOG,base1:BASE,ifi1:IFINDEX,ip2str1:IP2STR,print1:PRINTPKT,emu0:LOGEMU
>
> stack=log2:NFLOG,base1:BASE,ifi1:IFINDEX,ip2str1:IP2STR,print1:PRINTPKT,syslog1:SYSLOG
>
> having other stacks is not a problem as long as the log2:NFLOG is not
> present, could it be that stop_pluginstances() in this case is doing a
> double free() ?
Let me check this, if the problem is what you're pointing (which makes
sense at first look at the code) I guess that we need some refcounting
for plugins to avoid double freeing.
next prev parent reply other threads:[~2011-01-06 13:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-31 16:23 ulogd2 segfault Salih Gönüllü
2011-01-03 18:12 ` Salih Gönüllü
2011-01-06 13:53 ` Pablo Neira Ayuso [this message]
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=4D25C945.7030502@netfilter.org \
--to=pablo@netfilter.org \
--cc=netfilter@vger.kernel.org \
--cc=sag@open.ch \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox