linux-kernel - Re: [PATCH] compat: remove compat

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]

Message-Id: <20160621163857.cf59ebebf39c38d67d71eb80@linux-foundation.org>
Date:	Tue, 21 Jun 2016 16:38:57 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Arnd Bergmann <arnd@...db.de>
Cc:	Alexander Viro <viro@...iv.linux.org.uk>,
	"Theodore Ts'o" <tytso@....edu>,
	Arnaldo Carvalho de Melo <acme@...hat.com>,
	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] compat: remove compat_printk

On Fri, 17 Jun 2016 16:26:21 +0200 Arnd Bergmann <arnd@...db.de> wrote:

> After 7e8e385aaf6e ("x86/compat: Remove sys32_vm86_warning"), this
> function has become unused, so we can remove it as well.

hm,

> @@ -1077,15 +1076,6 @@ static struct ctl_table kern_table[] = {
>  		.extra1		= &neg_one,
>  	},
>  #endif
> -#ifdef CONFIG_COMPAT
> -	{
> -		.procname	= "compat-log",
> -		.data		= &compat_log,
> -		.maxlen		= sizeof (int),
> -	 	.mode		= 0644,
> -		.proc_handler	= proc_dointvec,
> -	},
> -#endif

How do we know we can simply remove /proc/sys/kernel/compat-log without
breaking any userspace?