From: Adrian Bunk <bunk@fs.tum.de>
To: Jon Grimm <jgrimm2@us.ibm.com>
Cc: Margit Schubert-While <margitsw@t-online.de>,
lksctp-developers@lists.sourceforge.net,
linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: [Lksctp-developers] Re: SCTP config 2.5.70(-bk)
Date: Sat, 7 Jun 2003 21:12:35 +0200 [thread overview]
Message-ID: <20030607191235.GE13377@fs.tum.de> (raw)
In-Reply-To: <3EDD0DFC.4080806@us.ibm.com>
On Tue, Jun 03, 2003 at 04:07:08PM -0500, Jon Grimm wrote:
> Hi Adrian,
Hi Jon,
> Sorry for a bit of delay... We are away at an SCTP Interoperability
> event.
the delay before my answer was bigger...
> Adrian Bunk wrote:
> >On Mon, Jun 02, 2003 at 09:53:04AM +0200, Margit Schubert-While wrote:
> >
> >
> >>CONFIG_IPV6_SCTP__ is always being set to "y" even though
> >>not selected (CONFIG_IPV6 not set)
> >
> >
> >First, this doesn't do any harm since CONFIG_IPV6_SCTP__ alone doensn't
> >result in anything getting compiled.
> >
> >But besides, it seems a bit broken.
> >
> >From net/sctp/Kconfig:
> >
> ><-- snip -->
> >
> >...
> >
> >config IPV6_SCTP__
> > tristate
> > default y if IPV6=n
> > default IPV6 if IPV6
> >
> >config IP_SCTP
> > tristate "The SCTP Protocol (EXPERIMENTAL)"
> > depends on IPV6_SCTP__
> >...
> >
> ><-- snip -->
> >
> >
> >Semantically equivalent is the following for IPV6_SCTP__:
> >
> >config IPV6_SCTP__
> > tristate
> > default y if IPV6=n || IPV6=y
> > default m if IPV6=m
> >
> >
> >If it was intended to disallow a static IP_SCTP with a modular IPV6 it
> >doesn't work: It's perfectly allowed to set IPV6=n and IP_SCTP=y and
> >later compile and install a modular IPV6 for the same kernel.
> >
>
> Are you sure? I vaguely remember one of the network structs having
> #ifdef'd fields for v6. Consequently, if one compiles first without,
> but the tries later compiles/loads ipv6... bad things happen as the
> kernel has a different concept of what the sock is.
after reading this at net/Kconfig:
<-- snip -->
...
# IPv6 as module will cause a CRASH if you try to unload it
config IPV6
tristate "The IPv6 protocol (EXPERIMENTAL)"
...
<-- snip -->
I'm wondering whether it might be an idea to disallow the modular
building of IPv6 support?
> >Could someone from the SCTP developers comment on the intentions behind
> >IPV6_SCTP__ ?
> >
>
> Yes. The intent was to at least discourage a configuration that will
> segfault.
It's currently discouraged but not completelyt impossible to select...
> Thanks,
> jon
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
prev parent reply other threads:[~2003-06-07 18:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-02 7:53 SCTP config 2.5.70(-bk) Margit Schubert-While
2003-06-03 13:03 ` Adrian Bunk
2003-06-03 21:07 ` [Lksctp-developers] " Jon Grimm
2003-06-07 19:12 ` Adrian Bunk [this message]
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=20030607191235.GE13377@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=jgrimm2@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lksctp-developers@lists.sourceforge.net \
--cc=margitsw@t-online.de \
--cc=netdev@oss.sgi.com \
/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).