Documentation: remove depends on CONFIG_EXPERIMENTAL
The CONFIG_EXPERIMENTAL config item has not carried much meaning for a while now and is almost always enabled by default. As agreed during the Linux kernel summit, remove it from any "depends on" lines in Kconfigs. CC: Rob Landley <rob@landley.net> CC: Jiri Kosina <jkosina@suse.cz> CC: Masanari Iida <standby24x7@gmail.com> CC: Jason Wessel <jason.wessel@windriver.com> CC: Richard L Maliszewski <richard.l.maliszewski@intel.com> CC: Gang Wei <gang.wei@intel.com> CC: Shane Wang <shane.wang@intel.com> CC: Harry Wei <harryxiyou@gmail.com> Signed-off-by: Kees Cook <keescook@chromium.org> Acked-by: Jason Wessel <jason.wessel@windriver.com>
This commit is contained in:
parent
5a958db311
commit
0335cb469a
|
@ -546,15 +546,7 @@ config AUDIT
|
||||||
logging of avc messages output). Does not do system-call
|
logging of avc messages output). Does not do system-call
|
||||||
auditing without CONFIG_AUDITSYSCALL.
|
auditing without CONFIG_AUDITSYSCALL.
|
||||||
|
|
||||||
Features that might still be considered unstable should be defined as
|
Seriously dangerous features (such as write support for certain
|
||||||
dependent on "EXPERIMENTAL":
|
|
||||||
|
|
||||||
config SLUB
|
|
||||||
depends on EXPERIMENTAL && !ARCH_USES_SLAB_PAGE_STRUCT
|
|
||||||
bool "SLUB (Unqueued Allocator)"
|
|
||||||
...
|
|
||||||
|
|
||||||
while seriously dangerous features (such as write support for certain
|
|
||||||
filesystems) should advertise this prominently in their prompt string:
|
filesystems) should advertise this prominently in their prompt string:
|
||||||
|
|
||||||
config ADFS_FS_RW
|
config ADFS_FS_RW
|
||||||
|
|
|
@ -1184,13 +1184,6 @@ static struct block_device_operations opt_fops = {
|
||||||
<filename>Documentation/kbuild/kconfig-language.txt</filename>.
|
<filename>Documentation/kbuild/kconfig-language.txt</filename>.
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
<para>
|
|
||||||
You may well want to make your CONFIG option only visible if
|
|
||||||
<symbol>CONFIG_EXPERIMENTAL</symbol> is enabled: this serves as a
|
|
||||||
warning to users. There many other fancy things you can do: see
|
|
||||||
the various <filename>Kconfig</filename> files for ideas.
|
|
||||||
</para>
|
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
In your description of the option, make sure you address both the
|
In your description of the option, make sure you address both the
|
||||||
expert user and the user who knows nothing about your feature. Mention
|
expert user and the user who knows nothing about your feature. Mention
|
||||||
|
|
|
@ -94,10 +94,8 @@
|
||||||
<sect1 id="CompileKGDB">
|
<sect1 id="CompileKGDB">
|
||||||
<title>Kernel config options for kgdb</title>
|
<title>Kernel config options for kgdb</title>
|
||||||
<para>
|
<para>
|
||||||
To enable <symbol>CONFIG_KGDB</symbol> you should first turn on
|
To enable <symbol>CONFIG_KGDB</symbol> you should look under
|
||||||
"Prompt for development and/or incomplete code/drivers"
|
"Kernel debugging" and select "KGDB: kernel debugger".
|
||||||
(CONFIG_EXPERIMENTAL) in "General setup", then under the
|
|
||||||
"Kernel debugging" select "KGDB: kernel debugger".
|
|
||||||
</para>
|
</para>
|
||||||
<para>
|
<para>
|
||||||
While it is not a hard requirement that you have symbols in your
|
While it is not a hard requirement that you have symbols in your
|
||||||
|
|
|
@ -192,7 +192,7 @@ grub.conf needs to be modified as follows:
|
||||||
|
|
||||||
The kernel option for enabling Intel TXT support is found under the
|
The kernel option for enabling Intel TXT support is found under the
|
||||||
Security top-level menu and is called "Enable Intel(R) Trusted
|
Security top-level menu and is called "Enable Intel(R) Trusted
|
||||||
Execution Technology (TXT)". It is marked as EXPERIMENTAL and
|
Execution Technology (TXT)". It is considered EXPERIMENTAL and
|
||||||
depends on the generic x86 support (to allow maximum flexibility in
|
depends on the generic x86 support (to allow maximum flexibility in
|
||||||
kernel build options), since the tboot code will detect whether the
|
kernel build options), since the tboot code will detect whether the
|
||||||
platform actually supports Intel TXT and thus whether any of the
|
platform actually supports Intel TXT and thus whether any of the
|
||||||
|
|
|
@ -462,13 +462,6 @@ config AUDIT
|
||||||
logging of avc messages output). Does not do system-call
|
logging of avc messages output). Does not do system-call
|
||||||
auditing without CONFIG_AUDITSYSCALL.
|
auditing without CONFIG_AUDITSYSCALL.
|
||||||
|
|
||||||
仍然被认为不够稳定的功能应该被定义为依赖于“EXPERIMENTAL”:
|
|
||||||
|
|
||||||
config SLUB
|
|
||||||
depends on EXPERIMENTAL && !ARCH_USES_SLAB_PAGE_STRUCT
|
|
||||||
bool "SLUB (Unqueued Allocator)"
|
|
||||||
...
|
|
||||||
|
|
||||||
而那些危险的功能(比如某些文件系统的写支持)应该在它们的提示字符串里显著的声明这
|
而那些危险的功能(比如某些文件系统的写支持)应该在它们的提示字符串里显著的声明这
|
||||||
一点:
|
一点:
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue