All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: Netfilter Development Mailinglist <netfilter-devel@lists.netfilter.org>
Subject: Re: [PATCH 6/10][CTNETLINK] dump counters iif connection ended or counters filled up
Date: Mon, 10 Jul 2006 06:47:32 +0200	[thread overview]
Message-ID: <44B1DBE4.7010109@trash.net> (raw)
In-Reply-To: <44AE66CA.8030705@netfilter.org>

Pablo Neira Ayuso wrote:
> Patrick McHardy wrote:
> 
>> Pablo Neira Ayuso wrote:
>>
>>> I think that this patch should also reset counters upon fill up event,
>>> comments?
>>
>>
>> Not sure, do you know any users of the counters besides conntrackd?
> 
> 
> I don't know any ctnetlink user of the counters. Thinking it well this
> "counters fill up" issue is tricky. Since netlink is unreliable, what if
> the fill up event gets lost? we could reset counters and nobody would
> apparently notice. I think that we need an overflow bit in the conntrack
> that must be set whenever and overflow happens and unset such bit once
> the overflow event has been caught.


If a message is lost userspace simply _must_ resync if it wants
reliability. If we reset the counter its impossible for userspace
to reconstruct the value at which it overflowed, so I don't think
we should do that. But you raise a good point, how should userspace
react to lost DESTROY messages that contain new information (like
counter values)? I don't see how it could reliable handle that case.

  parent reply	other threads:[~2006-07-10  4:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-07  2:15 [PATCH 6/10][CTNETLINK] dump counters iif connection ended or counters filled up Pablo Neira Ayuso
2006-07-07  4:48 ` Patrick McHardy
2006-07-07  8:25   ` Amin Azez
2006-07-07 13:51   ` Pablo Neira Ayuso
2006-07-07 16:03     ` Amin Azez
2006-07-10  4:47     ` Patrick McHardy [this message]
2006-07-13 20:09       ` Pablo Neira Ayuso
2006-07-14  9:43         ` Patrick McHardy
2006-07-07  8:18 ` 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=44B1DBE4.7010109@trash.net \
    --to=kaber@trash.net \
    --cc=netfilter-devel@lists.netfilter.org \
    --cc=pablo@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.