From: Harald Welte <laforge@netfilter.org>
To: Patrick McHardy <kaber@trash.net>
Cc: Netfilter Development Mailinglist
<netfilter-devel@lists.netfilter.org>,
Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Subject: Re: [PATCH]: several small patches
Date: Tue, 17 Jun 2003 18:04:38 +0200 [thread overview]
Message-ID: <20030617160438.GE936@naboo> (raw)
In-Reply-To: <3EECBFF1.2070503@trash.net>
[-- Attachment #1: Type: text/plain, Size: 2248 bytes --]
On Sun, Jun 15, 2003 at 08:50:25PM +0200, Patrick McHardy wrote:
> Hi Harald,
> these are some patches that summed up, mostly one liners.
Thanks.
> 1. ip_conntrack-outdated-comment.diff:
> remove outdated comment in ip_conntrack_expect_related
> that seems to have it's origin in time before newnat. it also
> makes the initialization of new->use explicit.
fine with me.
> 2. ip-conntrack-unneeded-check.diff:
> remove double-check for ct->master, master_ct() also does the
> check.
ack.
> 3. ip-conntrack-unconfirmed-expect.diff:
> in init_conntrack: do not delete timer/call expect function for
> connections matching expectations from unconfirmed connections.
Again, correct.
> 4. unneeded-init.diff:
> this is an old patch which removes some memset(x,0,..) for
> data in bss segment. some more unneeded initializations since
> last post:
>
> - conntrack->tuplehash[IP_CT_DIR_ORIGINAL].list.next = NULL
> in init_conntrack() seems to be forgotten when IPS_CONFIRMED
> was introduced.
true.
> - memset and INIT_LIST_HEAD in ip_conntrack_expect_related()
> are not required, memory is overwritten in the next line anyway
> and list-member heads don't need to be initialized.
ok, that was my mistake... I somehow didn't notice the fact that only
the master list head needs to be initialized. But this is, obviously,
correct.
> 5. ip-conntrack-expect-drop-refcnt.diff:
> drop master conntrack refcnt before setting expectant = NULL in
> remove_expectations. untested but seems to make sense.
There have been recent changes in this part of code...
Jozsef: Any objections?
> 6. ip-conntrack-remove_expectations-list_for_each_safe.diff:
> use list_for_each_safe in remove_expectations
ok, a cosmetic correction.
I'll put 1-4 and 6 into patch-o-matic, 5 is Jozsef's call.
> Best regards,
> Patrick
--
- Harald Welte <laforge@netfilter.org> http://www.netfilter.org/
============================================================================
"Fragmentation is like classful addressing -- an interesting early
architectural error that shows how much experimentation was going
on while IP was being designed." -- Paul Vixie
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-06-17 16:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-15 18:50 [PATCH]: several small patches Patrick McHardy
2003-06-15 22:21 ` Patrick McHardy
2003-06-17 16:18 ` Harald Welte
2003-06-17 16:04 ` Harald Welte [this message]
2003-06-20 12:22 ` Jozsef Kadlecsik
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=20030617160438.GE936@naboo \
--to=laforge@netfilter.org \
--cc=kaber@trash.net \
--cc=kadlec@blackhole.kfki.hu \
--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.