All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pablo Neira <pablo@eurodev.net>
To: Amin Azez <azez@ufomechanic.net>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: [PATCH] Fix wrong order in event notification
Date: Sat, 10 Sep 2005 18:06:16 +0200	[thread overview]
Message-ID: <43230478.7030701@eurodev.net> (raw)
In-Reply-To: <4321B575.4040009@ufomechanic.net>

Hi Sam,

Amin Azez wrote:
> I want to "backport" this patch to 2.6.11.7 (before IPS_DYING was
> invented to help shrink the conntrack struct)
> 
> The obvious fixup is below, I just wanted to check that it was safe, and
> that sending the event earlier instead of during death by timeout wasn't
> also depending on side effects of IPS_DYING

ctnetlink is already in the Linus tree, so it will be out in the next
kernel release. Because of that, I don't think that it's worth applying
that patch to the event API in pom-ng. We should focus on what is in
mainline.

--
Pablo

      reply	other threads:[~2005-09-10 16:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-05  0:38 [PATCH] Fix wrong order in event notification Pablo Neira
2005-08-05 12:28 ` Harald Welte
2005-09-09 16:16 ` Amin Azez
2005-09-10 16:06   ` Pablo Neira [this message]

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=43230478.7030701@eurodev.net \
    --to=pablo@eurodev.net \
    --cc=azez@ufomechanic.net \
    --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.