From: David Miller <davem@davemloft.net>
To: kazunori@miyazawa.org
Cc: miika@iki.fi, Diego.Beltrami@hiit.fi,
herbert@gondor.apana.org.au, netdev@vger.kernel.org,
usagi-core@linux-ipv6.org
Subject: Re: [RFC][PATCH][IPSEC][0/3]inter address family ipsec tunnel
Date: Tue, 06 Feb 2007 14:24:07 -0800 (PST) [thread overview]
Message-ID: <20070206.142407.48395902.davem@davemloft.net> (raw)
In-Reply-To: <20061229144702.11ff0478.kazunori@miyazawa.org>
From: Kazunori MIYAZAWA <kazunori@miyazawa.org>
Date: Fri, 29 Dec 2006 14:47:02 +0900
> I fixed the compile issue when we configure IPv6 as a module.
>
> [1/3] exporting xfrm_state_afinfo
> [2/3] supporting IPv6 over IPv4 IPsec
> [3/3] supporting IPv4 over IPv6 IPsec
>
> These patches can be applied to linux-2.6.20-rc2.
Thank you. This is not a bad solution to the symbol
export problem, for now.
I noticed that there is no need for the module symbol
export of xfrm6_output() you added, because xfrm6_output.o
and xfrm6_state.o always get linked together.
So I will remove that:
+EXPORT_SYMBOL(xfrm6_output);
part of the first patch.
We see so many issues with ipv6 symbols dependencies in various
subsystems (netfilter, xfrm, etc.). It is a sign that we need
some kind of long range plan to deal with this problem. Since
the ipv6 module can't be unloaded anyways, and it's been broken
like that forever, it might make sense to make ipv6 only available
non-modular. I know people would dislike this, but the current
situation isn't good either.
Thanks again.
next prev parent reply other threads:[~2007-02-06 22:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-29 5:47 [RFC][PATCH][IPSEC][0/3]inter address family ipsec tunnel Kazunori MIYAZAWA
2007-02-06 22:24 ` David Miller [this message]
2007-02-06 22:43 ` depending on IPv6 symbols (was: [RFC][PATCH][IPSEC][0/3]inter address family ipsec tunnel) Roland Dreier
2007-02-06 22:49 ` depending on IPv6 symbols David Miller
2007-02-06 22:53 ` Roland Dreier
2007-02-06 23:33 ` David Miller
2007-02-07 0:07 ` Roland Dreier
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=20070206.142407.48395902.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Diego.Beltrami@hiit.fi \
--cc=herbert@gondor.apana.org.au \
--cc=kazunori@miyazawa.org \
--cc=miika@iki.fi \
--cc=netdev@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).