mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>
Cc: Andrew Morton <akpm@osdl.org>, Tilman Schmidt <tilman@imap.cc>,
	linux-kernel@vger.kernel.org
Subject: Re: 2.6.18-rc1-mm2: process `showconsole' used the removed sysctl system call
Date: Sat, 15 Jul 2006 18:21:34 -0600	[thread overview]
Message-ID: <m1odvqpfg1.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <44B97ADD.5000302@gmail.com> (Michal Piotrowski's message of "Sun, 16 Jul 2006 01:31:41 +0200")

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

> Hi Andrew,
>
> Andrew Morton wrote:
>> On Sat, 15 Jul 2006 16:40:36 +0200
>> Tilman Schmidt <tilman@imap.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

  reply	other threads:[~2006-07-16  0:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-15 14:40 Tilman Schmidt
2006-07-15 22:42 ` Andrew Morton
2006-07-15 23:17   ` Eric W. Biederman
2006-07-15 23:31   ` Michal Piotrowski
2006-07-16  0:21     ` Eric W. Biederman [this message]
2006-07-16  0:50       ` Michal Piotrowski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m1odvqpfg1.fsf@ebiederm.dsl.xmission.com \
    --to=ebiederm@xmission.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.k.k.piotrowski@gmail.com \
    --cc=tilman@imap.cc \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®