From: Andi Kleen <ak@linux.intel.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Amerigo Wang <amwang@redhat.com>,
linux-kernel@vger.kernel.org, Randy Dunlap <rdunlap@xenotime.net>,
Mauro Carvalho Chehab <mchehab@redhat.com>,
Len Brown <len.brown@intel.com>, Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
David Howells <dhowells@redhat.com>,
Eric Paris <eparis@redhat.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Eric Dumazet <eric.dumazet@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Andy Shevchenko <ext-andriy.shevchenko@nokia.com>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH 2/2] sysctl: remove sysctl syscall
Date: Tue, 19 Oct 2010 17:04:37 +0200 [thread overview]
Message-ID: <4CBDB385.6080100@linux.intel.com> (raw)
In-Reply-To: <m1vd4yi977.fsf@fess.ebiederm.org>
> At the time the deprecation was written we nearly we were in the late
> rc's before anything that cared in practice. glibc has stopped even
> providing a sys_sysctl wrapper now.
What matters are old glibc installations, not new ones.
>> I think it's ok to remove the full tables, but keeping
>> a wrapper just for the functionality glibc use(s/d) is still a good
>> idea.
> I think the only problem should be the arm glibc. I don't know if
> it's iopl implementation ever got weened off of this. I tried
> but I didn't have good test machine and submitting patches to
> glibc is much more of a pain than kernel patches.
Eric, I think you have the wrong approach here: it doesn't matter what
new glibc does,
but what any old glibcs do. If any old one uses it we cannot simply
remove it.
> To my knowledge there has never been a version of x86 glibc that
> had problems if sys_sysctl returns -ENOSYS, and glibc proper removed
> even that dependency almost as soon as sys_sysctl was deprecated.
>
AFAIK older glibc didn't use some functionality in the kernel if they
couldn't
figure out the right kernel version. And they were using sysctl for this.
> Last time we discussed this (when I added the compatibility wrapper)
> I couldn't even find a version of glibc that used sysctl, and I could
> not find a distribution old enough that still had a version of glibc
> that used sysctl on x86.
When I did my really old work for sysctl_binary() I ran into this problem.
All glibc binaries on my distribution back then used sysctl.
> We warn on every sys_sysctl value now even the glibc uses and perhaps I
> am blind but I haven't seen any bug reports. So we should be safe
> turning this off.
>
I don't so. I don't think we can that easily break compatibility, sorry.
Binary compatibility is something very important for Linux.
Anyways I'm fine with removing the bulk of the tables, but not the compat
table for the one glibc uses.
I think the code could be a lot simplified and just provide support
for the single kernel version sysctl though (I had a patch to do that
back then)
-Andi
next prev parent reply other threads:[~2010-10-19 15:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-19 8:22 [PATCH 1/2] sysctl: refactor __do_proc_doulongvec_minmax() Amerigo Wang
2010-10-19 8:22 ` [PATCH 2/2] sysctl: remove sysctl syscall Amerigo Wang
2010-10-19 13:22 ` Andi Kleen
2010-10-19 13:49 ` Eric W. Biederman
2010-10-19 15:04 ` Andi Kleen [this message]
2010-10-19 16:00 ` Eric W. Biederman
2010-10-20 6:06 ` Cong Wang
2010-10-20 13:54 ` Eric W. Biederman
2010-10-21 9:26 ` Cong Wang
2010-10-19 14:10 ` Andreas Schwab
2010-10-19 15:05 ` Andi Kleen
2010-10-20 5:41 ` Cong Wang
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=4CBDB385.6080100@linux.intel.com \
--to=ak@linux.intel.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=amwang@redhat.com \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=ebiederm@xmission.com \
--cc=eparis@redhat.com \
--cc=eric.dumazet@gmail.com \
--cc=ext-andriy.shevchenko@nokia.com \
--cc=len.brown@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=mingo@elte.hu \
--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