From: Pablo Neira <pablo@eurodev.net>
To: Deti Fliegl <deti@fliegl.de>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: problem with conntrack utility and kernel 2.6.14
Date: Fri, 28 Oct 2005 12:01:03 +0200 [thread overview]
Message-ID: <4361F6DF.3050106@eurodev.net> (raw)
In-Reply-To: <4361EAAB.1090206@fliegl.de>
Deti Fliegl wrote:
> Reading /proc/net/ip_conntrack seems to lock the table as long as being
> read which causes delays and loss in network traffic. Now I'm trying to
> use the conntrack utility from the subversion repository to list the
> conntrack table. This in turn prints out some "Unknown Attribute 5"
> lines and what's even worse it runs very often into a segmentation fault at
>
> recvmsg(3, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=00000008},
> msg_iov(1)=[{"\260\0\0\0\0\1\0\6\0\0\0\0\0\0\0\0\2\0\0\0004\0\2\200\24"...,
> 8192}], msg_controllen=0, msg_flags=0}, 0) = 176
> write(2, "nfnl_parse_attr: deficit (4) len"..., 39nfnl_parse_attr:
> deficit (4) len (0).
>
> ) = 39
This problem was already fixed days ago in libnetfilter_conntrack on Oct
17, see SVN. I'm not able to reproduce what you're reporting. Please
send me a gdb backtrace, together with other extra info. Are you running
conntrack on a x86?
> Maybe I'm wrong but it seems to happen due to a race condition when
> conntracking entries are being updated by the kernel... (if you like to
> reproduce this: just keep a high bandwidth connection open where byte
> counters in the conntrack tavle have to be updated very often...)
No, that doesn't make too much sense to me.
--
Pablo
next prev parent reply other threads:[~2005-10-28 10:01 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-28 9:08 problem with conntrack utility and kernel 2.6.14 Deti Fliegl
2005-10-28 9:26 ` Pablo Neira
2005-10-28 9:26 ` Deti Fliegl
2005-10-28 10:01 ` Pablo Neira [this message]
2005-10-28 11:48 ` Deti Fliegl
2005-10-28 19:22 ` Pablo Neira
2005-10-28 19:53 ` Deti Fliegl
2005-10-29 13:06 ` Pablo Neira
2005-10-29 15:34 ` Deti Fliegl
2005-10-29 18:35 ` Pablo Neira
2005-10-29 15:44 ` Deti Fliegl
2005-10-31 4:41 ` Pablo Neira
2005-10-31 8:28 ` Krzysztof Oledzki
2005-11-01 1:09 ` Pablo Neira
2005-11-01 10:29 ` Krzysztof Oledzki
2005-11-01 13:55 ` Pablo Neira
2005-11-01 15:17 ` Krzysztof Oledzki
2005-11-01 16:39 ` Pablo Neira
2005-11-01 18:49 ` Krzysztof Oledzki
2005-11-01 19:27 ` Pablo Neira
2005-11-01 19:39 ` Krzysztof Oledzki
2005-11-01 20:07 ` Pablo Neira
2005-11-01 20:21 ` Krzysztof Oledzki
2005-11-02 16:04 ` Pablo Neira
2005-10-31 11:10 ` Deti Fliegl
2005-12-04 2:14 ` Pablo Neira Ayuso
2005-12-04 16:09 ` Patrick McHardy
2005-12-04 16:53 ` Deti Fliegl
2005-12-04 17:10 ` Yasuyuki KOZAKAI
2005-12-04 18:44 ` Deti Fliegl
2005-12-04 19:56 ` Patrick McHardy
2005-12-05 5:51 ` Yasuyuki KOZAKAI
2005-12-15 12:49 ` problem with conntrack utility and kernel 2.6.14 - still with 2.6.14.4 Deti Fliegl
2005-12-15 13:05 ` Pablo Neira Ayuso
2005-12-15 17:21 ` Krzysztof Oledzki
[not found] ` <200512041004.37192.romary@nikoon.com>
2005-12-04 20:04 ` Major problem with conntrack utility and kernel 2.6.14.3 Patrick McHardy
2005-12-04 23:08 ` Deti Fliegl
2005-12-05 10:24 ` Krzysztof Oledzki
2005-12-05 15:17 ` Patrick McHardy
2005-10-28 13:39 ` problem with conntrack utility and kernel 2.6.14 Deti Fliegl
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=4361F6DF.3050106@eurodev.net \
--to=pablo@eurodev.net \
--cc=deti@fliegl.de \
--cc=netfilter-devel@lists.netfilter.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.