[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20061206.234050.77634656.davem@davemloft.net>
Date: Wed, 06 Dec 2006 23:40:50 -0800 (PST)
From: David Miller <davem@...emloft.net>
To: kazunori@...azawa.org
Cc: miika@....fi, Diego.Beltrami@...t.fi, herbert@...dor.apana.org.au,
netdev@...r.kernel.org, usagi-core@...ux-ipv6.org
Subject: Re: [PATCH][IPSEC][4/7] inter address family ipsec tunnel
From: David Miller <davem@...emloft.net>
Date: Wed, 06 Dec 2006 23:37:49 -0800 (PST)
> From: Kazunori MIYAZAWA <kazunori@...azawa.org>
> Date: Wed, 6 Dec 2006 20:35:37 +0900
>
> > Sorry, I mixed up changes in the patches. I described that [4/7] will add
> > "IPv6 over IPv4 IPsec tunnel". However I send a patch for "IPv4 over IPv6"
> > as a reply because it includes the discussing item.
> > So this patch adds IPv4 over IPv6 IPsec tunnel. It's complicated.
> >
> > I deleted subustituting NULL for rt->peer and moved atomic_inc stuff
> > under the "if" section.
>
> I have applied this patch, thanks for fixing it up.
Actually, I have to revert this change again, it still has a problem.
Sorry :-/
I very much feared the following kind of obstacle with these changes.
Specifically, references to modular IPV6 code from statically compiled
IPV4 code. Which produces the following build error:
net/built-in.o: In function `__xfrm4_bundle_create':xfrm4_policy.c:(.text+0x59a88): undefined reference to `xfrm6_output'
:xfrm4_policy.c:(.text+0x59ac0): undefined reference to `xfrm6_output'
Please test with IPV6 built modular in the future, thank you.
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists