linux-kernel - Re: [PATCH 22/23] sysctl arm: Remove binary sysctl support

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:	Sun, 08 Nov 2009 15:05:05 -0800
From:	ebiederm@...ssion.com (Eric W. Biederman)
To:	Russell King <rmk+lkml@....linux.org.uk>
Cc:	linux-kernel@...r.kernel.org, Leo Chen <leochen@...adcom.com>
Subject: Re: [PATCH 22/23] sysctl arm: Remove binary sysctl support

ebiederm@...ssion.com (Eric W. Biederman) writes:

> Russell King <rmk+lkml@....linux.org.uk> writes:
>
>>
>> NAK.  Glibc uses these numeric sysctls to support ioperm emulation on ARM.
>> Therefore, removal of these numeric sysctls breaks that user interface:
>>
>>   static int iobase_name[] = { CTL_BUS, BUS_ISA, BUS_ISA_PORT_BASE };
>>   static int ioshift_name[] = { CTL_BUS, BUS_ISA, BUS_ISA_PORT_SHIFT };
>>   if (! sysctl (iobase_name, 3, &io.io_base, &len, NULL, 0)
>>       && ! sysctl (ioshift_name, 3, &io.shift, &len, NULL, 0))
>>     {
>>       io.initdone = 1;
>>       return 0;
>>     }
>
> Those still exist in sysctl_binary.c are provided by reading
> /proc/sys/bus/isa/membase, /proc/sys/bus/isa/portbase, and
> /proc/sys/bus/isa/portshift.
>
> The practical difference is that /proc support now must be compiled
> in to support sys_sysctl.

But thanks for the reminder that I need to go into glibc and fix this before
we disable the sys_sysctl emulation by default.

Eric
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/