Skip to contentSkip to conversation

x86: Kill some chicken bits

PATCH In review Borislav Petkov 2 participants 4 messages Oct 20, 2015 – Oct 21, 2015

Subsystems (2)
lore
Share & tools
lore

Borislav Petkov

author maintainer
#0 lore raw

PATCH 1/1 x86: Kill some chicken bits

From: Borislav Petkov <[email protected]>

Those were added as, well, chicken bits in case some of those features are b0rked and as a way for us to "chicken" out and disable them. Remove those chicken bits now, as they're not needed anymore.

---
 Documentation/kernel-parameters.txt | 10 ----------
 arch/x86/kernel/cpu/common.c        | 22 ----------------------
 2 files changed, 32 deletions(-)
Documentation/kernel-parameters.txt +0 -10
index 22a4b687ea5b..0448d63e3269 100644
@@ -2362,8 +2362,6 @@ bytes respectively. Such letter suffixes can also be entirely omitted.
 
 	nocache		[ARM]
 
-	noclflush	[BUGS=X86] Don't use the CLFLUSH instruction
-
 	nodelayacct	[KNL] Disable per-task delay accounting
 
 	nodisconnect	[HW,SCSI,M68K] Disables SCSI disconnects.
@@ -2379,14 +2377,6 @@ bytes respectively. Such letter suffixes can also be entirely omitted.
 			noexec=on: enable non-executable mappings (default)
 			noexec=off: disable non-executable mappings
 
-	nosmap		[X86]
-			Disable SMAP (Supervisor Mode Access Prevention)
-			even if it is supported by processor.
-
-	nosmep		[X86]
-			Disable SMEP (Supervisor Mode Execution Prevention)
-			even if it is supported by processor.
-
 	noexec32	[X86-64]
 			This affects only 32-bit executables.
 			noexec32=on: enable non-executable mappings (default)
arch/x86/kernel/cpu/common.c +0 -22
index de22ea7ff82f..610c84379d87 100644
@@ -251,26 +251,12 @@ static inline void squash_the_stupid_serial_number(struct cpuinfo_x86 *c)
 }
 #endif
 
-static __init int setup_disable_smep(char *arg)
-{
-	setup_clear_cpu_cap(X86_FEATURE_SMEP);
-	return 1;
-}
-__setup("nosmep", setup_disable_smep);
-
 static __always_inline void setup_smep(struct cpuinfo_x86 *c)
 {
 	if (cpu_has(c, X86_FEATURE_SMEP))
 		cr4_set_bits(X86_CR4_SMEP);
 }
 
-static __init int setup_disable_smap(char *arg)
-{
-	setup_clear_cpu_cap(X86_FEATURE_SMAP);
-	return 1;
-}
-__setup("nosmap", setup_disable_smap);
-
 static __always_inline void setup_smap(struct cpuinfo_x86 *c)
 {
 	unsigned long eflags;
@@ -1083,14 +1069,6 @@ static __init int setup_show_msr(char *arg)
 }
 __setup("show_msr=", setup_show_msr);
 
-static __init int setup_noclflush(char *arg)
-{
-	setup_clear_cpu_cap(X86_FEATURE_CLFLUSH);
-	setup_clear_cpu_cap(X86_FEATURE_CLFLUSHOPT);
-	return 1;
-}
-__setup("noclflush", setup_noclflush);
-
 void print_cpu_info(struct cpuinfo_x86 *c)
 {
 	const char *vendor = NULL;
Signature · 1 line
2.3.5
#1 lore raw
Quoted 83 lines · Borislav Petkov

From: Borislav Petkov <[email protected]>

Those were added as, well, chicken bits in case some of those features are b0rked and as a way for us to "chicken" out and disable them. Remove
those chicken bits now, as they're not needed anymore.

---
Documentation/kernel-parameters.txt | 10 ----------
arch/x86/kernel/cpu/common.c | 22 ----------------------

2 files changed, 32 deletions(-)
Documentation/kernel-parameters.txt +0 -0
index 22a4b687ea5b..0448d63e3269 100644
@@ -2362,8 +2362,6 @@ bytes respectively. Such letter suffixes can also

be entirely omitted.

	nocache		[ARM]
Documentation/kernel-parameters.txt +0 -2
-	noclflush	[BUGS=X86] Don't use the CLFLUSH instruction
-

nodelayacct [KNL] Disable per-task delay accounting

nodisconnect [HW,SCSI,M68K] Disables SCSI disconnects.

Documentation/kernel-parameters.txt +0 -0
@@ -2379,14 +2377,6 @@ bytes respectively. Such letter suffixes can

also be entirely omitted.
noexec=on: enable non-executable mappings (default) noexec=off: disable non-executable mappings

Documentation/kernel-parameters.txt +0 -8
-	nosmap		[X86]
-			Disable SMAP (Supervisor Mode Access Prevention)
-			even if it is supported by processor.
-
-	nosmep		[X86]
-			Disable SMEP (Supervisor Mode Execution Prevention)
-			even if it is supported by processor.
-

noexec32 [X86-64]
This affects only 32-bit executables. noexec32=on: enable non-executable mappings (default)

arch/x86/kernel/cpu/common.c +0 -14
index de22ea7ff82f..610c84379d87 100644
@@ -251,26 +251,12 @@ static inline void
 squash_the_stupid_serial_number(struct cpuinfo_x86 *c)
 }
 #endif
 
-static __init int setup_disable_smep(char *arg)
-{
-	setup_clear_cpu_cap(X86_FEATURE_SMEP);
-	return 1;
-}
-__setup("nosmep", setup_disable_smep);
-
 static __always_inline void setup_smep(struct cpuinfo_x86 *c)
 {
 	if (cpu_has(c, X86_FEATURE_SMEP))
 		cr4_set_bits(X86_CR4_SMEP);
 }
 
-static __init int setup_disable_smap(char *arg)
-{
-	setup_clear_cpu_cap(X86_FEATURE_SMAP);
-	return 1;
-}
-__setup("nosmap", setup_disable_smap);
-
 static __always_inline void setup_smap(struct cpuinfo_x86 *c)
 {
	unsigned long eflags;
arch/x86/kernel/cpu/common.c +0 -1
@@ -1083,14 +1069,6 @@ static __init int setup_show_msr(char *arg)
 }
 __setup("show_msr=", setup_show_msr);
 
-static __init int setup_noclflush(char *arg)

arch/x86/kernel/cpu/common.c static __init int setup_show_msr(char *arg) · line 1074

Quoted 10 lines
arch/x86/kernel/cpu/common.c +0 -7
-{
-	setup_clear_cpu_cap(X86_FEATURE_CLFLUSH);
-	setup_clear_cpu_cap(X86_FEATURE_CLFLUSHOPT);
-	return 1;
-}
-__setup("noclflush", setup_noclflush);
-
 void print_cpu_info(struct cpuinfo_x86 *c)
 {
 	const char *vendor = NULL;

I would like to keep nosmap until SMAP hardware is more ubiquitous since SMAP is vulnerable to kernel bugs. We have already had a case where a maintainer pushed "cleanup" code straight to Linus, bypassing the x86 maintainers, which broke booting on SMAP hardware.

Signature · 1 line
Sent from my Android device with K-9 Mail. Please excuse my brevity.
author maintainer
#2 lore raw
Quoted 4 lines · H. Peter Anvin

I would like to keep nosmap until SMAP hardware is more ubiquitous since SMAP is vulnerable to kernel bugs. We have already had a case where a maintainer pushed "cleanup" code straight to Linus, bypassing the x86 maintainers, which broke booting on SMAP hardware.

Right, so the thought came to my mind while going through those, that we don't really know what they're going to be good for and what we're going to need them for in the future. So maybe we want to keep them after all
- you never know.

For example, luto made me use "nosep" recently even though that's an ancient chicken bit.

So maybe we want to not remove them ever - the cleanup win is not that great to even care...

Signature · 4 lines
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.
#3 lore raw
Quoted 11 lines · Borislav Petkov
Quoted 4 lines · H. Peter Anvin

I would like to keep nosmap until SMAP hardware is more ubiquitous since SMAP is vulnerable to kernel bugs. We have already had a case where a maintainer pushed "cleanup" code straight to Linus, bypassing the x86 maintainers, which broke booting on SMAP hardware.

Right, so the thought came to my mind while going through those, that we don't really know what they're going to be good for and what we're going to need them for in the future. So maybe we want to keep them after all
- you never know.

Quoted 6 lines

For example, luto made me use "nosep" recently even though that's an ancient chicken bit.

So maybe we want to not remove them ever - the cleanup win is not that great to even care...

Some chicken bits may be better than others, though.

-hpa