From: ebiederm@xmission.com (Eric W. Biederman)
To: "Randy.Dunlap" <rdunlap@xenotime.net>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sysctl: Allow /proc/sys without sys_sysctl
Date: Mon, 10 Jul 2006 22:00:23 -0600 [thread overview]
Message-ID: <m1zmfgkcyw.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <20060710154849.cdfa74cd.rdunlap@xenotime.net> (Randy Dunlap's message of "Mon, 10 Jul 2006 15:48:49 -0700")
"Randy.Dunlap" <rdunlap@xenotime.net> writes:
> On Mon, 10 Jul 2006 16:38:59 -0600 Eric W. Biederman wrote:
>
>>
>> Since sys_sysctl is deprecated start allow it to be compiled out.
>> This should catch any remaining user space code that cares,
>> and paves the way for further sysctl cleanups.
>
> Where is it documented and users notified that sys_sysctl is
> deprecated? Sounds like it should be added to
> Documentation/feature-removal-schedule.txt.
The deprecation I believe actually predates feature-remove-schedule.txt
>From include/linux/sysctl.h
> ****************************************************************
> ****************************************************************
> **
> ** The values in this file are exported to user space via
> ** the sysctl() binary interface. However this interface
> ** is unstable and deprecated and will be removed in the future.
> ** For a stable interface use /proc/sys.
> **
> ****************************************************************
> ****************************************************************
And I can't actually find any user space applications that continue
to use sys_sysctl.
So the combination of the two patches and makes the deprecation official,
and makes it a compile time option so we can disable sys_sysctl now,
but still have recourse if some parts of user space need the code.
Currently the we dup the internal helpers which makes maintenance
of the code a nightmare.
Eric
next prev parent reply other threads:[~2006-07-11 4:01 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-10 22:38 Eric W. Biederman
2006-07-10 22:48 ` Randy.Dunlap
2006-07-11 4:00 ` Eric W. Biederman [this message]
2006-07-11 4:19 ` Andrew Morton
2006-07-11 6:57 ` Eric W. Biederman
2006-07-11 7:04 ` Andrew Morton
2006-07-11 7:52 ` Eric W. Biederman
2006-07-11 8:05 ` Andrew Morton
2006-07-11 7:23 ` [PATCH] sysctl: Scream if someone uses sys_sysctl Eric W. Biederman
2006-07-11 22:26 ` [PATCH] sysctl: Allow /proc/sys without sys_sysctl Andi Kleen
2006-07-12 3:13 ` Eric W. Biederman
2006-07-12 13:32 ` Andi Kleen
2006-07-12 14:47 ` Eric W. Biederman
2006-07-12 14:52 ` Andi Kleen
2006-07-12 15:32 ` Eric W. Biederman
2006-07-12 16:08 ` Andi Kleen
2006-07-12 16:36 ` Eric W. Biederman
2006-07-12 18:24 ` Stephen Hemminger
2006-07-12 19:58 ` Arjan van de Ven
2006-07-13 0:52 ` Theodore Tso
2006-07-14 20:09 ` H. Peter Anvin
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=m1zmfgkcyw.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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®