All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Leblond <eric@inl.fr>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: [PATCH] Dump mark even if event is a DESTROY event
Date: Wed, 21 Feb 2007 14:13:04 +0100	[thread overview]
Message-ID: <1172063584.5413.18.camel@localhost.localdomain> (raw)
In-Reply-To: <45DC4052.2010305@netfilter.org>

[-- Attachment #1: Type: text/plain, Size: 948 bytes --]

Hi,

Le mercredi 21 février 2007 à 13:51 +0100, Pablo Neira Ayuso a écrit :
> Hi Eric,
> 
> I don't see why you may need the mark in the destroy message. You can 
> keep a cache in userspace with the connections that belong to a certain 
> subset and their marks, then if the mark changes, move such connection 
> the a different subset. It doesn't make sense to me the idea of 
> including the mark in the destroy message since such mark didn't change 
> with regards to the previous event delivered.

I do not agree with the idea of having a cache in userspace. It has been
coded in kernel and for this kind of stuff, once is enough. I really
want to avoid all synchronisation problems we could have to do this in
userspace.

Furthermore, mark exists to be able to create subset for other tools
like tc or ip.

BR,
-- 
Éric Leblond, eleblond@inl.fr
Téléphone : 01 44 89 46 39, Fax : 01 44 89 45 01
INL, http://www.inl.fr

[-- Attachment #2: Ceci est une partie de message numériquement signée --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2007-02-21 13:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-20  9:45 [PATCH] Dump mark even if event is a DESTROY event Eric Leblond
2007-02-21 12:51 ` Pablo Neira Ayuso
2007-02-21 13:13   ` Eric Leblond [this message]
2007-02-23 10:45     ` 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=1172063584.5413.18.camel@localhost.localdomain \
    --to=eric@inl.fr \
    --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.