From: ebiederm@xmission.com (Eric W. Biederman)
To: Andi Kleen <ak@suse.de>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] sysctl: Allow /proc/sys without sys_sysctl
Date: Tue, 11 Jul 2006 21:13:51 -0600 [thread overview]
Message-ID: <m1sll7ecr4.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <p73ac7fok13.fsf@verdi.suse.de> (Andi Kleen's message of "12 Jul 2006 00:26:32 +0200")
Andi Kleen <ak@suse.de> writes:
> ebiederm@xmission.com (Eric W. Biederman) writes:
>
>> Since sys_sysctl is deprecated start allow it to be compiled out.
>> This should catch any remaining user space code that cares,
>
> I tried this long ago, but found that glibc uses sysctl in each
> program to get the kernel version. It probably handles ENOSYS,
> but there might be slowdowns or subtle problems from it not knowing
> the kernel version.
>
> So I think it's ok to remove the big sysctl, but at a very minimal
> replacement that just handles (CTL_KERN, KERN_VERSION) is needed.
If glibc is looking at kernel.osrelease it might make sense.
If glibc is looking at kernel.version which is just the build number
and date I can't imagine a correct usage.
If this usage is still common in glibc we can decide what to do
when the warnings pop up.
> Also it's useful to printk for the rest at least for some time
> so we know what uses it.
Yes. Andrew and I discussed that and when he picked up a patch.
A printk was added to warn of people using the interface.
Eric
next prev parent reply other threads:[~2006-07-12 3:14 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
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 [this message]
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=m1sll7ecr4.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
/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
Powered by JetHome