From: Adrian Bunk <bunk@fs.tum.de>
To: Arnaldo Carvalho de Melo <acme@conectiva.com.br>,
netdev@oss.sgi.com, davem@redhat.com, pekkas@netcore.fi,
lksctp-developers@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: RFC: [2.6 patch] disallow modular IPv6
Date: Mon, 29 Sep 2003 01:24:03 +0200 [thread overview]
Message-ID: <20030928232403.GX15338@fs.tum.de> (raw)
In-Reply-To: <20030928231842.GE1039@conectiva.com.br>
On Sun, Sep 28, 2003 at 08:18:42PM -0300, Arnaldo Carvalho de Melo wrote:
> Em Mon, Sep 29, 2003 at 12:59:41AM +0200, Adrian Bunk escreveu:
> > It seems modular IPv6 doesn't work 100% reliable, e.g. after looking at
> > the code it doesn't seem to be a good idea to compile a kernel without
> > IPv6 support and later build and install IPv6 modules. Is there a great
> > need for modular IPv6 or is the patch below to disallow modular IPv6 OK?
>
> Please, don't... We're going in the all modules direction, not the other
> way around, distro (general purpose) kernels would get big bloat in the
> static kernel.
E.g. from include/net/tcp.h:
<-- snip -->
...
struct tcp_skb_cb {
union {
struct inet_skb_parm h4;
#if defined(CONFIG_IPV6) || defined (CONFIG_IPV6_MODULE)
struct inet6_skb_parm h6;
#endif
} header; /* For incoming frames */
...
<-- snip -->
This is broken since it's legal to compile a module much later than the
kernel.
If modular IPv6 is allowed, the #if has to be removed, and the struct
will be larger in the case IPv6 is never be used.
> - Arnaldo
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2003-09-28 23:24 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-28 22:59 RFC: [2.6 patch] disallow modular IPv6 Adrian Bunk
2003-09-28 23:18 ` Arnaldo Carvalho de Melo
2003-09-28 23:24 ` Adrian Bunk [this message]
2003-09-28 23:39 ` Arnaldo Carvalho de Melo
2003-09-28 23:47 ` Arnaldo Carvalho de Melo
2003-09-29 0:14 ` Adrian Bunk
2003-09-29 0:32 ` Arnaldo Carvalho de Melo
2003-09-29 9:02 ` David Woodhouse
2003-09-29 14:15 ` Arnaldo Carvalho de Melo
2003-09-29 14:28 ` Jan Evert van Grootheest
2003-09-29 14:29 ` David Woodhouse
2003-09-29 14:38 ` Valdis.Kletnieks
2003-09-29 14:46 ` David Woodhouse
2003-09-30 5:17 ` David S. Miller
2003-09-30 6:31 ` David Woodhouse
2003-10-01 19:47 ` Guennadi Liakhovetski
2003-09-30 5:11 ` David S. Miller
2003-09-30 13:37 ` Adrian Bunk
2003-09-30 15:04 ` Arnaldo Carvalho de Melo
2003-10-01 6:39 ` David S. Miller
2003-09-30 5:09 ` David S. Miller
2003-09-30 6:32 ` David Woodhouse
2003-09-30 7:03 ` David S. Miller
2003-09-30 7:39 ` David Woodhouse
2003-09-30 8:08 ` David S. Miller
2003-09-30 8:26 ` David Woodhouse
2003-09-30 8:30 ` David S. Miller
2003-09-30 8:42 ` David Woodhouse
2003-09-30 8:51 ` David S. Miller
2003-09-30 9:14 ` David Woodhouse
2003-09-30 9:17 ` David Woodhouse
2003-09-30 9:24 ` David S. Miller
2003-09-30 9:57 ` Sam Ravnborg
2003-09-30 10:02 ` David Woodhouse
2003-09-30 10:01 ` David S. Miller
2003-09-30 10:14 ` David Woodhouse
2003-09-30 11:39 ` Sam Ravnborg
2003-09-30 13:44 ` Dana Lacoste
2003-09-30 13:50 ` Kai Germaschewski
2003-09-30 15:13 ` Richard Guy Briggs
2003-09-30 14:21 ` Theodore Ts'o
2003-09-30 14:51 ` David Woodhouse
2003-09-30 12:06 ` Olivier Galibert
2003-09-29 6:29 ` Pekka Savola
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=20030928232403.GX15338@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=acme@conectiva.com.br \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lksctp-developers@lists.sourceforge.net \
--cc=netdev@oss.sgi.com \
--cc=pekkas@netcore.fi \
/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).