From: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Tilman Schmidt <tilman@imap.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: Sun, 16 Jul 2006 01:31:41 +0200 [thread overview]
Message-ID: <44B97ADD.5000302@gmail.com> (raw)
In-Reply-To: <20060715154200.e9138a6b.akpm@osdl.org>
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)?
Regards,
Michal
--
Michal K. K. Piotrowski
LTG - Linux Testers Group
(http://www.stardust.webpages.pl/ltg/wiki/)
Signed-off-by: Michal Piotrowski <michal.k.k.piotowski@gmail.com>
diff -uprN -X linux-mm/Documentation/dontdiff linux-mm-clean/Documentation/ABI/obsolete/sysctl linux-mm/Documentation/ABI/obsolete/sysctl
--- linux-mm-clean/Documentation/ABI/obsolete/sysctl 1970-01-01 01:00:00.000000000 +0100
+++ linux-mm/Documentation/ABI/obsolete/sysctl 2006-07-16 01:22:51.000000000 +0200
@@ -0,0 +1,15 @@
+What: sys_sysctl
+Date: January 2010
+Contact: Eric W. Biederman <ebiederm@xmission.com>
+Description:
+ sys_sysctl uses binary paths that have been found to be a major
+ pain to maintain and use. The interface in /proc/sys is now
+ the primary and what everyone uses.
+
+ Nothing has been using the binary sysctl interface for some time
+ time now so nothing should break if you disable sysctl syscall
+ support, and you kernel will get marginally smaller.
+
+Users:
+
+date, ls, salsa, showconsole, touch
next prev parent reply other threads:[~2006-07-15 23:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-15 14:40 2.6.18-rc1-mm2: process `showconsole' used the removed sysctl system call Tilman Schmidt
2006-07-15 22:42 ` Andrew Morton
2006-07-15 23:17 ` Eric W. Biederman
2006-07-15 23:31 ` Michal Piotrowski [this message]
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=44B97ADD.5000302@gmail.com \
--to=michal.k.k.piotrowski@gmail.com \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.