netdev
[Top] [All Lists]

Re: SCTP config 2.5.70(-bk)

To: Margit Schubert-While <margitsw@xxxxxxxxxxx>, lksctp-developers@xxxxxxxxxxxxxxxxxxxxx
Subject: Re: SCTP config 2.5.70(-bk)
From: Adrian Bunk <bunk@xxxxxxxxx>
Date: Tue, 3 Jun 2003 15:03:08 +0200
Cc: linux-kernel@xxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx
In-reply-to: <5.1.0.14.2.20030602094232.00aeda18@pop.t-online.de>
References: <5.1.0.14.2.20030602094232.00aeda18@pop.t-online.de>
Sender: netdev-bounce@xxxxxxxxxxx
User-agent: Mutt/1.4.1i
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.


Could someone from the SCTP developers comment on the intentions behind 
IPV6_SCTP__ ?


> Margit

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 in Thread] Current Thread [Next in Thread>