linux-kernel - Re: Change CONFIG_DEVKMEM default value to n

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Fri, 7 Oct 2016 05:57:19 +0200
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Dave Young <dyoung@...hat.com>
Cc:     Arnd Bergmann <arnd@...db.de>, Kees Cook <keescook@...omium.org>,
        linux-kernel@...r.kernel.org
Subject: Re: Change CONFIG_DEVKMEM default value to n

On Fri, Oct 07, 2016 at 10:04:11AM +0800, Dave Young wrote:
> Kconfig comment suggests setting it as "n" if in doubt thus move the
> default value to 'n'.
> 
> Signed-off-by: Dave Young <dyoung@...hat.com>
> Suggested-by: Kees Cook <keescook@...omium.org>
> ---
>  drivers/char/Kconfig |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> --- linux-x86.orig/drivers/char/Kconfig
> +++ linux-x86/drivers/char/Kconfig
> @@ -17,7 +17,7 @@ config DEVMEM
>  
>  config DEVKMEM
>  	bool "/dev/kmem virtual device support"
> -	default y
> +	default n

If you remove the "default" line, it defaults to 'n'.

And is it really "safe" to default this to n now?

thanks,

greg k-h