public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: "David S. Miller" <davem@redhat.com>
Cc: kuznet@ms2.inr.ac.ru, linux-kernel@vger.kernel.org
Subject: Re: Fragment flooding in 2.4.x/2.5.x
Date: 05 Aug 2002 16:00:25 +0200	[thread overview]
Message-ID: <shs7kj576di.fsf@charged.uio.no> (raw)
In-Reply-To: <15694.33047.965504.346909@charged.uio.no>

>>>>> " " == Trond Myklebust <trond.myklebust@fys.uio.no> writes:

     > Concerning the 2.4.x kernel: it would be very nice if this fix
     > made it into 2.4.19, as the bug has already been known to crash
     > a few servers...

Bump the above request to read '...made it into 2.4.20...'. I replied
before I saw Marcelo's announcement.

Cheers,
  Trond

  reply	other threads:[~2002-08-05 13:56 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-27 15:57 Fragment flooding in 2.4.x/2.5.x Trond Myklebust
2002-06-27 16:34 ` kuznet
2002-06-27 17:00   ` Trond Myklebust
2002-06-27 20:05     ` kuznet
2002-06-27 20:45       ` Trond Myklebust
2002-06-27 22:07         ` kuznet
2002-06-28  8:22           ` Trond Myklebust
2002-06-28 10:38             ` Trond Myklebust
2002-06-28 18:21               ` Alexey Kuznetsov
2002-07-01 12:14                 ` Trond Myklebust
2002-08-03 10:17                   ` David S. Miller
2002-08-05 13:43                     ` Trond Myklebust
2002-08-05 14:00                       ` Trond Myklebust [this message]
2002-08-05 14:54                       ` David S. Miller
2002-08-05 23:30                       ` kuznet
2002-08-05 23:45                         ` Trond Myklebust
2002-08-06  7:53                           ` Henning P. Schmiedehausen
2002-08-06  4:43                         ` David S. Miller

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=shs7kj576di.fsf@charged.uio.no \
    --to=trond.myklebust@fys.uio.no \
    --cc=davem@redhat.com \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox