From: Yasuyuki Kozakai <yasuyuki.kozakai@toshiba.co.jp>
To: kisza@securityaudit.hu
Cc: netfilter-devel@lists.netfilter.org, laforge@netfilter.org,
usagi-core@linux-ipv6.org
Subject: Re: [PATCH]: 1st step to remove skb_linearize() in ip6_tables.c and optimization
Date: Thu, 24 Jun 2004 19:12:31 +0900 (JST) [thread overview]
Message-ID: <200406241012.TAA24555@toshiba.co.jp> (raw)
In-Reply-To: <1088064830.3104.21.camel@jds.i.dns-hungary.hu>
Hi, Andras,
From: Andras Kis-Szabo <kisza@securityaudit.hu>
Date: Thu, 24 Jun 2004 10:13:50 +0200
> Hi Yasuyuki,
>
> you saved my life :)
I'm glad.
> When I tried to do the same a was not able to track behaviour of
> skb->nh. (There was some grey point, like when the packet leaves the
> machine over the tunnel interface.)
Tunnel interfaces reset nh.raw to new address of network protocol header.
Otherwide kernel can be down in many parts of IPv6 stack.
BTW, if I remember correctly, you also tryed to rewrite match modules which
find extension headers. Have you already finished ? If so, you'll save my life,
too :)
> > - In all match module, the only arguments of match() are changed.
> I think it is not a problem since the ip6tables - as I know - not a
> 'core' product. We can break the compatibility / usability of these
> extensions. (And it will push us to fix the problems and sync the
> matches with the IPv4 parts.)
> Could you add an #error string right after the definitions in the
> matches?
>
> In this case the compilation of the matches will cause strange error
> messages - and someone have to answer all of them. An error message
> should help a little bit. (Eg.: Known error point. This part is under
> reconstruction. Please, be patient. etc.)
my patch doesn't remove skb_linearize() and I'll keep it until all IPv6
modules in main kernel has changed. and if match module uses old API,
compilation errors are occurred and user can notice and report that.
Then I think adding #error string to match module is not needed.
But I'm reminded by you that target modules doesn't cause compiling error.
OK, I try to solve this problem... But how same problem was managed when
removing skb_linearize() from "ip_tables.c" ? Maybe the order of arguments
of target() were changed ?
Anyone knows about that ?
-----------------------------------------------------------------
Yasuyuki KOZAKAI @ USAGI Project <yasuyuki.kozakai@toshiba.co.jp>
next prev parent reply other threads:[~2004-06-24 10:12 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-24 4:04 [PATCH]: 1st step to remove skb_linearize() in ip6_tables.c and optimization Yasuyuki Kozakai
2004-06-24 8:13 ` Andras Kis-Szabo
2004-06-24 10:12 ` Yasuyuki Kozakai [this message]
2004-06-24 10:24 ` Jozsef Kadlecsik
2004-06-24 10:35 ` Yasuyuki Kozakai
2004-06-24 11:26 ` Patrick McHardy
2004-06-24 11:50 ` Jozsef Kadlecsik
2004-06-24 13:04 ` Yasuyuki Kozakai
2004-06-24 13:25 ` Jozsef Kadlecsik
2004-06-24 13:48 ` (usagi-core 18584) " YOSHIFUJI Hideaki / 吉藤英明
2004-06-24 15:06 ` Yasuyuki Kozakai
2004-06-24 16:50 ` Patrick McHardy
2004-06-25 4:57 ` Yasuyuki Kozakai
2004-06-25 10:01 ` Jozsef Kadlecsik
2004-06-26 7:25 ` Yasuyuki Kozakai
2004-07-21 21:36 ` Harald Welte
2004-07-29 6:09 ` Yasuyuki Kozakai
2004-08-01 16:46 ` Harald Welte
2004-08-01 17:08 ` Patrick McHardy
2004-08-01 18:11 ` Harald Welte
2004-08-02 4:05 ` Yasuyuki Kozakai
2004-08-07 21:05 ` Yasuyuki Kozakai
2004-08-09 1:40 ` Yasuyuki Kozakai
2004-06-25 9:53 ` Harald Welte
2004-06-28 20:31 ` Patrick McHardy
2004-07-06 10:20 ` Patrick McHardy
2004-07-06 10:35 ` Harald Welte
2004-07-06 22:59 ` Pablo Neira
2004-07-06 23:33 ` Patrick McHardy
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=200406241012.TAA24555@toshiba.co.jp \
--to=yasuyuki.kozakai@toshiba.co.jp \
--cc=kisza@securityaudit.hu \
--cc=laforge@netfilter.org \
--cc=netfilter-devel@lists.netfilter.org \
--cc=usagi-core@linux-ipv6.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.