From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Max Kellermann <max@duempel.org>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH 1/4] check nfct_get_attr()!=NULL
Date: Mon, 21 Jan 2008 14:07:24 +0100 [thread overview]
Message-ID: <4794990C.5050505@netfilter.org> (raw)
In-Reply-To: <20080121125824.GA29741@swift.blarg.de>
Max Kellermann wrote:
> On 2008/01/21 13:53, Pablo Neira Ayuso <pablo@netfilter.org> wrote:
>> Max Kellermann wrote:
>>> from time to time, conntrackd segfaults in cache.c, function hash(),
>>> because it does not check the return value of nfct_get_attr(). For
>>> some reason (which I have not investigated), there is no
>>> ATTR_ORIG_IPV4_SRC. A gdb dump of *ct after the segfault says the
>>> following:
>> I cannot reproduce this problem in my testbed. Are you running
>> conntrackd with IPv6 connections?
>
> This machine uses IPv6 and IPv6 CT. I have no idea what conntrackd
> does with these.
I started IPv6 support months ago but it's still incomplete. This is
probably the reason of this crash. We can fix the IPv6 code or
preventively disable it until we finish it.
--
"Los honestos son inadaptados sociales" -- Les Luthiers
prev parent reply other threads:[~2008-01-21 13:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-21 8:29 [PATCH 0/4] fix SEGV, some run.c API stuff Max Kellermann
2008-01-21 8:29 ` [PATCH 2/4] don't ignore fd events when an alarm is due Max Kellermann
2008-01-21 13:14 ` Pablo Neira Ayuso
2008-01-21 14:09 ` Max Kellermann
2008-01-22 1:29 ` Pablo Neira Ayuso
2008-01-21 8:29 ` [PATCH 3/4] __run() returns void Max Kellermann
2008-01-21 13:22 ` Pablo Neira Ayuso
2008-01-22 1:29 ` Pablo Neira Ayuso
2008-01-21 8:29 ` [PATCH 4/4] call __run() after do_alarm_run() Max Kellermann
2008-01-22 1:30 ` Pablo Neira Ayuso
2008-01-21 8:29 ` [PATCH 1/4] check nfct_get_attr()!=NULL Max Kellermann
2008-01-21 12:53 ` Pablo Neira Ayuso
2008-01-21 12:58 ` Max Kellermann
2008-01-21 13:07 ` Pablo Neira Ayuso [this message]
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=4794990C.5050505@netfilter.org \
--to=pablo@netfilter.org \
--cc=max@duempel.org \
--cc=netfilter-devel@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.