From: Patrick McHardy <kaber@trash.net>
To: Volker Poplawski <volker@openbios.org>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: libnl: Unmatched NL_ACT_DEL and NL_ACT_CHANGE
Date: Mon, 06 Jul 2009 13:29:40 +0200 [thread overview]
Message-ID: <4A51E024.8090402@trash.net> (raw)
In-Reply-To: <200907051144.51967.volker@openbios.org>
[-- Attachment #1: Type: text/plain, Size: 773 bytes --]
Volker Poplawski wrote:
> Hi all.
>
> Could s.o. please have a look at my (short) code at
> http://pastie.org/534637
>
> (maybe compile it with g++ -Wall test.c -o test -I ... -L ... -lnl -lnl-genl -
> lnl-nf -lnl-route)
>
> What the code does is to listen to changes in the ct-table using libnl. It
> keeps score of reported ctId in a lookup table.
>
> Problem is: I'm getting a lot of NL_ACT_CHANGE & NL_ACT_DEL without having
> seen a matching NL_ACT_NEW. (Also there seems to be no initial cache fill)
>
> kernel 2.6.27 (opensuse 11.1), libnl 2.0 (git master)
I think I know whats happening - the ct objects don't define the
attribute(s) distinguishing different entries, so cache_include()
doesn't recognize them as new.
Does this patch make any difference?
[-- Attachment #2: x --]
[-- Type: text/plain, Size: 347 bytes --]
diff --git a/lib/netfilter/ct_obj.c b/lib/netfilter/ct_obj.c
index ae14c0d..48a7abe 100644
--- a/lib/netfilter/ct_obj.c
+++ b/lib/netfilter/ct_obj.c
@@ -779,6 +779,7 @@ struct nl_object_ops ct_obj_ops = {
[NL_DUMP_STATS] = ct_dump_stats,
},
.oo_compare = ct_compare,
+ .oo_id_attrs = CT_ATTR_ID,
.oo_attrs2str = ct_attrs2str,
};
next prev parent reply other threads:[~2009-07-06 11:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-05 9:44 libnl: Unmatched NL_ACT_DEL and NL_ACT_CHANGE Volker Poplawski
2009-07-06 11:29 ` Patrick McHardy [this message]
2009-07-06 12:17 ` Volker Poplawski
2009-07-07 5:29 ` Philip Craig
2009-07-07 9:01 ` Volker Poplawski
2009-07-10 10:40 ` Patrick McHardy
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=4A51E024.8090402@trash.net \
--to=kaber@trash.net \
--cc=netfilter-devel@vger.kernel.org \
--cc=volker@openbios.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).