mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: mhaque@haque.net
Cc: kuznet@ms2.inr.ac.ru, tleete@mountain.net, laforge@gnumonks.org,
	rusty@linuxcare.com.au, netfilter-devel@us5.samba.org,
	linux-kernel@vger.kernel.org
Subject: Re: ip_defrag / ip_conntrack issues (was Re: [PATCH] Fix netfilter
Date: Tue, 19 Dec 2000 17:35:23 -0800	[thread overview]
Message-ID: <200012200135.RAA08489@pizda.ninka.net> (raw)
In-Reply-To: <3A400F2A.E5CD52BA@haque.net> (mhaque@haque.net)
In-Reply-To: <200012191454.RAA13529@ms2.inr.ac.ru> <3A400F2A.E5CD52BA@haque.net>

   Date: Tue, 19 Dec 2000 20:45:14 -0500
   From: "Mohammad A. Haque" <mhaque@haque.net>

   how is this meaningless?

   This just confirms what I and others have found in test12 wrt to the
   netfilter issue.

Alexey is talking about test12/netfilter + our ip_fragment.c fix,
not vanilla test12.

Later,
David S. Miller
davem@redhat.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-12-20  2:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E147qmG-0001yB-00@halfway>
     [not found] ` <200012181811.KAA05490@pizda.ninka.net>
2000-12-18 19:14   ` ip_defrag / ip_conntrack issues (was Re: [PATCH] Fix netfilter locking) Harald Welte
2000-12-19 13:55     ` Tom Leete
2000-12-19 14:12     ` David S. Miller
2000-12-19 14:54       ` ip_defrag / ip_conntrack issues (was Re: [PATCH] Fix netfilter kuznet
2000-12-20  1:35         ` David S. Miller [this message]
2000-12-20  2:47           ` Mohammad A. Haque
2000-12-20  1:45         ` Mohammad A. Haque
2000-12-20  5:59       ` ip_defrag / ip_conntrack issues (was Re: [PATCH] Fix netfilter locking) Tom Leete

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=200012200135.RAA08489@pizda.ninka.net \
    --to=davem@redhat.com \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=laforge@gnumonks.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhaque@haque.net \
    --cc=netfilter-devel@us5.samba.org \
    --cc=rusty@linuxcare.com.au \
    --cc=tleete@mountain.net \
    /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

all inboxes | Powered by JetHome®