From: Harald Welte <laforge@gnumonks.org>
To: Stelian Pop <stelian.pop@fr.alcove.com>
Cc: linux-kernel@vger.kernel.org, netfilter-devel@lists.samba.org,
hpa@zytor.com
Subject: Re: [SOLUTION] Re: Fw: 2.4.18-pre9: iptables screwed?
Date: Fri, 8 Feb 2002 11:30:14 +0100 [thread overview]
Message-ID: <20020208113014.Q26676@sunbeam.de.gnumonks.org> (raw)
In-Reply-To: <20020208.010839.112626203.davem@redhat.com> <20020208105548.P26676@sunbeam.de.gnumonks.org> <20020208101218.GD12130@come.alcove-fr>
In-Reply-To: <20020208101218.GD12130@come.alcove-fr>; from stelian.pop@fr.alcove.com on Fri, Feb 08, 2002 at 11:12:18AM +0100
On Fri, Feb 08, 2002 at 11:12:18AM +0100, Stelian Pop wrote:
> > The code you are quoting is only defined if debugging is compiled into
> > the iptables package. The default distribution of the iptables package
> > does _not_ ship with debugging enabled.
>
> Right, upon further analysis the redhat RPM is overriding COPT_FLAGS
> and removes the -DNDEBUG from the compile line.
hm. bad coincidence :(
> > We always want to make sure that nobody needs to update the iptables
> > package during the 2.4.x stable kernel series. Because of this (sane)
> > policy, we are keeping back a whole bunch of changes. We can't just
> > silently abandon backwards compatibility.
>
> Hey, you keeped backwards compatibility _only_ for those compiling
> the non debug version of the package. I believe this remains however
> a half-bug...
Well, it is a bug in the debugging code, yes. We missed to updated the
debugging code when changing the mangle table. The reason for this is
that not even the developers are using the debugging code.
But when I do compatibility checks / tests for something I want to submit to
the kernel, I use plain unmodified iptables sources - new and old.
And I really didn't expect anybody to run debugging code on production
systems, sorry.
I'm not going to pull this change back out of the kernel because
one (or more) distributors/vendors ship a compiled-with-debug iptables.
I don't think this was by RedHat's intention.
> Stelian.
> Stelian Pop <stelian.pop@fr.alcove.com>
--
Live long and prosper
- Harald Welte / laforge@gnumonks.org http://www.gnumonks.org/
============================================================================
GCS/E/IT d- s-: a-- C+++ UL++++$ P+++ L++++$ E--- W- N++ o? K- w--- O- M+
V-- PS++ PE-- Y++ PGP++ t+ 5-- !X !R tv-- b+++ !DI !D G+ e* h--- r++ y+(*)
next prev parent reply other threads:[~2002-02-08 10:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020208.010839.112626203.davem@redhat.com>
2002-02-08 9:55 ` Harald Welte
2002-02-08 10:12 ` Stelian Pop
2002-02-08 10:30 ` Harald Welte [this message]
2002-02-08 10:50 ` Stelian Pop
2002-02-11 18:11 ` Bill Davidsen
2002-02-12 7:36 ` Harald Welte
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=20020208113014.Q26676@sunbeam.de.gnumonks.org \
--to=laforge@gnumonks.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netfilter-devel@lists.samba.org \
--cc=stelian.pop@fr.alcove.com \
/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®