From: Andrew Morton <akpm@osdl.org>
To: Tilman Schmidt <tilman@imap.cc>
Cc: linux-kernel@vger.kernel.org,
"Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: 2.6.18-rc1-mm2: process `showconsole' used the removed sysctl system call
Date: Sat, 15 Jul 2006 15:42:00 -0700 [thread overview]
Message-ID: <20060715154200.e9138a6b.akpm@osdl.org> (raw)
In-Reply-To: <44B8FE64.6040700@imap.cc>
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.
Eric, that tends to make the whole idea inviable, doesn't it?
next prev parent reply other threads:[~2006-07-15 22:42 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 [this message]
2006-07-15 23:17 ` Eric W. Biederman
2006-07-15 23:31 ` Michal Piotrowski
2006-07-16 0:21 ` Eric W. Biederman
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=20060715154200.e9138a6b.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--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®