lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 09 Nov 2009 10:38:05 +0100
From:	Andi Kleen <>
To: (Eric W. Biederman)
Cc:	Arjan van de Ven <>,
Subject: Re: [PATCH 22/23] sysctl arm: Remove binary sysctl support (Eric W. Biederman) writes:
> The glibc pthread code that uses sysctl has no problems if sys_sysctl
> is gone.  It both falls back to reading /proc/sys and it just controls
> an optimization and the code works with either result.  Been there,
> done that.

/proc/sys is much slower than sysctl though. So you made program startup

Also I agree with Arjan that breaking such a common ABI is not
really a good idea. But I think it's enough to only handle
common sysctls that are actually used, which are very few.

It would be better to simply keep the commonly used binary sysctls
as emulation around always (commonly = used by glibc and perhaps
added by user printk feedback) That's very cheap because it's just
a simple translation and can be done internally cheaper than going
through the VFS with a bazillion of locks.


-- -- Speaking for myself only.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists