From: Patrick McHardy <kaber@trash.net>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: [PATCH] Fix NAT TCP sequence adjustment
Date: Tue, 31 May 2005 16:35:21 +0200 [thread overview]
Message-ID: <429C7629.4010602@trash.net> (raw)
In-Reply-To: <1117547304.7878.42.camel@localhost.localdomain>
Rusty Russell wrote:
> On Tue, 2005-05-31 at 15:02 +0200, Patrick McHardy wrote:
>
>> Second of all, I spent like 10 hours to verify the
>>proposed fixes, and I am still convinced that it is correct.
>
> Which shows exactly *why* we have a testsuite. Dammit, I didn't spend
> all those hours on it for fun.
>
> You spent *10* hours, and the testsuite runs in 5 seconds (60 seconds
> counting build time the first time).
I don't get your point - I know why we have a testsuite. You're
complaining that I had more important things to do than add tests to a
testsuite that didn't even run on my system until perhaps 4 hours ago,
after spending considerable time fixing the fallout from your patches?
In any case, without identifying the problems, you can't test for them.
It looks like your tests won't even trigger the original problem, let
alone the problem case I identified in Phil's proposed patch. So if I
had relied on it, we would now have an incorrect fix. And no, the 10
hours won't be wasted, as I already said before, I'll add proper tests
when nfsim runs on my system and I have time.
> <sigh>
Sigh indeed.
> I fixed the testsuite, so now when I get bored I can come up with a
> patch which removes those horrible hooks you added (sure, I may have to
> rewrite everything to do it).
Feel free to do so. Its not hard to replace them, the alternative just
felt a bit unsafe for -rc3.
prev parent reply other threads:[~2005-05-31 14:35 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-02 20:24 [PATCH] Fix NAT TCP sequence adjustment Phil Oester
2005-04-03 12:26 ` Milos Wimmer
2005-04-03 19:26 ` Patrick McHardy
2005-04-03 23:53 ` Phil Oester
2005-04-04 4:40 ` Phil Oester
2005-04-04 8:27 ` Patrick McHardy
2005-04-04 20:47 ` Phil Oester
2005-04-05 7:32 ` Patrick McHardy
2005-04-05 13:33 ` Patch lifetime " Amin Azez
2005-04-10 20:49 ` Harald Welte
2005-04-06 4:48 ` Phil Oester
2005-04-18 1:42 ` Patrick McHardy
2005-04-19 0:58 ` Phil Oester
2005-04-20 15:03 ` Patrick McHardy
2005-04-20 15:53 ` Phil Oester
2005-04-20 16:07 ` Patrick McHardy
2005-04-20 17:24 ` Phil Oester
2005-04-20 17:50 ` Patrick McHardy
2005-04-20 18:25 ` Phil Oester
2005-04-20 21:39 ` Martijn Lievaart
2005-04-21 1:41 ` Patrick McHardy
2005-04-21 1:38 ` Patrick McHardy
2005-04-21 12:31 ` Milos Wimmer
2005-04-21 12:32 ` Patrick McHardy
2005-04-21 13:31 ` Jonas Berlin
2005-04-21 23:01 ` Patrick McHardy
2005-04-27 0:44 ` Rusty Russell
2005-04-27 10:27 ` Patrick McHardy
2005-05-31 9:17 ` Rusty Russell
2005-05-31 13:02 ` Patrick McHardy
2005-05-31 13:48 ` Rusty Russell
2005-05-31 14:35 ` Patrick McHardy [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=429C7629.4010602@trash.net \
--to=kaber@trash.net \
--cc=netfilter-devel@lists.netfilter.org \
--cc=rusty@rustcorp.com.au \
/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.