Re: sysctl in 2.6.24.2 excludes unapproved files from /proc/sys?



On Sat, 01 Mar 2008 02:12:05 +0100, "Peter T. Breuer" said:
A change in 2.6.24.x kernel/sysctl.c seems to exclude exo-kernel drivers
from using the /proc/sys/ interface:


What's a person to do?

Umm.. as a wild guess? Maybe a patch to add entries to the sysctl_check_table
arrays for your sysctl?

They didn't spend their holiday just coming up with this to annoy you - the
checking found a *lot* of entries that were well and truly broken (in the
how-did-it-ever-not-panic sense)...

Yes, it does make it more difficult for out-of-tree modules to create a new
sysctl entry - which is probably just as well, given that there's sysfs and
debugfs and a whole lot of other options as well for userspace-kernel
interaction.

Attachment: pgp6fuEsS4Dxh.pgp
Description: PGP signature



Relevant Pages

  • help me understand /var/log/messages
    ... sysctl: kernel.core_uses_pid = 1 ... these are 'early' entries in messages. ... missing is strange indeed: lo is configured anyway, ... when usb is not working. ...
    (Fedora)
  • Re: Approaching the limit on PV entries, consider increasing either the vm.pmap.shpgperproc or the v
    ... Approaching the limit on PV entries, consider increasing either the vm.pmap.shpgperproc or the vm.pmap.pv_entry_max sysctl. ... medium load and 2GB RAM. ... in many places there is references to rebooting after putting a new vm.pmap.shpgperproc value to loader.conf. ...
    (freebsd-stable)
  • PV entries too small
    ... I get an "Approaching the limits on PV entries, ... all the time when the system gets under heavy load. ... Also it seems to be impossible to set this via sysctl during runtime nor does it show up in sysctl -a. ...
    (freebsd-current)
  • Re: [RFC][PATCH 4/5] utsname namespaces: sysctl hack
    ... All of the networking entries. ... simply won't allow anything in a container to touch it. ... I have a slightly revamped way of doing the sysv namespace sysctl code. ... The proc entries are the real interface, ...
    (Linux-Kernel)
  • [PATCH 6/10] x86 boot: proper use of ARRAY_SIZE instead of repeated E820MAX constant
    ... This patch is motivated by a subsequent patch which will allow for more ... memory map entries on EFI supported systems than can be passed via the x86 ... size for several arrays and loops over those arrays. ... * replaces the original e820 map with a new one, ...
    (Linux-Kernel)