From 4cb6066af9ee58ddba58a63cc77b324ac21add75 Mon Sep 17 00:00:00 2001 From: "David S. Miller" Date: Mon, 9 Aug 2010 00:45:46 -0700 Subject: sparc: Kill user copy check code. For whatever reason GCC isn't able to figure things out in the control flow (in particular when min() and max() expressions are involved) on sparc as well as it can on x86. So lots of useless incorrect user copy warnings get spewed and the full-on compile failure mode of the user copy checks were never usable on sparc at all. People can debug these kinds of problems on x86. Signed-off-by: David S. Miller --- arch/sparc/Kconfig.debug | 14 -------------- 1 file changed, 14 deletions(-) (limited to 'arch/sparc/Kconfig.debug') diff --git a/arch/sparc/Kconfig.debug b/arch/sparc/Kconfig.debug index 1b4a831565f..d9a795efbc0 100644 --- a/arch/sparc/Kconfig.debug +++ b/arch/sparc/Kconfig.debug @@ -30,18 +30,4 @@ config FRAME_POINTER depends on MCOUNT default y -config DEBUG_STRICT_USER_COPY_CHECKS - bool "Strict copy size checks" - depends on DEBUG_KERNEL && !TRACE_BRANCH_PROFILING - ---help--- - Enabling this option turns a certain set of sanity checks for user - copy operations into compile time failures. - - The copy_from_user() etc checks are there to help test if there - are sufficient security checks on the length argument of - the copy operation, by having gcc prove that the argument is - within bounds. - - If unsure, or if you run an older (pre 4.4) gcc, say N. - endmenu -- cgit v1.2.3