From: Florian Fainelli <florian@openwrt.org>
To: Vlad Yasevich <vyasevich@gmail.com>
Cc: Neil Horman <nhorman@tuxdriver.com>,
netdev@vger.kernel.org, David Miller <davem@davemloft.net>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-sctp@vger.kernel.org
Subject: Re: [PATCH v2] sctp: Change defaults on cookie hmac selection
Date: Tue, 08 Jan 2013 17:36:50 +0000 [thread overview]
Message-ID: <50EC5932.4040407@openwrt.org> (raw)
In-Reply-To: <50EAEE64.5010300@gmail.com>
Le 01/07/13 16:48, Vlad Yasevich a écrit :
> No, thats the problem, your old config is no longer valid with this
> new Kconfig
>> file. Your config is telling the config utility that you want your
>> default
>> Cookie hmac to be MD5, but you've explicitly told it (via your yes ""
>> | make
>> oldconfig command), that you want SCTP_COOKIE_HMAC_MD5 to be
>> disabled, so the
>> config utility is left with no choice to prompt you again for a
>> default hmac,
>> which your command answers again by saying
>> SCTP_DEFAULT_COOKIE_HMAC_MD5 (the
>> default choice of 1). Thats your loop, you keep telling the config
>> utility that
>> you both want the default hmac to be md5, and that you don't want to
>> allow md5
>> to be an available hmac alg.
>>
>> Thats not a bug. I'm sorry if your old configuration needs manual
>> updating, but
>> there are no guarantees that old configurations will 'just work' in
>> perpituity.
>>
>
> Neil
>
> Actually, I think we have a bug in the config. Look at the thermal
> driver config again. It has:
>
> choice
> prompt "Default Thermal governor"
> default THERMAL_DEFAULT_GOV_STEP_WISE
>
> config THERMAL_DEFAULT_GOV_STEP_WISE
> ...
> config THERMAL_DEFAULT_GOV_FAIR_SHARE
> ...
> config THERMAL_DEFAULT_GOV_USER_SPACE
> ...
> endchoice
>
>
> SCTP has:
>
> choice
> prompt "Default SCTP cookie HMAC encoding"
> default SCTP_COOKIE_HMAC_MD5
>
> config SCTP_DEFAULT_COOKIE_HMAC_MD5
> ...
> config SCTP_DEFAULT_COOKIE_HMAC_SHA1
> ...
> config SCTP_DEFAULT_COOKIE_HMAC_NONE
> ...
> endchoice
>
> See the difference? The default value of the choice statement needs to
> be one of the available choices.
Right, since none of the config symbols actually exist when migrating
from and oldconfig we are still being prompted, which is just fine
actually. Having the config symbol being the default a member of the
choice/endchoice section is what should be expected.
--
Florian
WARNING: multiple messages have this Message-ID (diff)
From: Florian Fainelli <florian@openwrt.org>
To: Vlad Yasevich <vyasevich@gmail.com>
Cc: Neil Horman <nhorman@tuxdriver.com>,
netdev@vger.kernel.org, David Miller <davem@davemloft.net>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-sctp@vger.kernel.org
Subject: Re: [PATCH v2] sctp: Change defaults on cookie hmac selection
Date: Tue, 08 Jan 2013 18:36:50 +0100 [thread overview]
Message-ID: <50EC5932.4040407@openwrt.org> (raw)
In-Reply-To: <50EAEE64.5010300@gmail.com>
Le 01/07/13 16:48, Vlad Yasevich a écrit :
> No, thats the problem, your old config is no longer valid with this
> new Kconfig
>> file. Your config is telling the config utility that you want your
>> default
>> Cookie hmac to be MD5, but you've explicitly told it (via your yes ""
>> | make
>> oldconfig command), that you want SCTP_COOKIE_HMAC_MD5 to be
>> disabled, so the
>> config utility is left with no choice to prompt you again for a
>> default hmac,
>> which your command answers again by saying
>> SCTP_DEFAULT_COOKIE_HMAC_MD5 (the
>> default choice of 1). Thats your loop, you keep telling the config
>> utility that
>> you both want the default hmac to be md5, and that you don't want to
>> allow md5
>> to be an available hmac alg.
>>
>> Thats not a bug. I'm sorry if your old configuration needs manual
>> updating, but
>> there are no guarantees that old configurations will 'just work' in
>> perpituity.
>>
>
> Neil
>
> Actually, I think we have a bug in the config. Look at the thermal
> driver config again. It has:
>
> choice
> prompt "Default Thermal governor"
> default THERMAL_DEFAULT_GOV_STEP_WISE
>
> config THERMAL_DEFAULT_GOV_STEP_WISE
> ...
> config THERMAL_DEFAULT_GOV_FAIR_SHARE
> ...
> config THERMAL_DEFAULT_GOV_USER_SPACE
> ...
> endchoice
>
>
> SCTP has:
>
> choice
> prompt "Default SCTP cookie HMAC encoding"
> default SCTP_COOKIE_HMAC_MD5
>
> config SCTP_DEFAULT_COOKIE_HMAC_MD5
> ...
> config SCTP_DEFAULT_COOKIE_HMAC_SHA1
> ...
> config SCTP_DEFAULT_COOKIE_HMAC_NONE
> ...
> endchoice
>
> See the difference? The default value of the choice statement needs to
> be one of the available choices.
Right, since none of the config symbols actually exist when migrating
from and oldconfig we are still being prompted, which is just fine
actually. Having the config symbol being the default a member of the
choice/endchoice section is what should be expected.
--
Florian
next prev parent reply other threads:[~2013-01-08 17:36 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-14 18:51 [PATCH] sctp: Change defaults on cookie hmac selection Neil Horman
2012-12-14 18:51 ` Neil Horman
2012-12-14 20:01 ` Vlad Yasevich
2012-12-14 20:01 ` Vlad Yasevich
2012-12-14 21:56 ` Linus Torvalds
2012-12-14 21:56 ` Linus Torvalds
2012-12-15 0:38 ` Neil Horman
2012-12-15 0:38 ` Neil Horman
2012-12-15 0:44 ` Linus Torvalds
2012-12-15 0:44 ` Linus Torvalds
2012-12-15 1:12 ` Neil Horman
2012-12-15 1:12 ` Neil Horman
2012-12-15 1:14 ` David Miller
2012-12-15 1:14 ` David Miller
2012-12-15 1:22 ` [PATCH v2] " Neil Horman
2012-12-15 1:22 ` Neil Horman
2012-12-16 1:16 ` David Miller
2012-12-16 1:16 ` David Miller
2013-01-07 13:25 ` Florian Fainelli
2013-01-07 13:25 ` Florian Fainelli
2013-01-07 14:49 ` Neil Horman
2013-01-07 14:49 ` Neil Horman
2013-01-07 15:15 ` Florian Fainelli
2013-01-07 15:15 ` Florian Fainelli
2013-01-07 15:38 ` Neil Horman
2013-01-07 15:38 ` Neil Horman
2013-01-07 15:48 ` Vlad Yasevich
2013-01-07 15:48 ` Vlad Yasevich
2013-01-08 17:36 ` Florian Fainelli [this message]
2013-01-08 17:36 ` Florian Fainelli
2013-01-07 15:32 ` Vlad Yasevich
2013-01-07 15:32 ` Vlad Yasevich
2013-01-07 15:46 ` Neil Horman
2013-01-07 15:46 ` Neil Horman
2013-01-07 16:39 ` Vlad Yasevich
2013-01-07 16:39 ` Vlad Yasevich
2013-01-08 17:48 ` Florian Fainelli
2013-01-08 17:48 ` Florian Fainelli
2013-01-08 18:08 ` Vlad Yasevich
2013-01-08 18:08 ` Vlad Yasevich
2013-01-08 18:20 ` Alex Elder
2013-01-08 18:20 ` Alex Elder
2013-01-08 18:28 ` Vlad Yasevich
2013-01-08 18:28 ` Vlad Yasevich
2013-01-09 9:08 ` Florian Fainelli
2013-01-09 9:08 ` Florian Fainelli
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=50EC5932.4040407@openwrt.org \
--to=florian@openwrt.org \
--cc=davem@davemloft.net \
--cc=linux-sctp@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=torvalds@linux-foundation.org \
--cc=vyasevich@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.