linux-kernel - Re: 2.6.18-rc1-mm2: process `showconsole' used the removed sysctl system call

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: <m1odvqpfg1.fsf@ebiederm.dsl.xmission.com>
Date:	Sat, 15 Jul 2006 18:21:34 -0600
From:	ebiederm@...ssion.com (Eric W. Biederman)
To:	Michal Piotrowski <michal.k.k.piotrowski@...il.com>
Cc:	Andrew Morton <akpm@...l.org>, Tilman Schmidt <tilman@...p.cc>,
	linux-kernel@...r.kernel.org
Subject: Re: 2.6.18-rc1-mm2: process `showconsole' used the removed sysctl system call

Michal Piotrowski <michal.k.k.piotrowski@...il.com> writes:

> Hi Andrew,
>
> Andrew Morton wrote:
>> On Sat, 15 Jul 2006 16:40:36 +0200
>> Tilman Schmidt <tilman@...p.cc> wrote:
>> 
>>> After installing a 2.6.18-rc1-mm2 kernel without sysctl syscall support
>>> on a standard SuSE 10.0 system, I find the following in my dmesg:
>>>
>>>> [ 36.955720] warning: process `showconsole' used the removed sysctl system
> call
>>>> [ 39.656410] warning: process `showconsole' used the removed sysctl system
> call
>>>> [ 43.304401] warning: process `showconsole' used the removed sysctl system
> call
>>>> [   45.717220] warning: process `ls' used the removed sysctl system call
>>>> [   45.789845] warning: process `touch' used the removed sysctl system call
>>> which at face value seems to contradict the statement in the help text
>>> for the CONFIG_SYSCTL_SYSCALL option that "Nothing has been using the
>>> binary sysctl interface for some time time now". (sic)
>>>
>>> Meanwhile, the second part of that sentence that "nothing should break"
>>> by disabling it seems to hold true anyway. The system runs fine, and
>>> activating CONFIG_SYSCTL_SYSCALL in the kernel doesn't seem to have any
>>> effect apart from changing the word "removed" to "obsolete" in the above
>>> messages.
>> 
>> Thanks.
>> 
>
> date and salsa also use sysctl.
>
> warning: process `date' used the removed sysctl system call
> warning: process `salsa' used the removed sysctl system call
>
>> Eric, that tends to make the whole idea inviable, doesn't it?
>
> How about _very_ long term to remove sysctl (i.e. January 2010)?

That may be reasonable.  However please confirm that everything
that you have complaints from is using libpthreads.

As there is one use of libpthreads that is using sysctl
in a very non-serious way.

With libptrheads modified to use uname and not sysctl I am not seeing that
message.  I thought I had broken my test setup by forgetting to compile
glibc with --with-tls but I managed but I managed to get things working
again using LD_ASSUME_KERNEL=2.4.1

Still not the best data point but a very interesting one.

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/