All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phil Oester <kernel@linuxace.com>
To: borg@uu3.net
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: ipt_limit patch for iptables-1.3.1 and linux-2.4.22
Date: Fri, 23 Dec 2005 12:19:51 -0800	[thread overview]
Message-ID: <20051223201951.GA28723@linuxace.com> (raw)
In-Reply-To: <036110574.20051223211301@uu3.net>

On Fri, Dec 23, 2005 at 09:13:01PM +0100, borg@uu3.net wrote:
> Well.. patching only kernel or only userland is pointless indeed.
> I still dont understand "brakes userspace"
> I assume that we patch both iptables + kernel.

new kernel + old userspace = broken
old kernel + new userspace = broken

> Where is the problem then?

comprehension

Phil

  reply	other threads:[~2005-12-23 20:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-23 13:12 ipt_limit patch for iptables-1.3.1 and linux-2.4.22 borg
2005-12-23 13:40 ` m.innocenti
2005-12-23 15:43   ` Re[2]: " borg
2005-12-23 19:26     ` Patrick McHardy
2005-12-23 20:13       ` Re[2]: " borg
2005-12-23 20:19         ` Phil Oester [this message]
2005-12-23 20:35           ` borg
2005-12-23 20:57             ` Phil Oester
2005-12-27  9:21               ` m.innocenti
2005-12-24  6:27             ` Patrick Schaaf

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=20051223201951.GA28723@linuxace.com \
    --to=kernel@linuxace.com \
    --cc=borg@uu3.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.