All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Patrick McHardy <kaber@trash.net>
Cc: Maciej Soltysiak <solt@dns.toxicfilms.tv>,
	Netfilter development mailing list
	<netfilter-devel@lists.netfilter.org>
Subject: Re: [PATCH] netfilter: ECN target corrupts packets (2.6 only)
Date: Mon, 03 Jan 2005 21:15:34 +1100	[thread overview]
Message-ID: <1104747334.14092.22.camel@localhost.localdomain> (raw)
In-Reply-To: <41D861F0.8000303@trash.net>

On Sun, 2005-01-02 at 22:04 +0100, Patrick McHardy wrote:
> There's more brokeness, it mangles the tcp header before making
> it writable and doesn't reload pointers after doing so. This patch
> should fix all of it and as a side-effect avoids some useless
> copying. Any voluteers for testing ? :)

I see more nfsim work coming up...

Thanks!
Rusty.
-- 
A bad analogy is like a leaky screwdriver -- Richard Braakman

      reply	other threads:[~2005-01-03 10:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-02 11:17 [PATCH] netfilter: ECN target corrupts packets (2.6 only) Rusty Russell
2005-01-02 15:07 ` Maciej Soltysiak
2005-01-02 21:04   ` Patrick McHardy
2005-01-03 10:15     ` Rusty Russell [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=1104747334.14092.22.camel@localhost.localdomain \
    --to=rusty@rustcorp.com.au \
    --cc=kaber@trash.net \
    --cc=netfilter-devel@lists.netfilter.org \
    --cc=solt@dns.toxicfilms.tv \
    /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.