From: Pablo Neira <pablo@eurodev.net>
To: ferry@Hupie.com
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: [PATCH] Conntrack proc interface for tuple removal
Date: Fri, 13 May 2005 07:13:47 +0200 [thread overview]
Message-ID: <4284378B.8080401@eurodev.net> (raw)
In-Reply-To: <11148.217.169.232.210.1115923639.squirrel@hupie.xs4all.nl>
Ferry Huberts wrote:
> I badly needed to be able to remove conntrack tuple because of some very
> dynamic application behaviour, so I wrote a patch.
> Hope it lives up to your standards, I find it quite usefull :-)
>
> The patch is based on work from Yutaka Kondo.
>
> The patch is against 2.4.30 since that is the kernel I'm using, haven't
> looked into applying it against 2.6.x.y
You should do this with ctnetlink. It actually provides a more flexible
interface to user space applications: I mean, more actions like
creation, update, deletion, whatever... instead of doing this via /proc.
Have a look at the conntrack tool in netfilter SVN.
BTW, some comments about your patch:
- READ_LOCK'ing while trying to delete a conntrack is racy, you must use
write_lock instead. Someone else could be reading the conntrack table
while you try to delete a conntrack.
- check the value returned by del_timer, currently racy as well.
- Deadlock on SMP: calling conntrack->timeout.function
(death_by_timeout) is illegal if you've got ip_conntrack_lock.
--
Pablo
next prev parent reply other threads:[~2005-05-13 5:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-12 18:47 [PATCH] Conntrack proc interface for tuple removal Ferry Huberts
2005-05-13 5:13 ` Pablo Neira [this message]
2005-05-17 16:00 ` Amin Azez
2005-05-18 6:51 ` Jozsef Kadlecsik
2005-05-19 3:10 ` Pablo Neira
2005-05-17 16:00 ` Amin Azez
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=4284378B.8080401@eurodev.net \
--to=pablo@eurodev.net \
--cc=ferry@Hupie.com \
--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.