History log of /freebsd/sys/kern/kern_sysctl.c (Results 101 – 125 of 628)
Revision (<<< Hide revision tags) (Show revision tags >>>) Date Author Comments
# 11d38a57 28-Oct-2015 Baptiste Daroussin <bapt@FreeBSD.org>

Merge from head

Sponsored by: Gandi.net


# c3220d0b 23-Oct-2015 Conrad Meyer <cem@FreeBSD.org>

Sysctl: Add common support for U8, U16 types

Sponsored by: EMC / Isilon Storage Division


# becbad1f 13-Oct-2015 Baptiste Daroussin <bapt@FreeBSD.org>

Merge from head


# 5a2b666c 01-Oct-2015 Baptiste Daroussin <bapt@FreeBSD.org>

Merge from head


# 0f405ee7 28-Sep-2015 Navdeep Parhar <np@FreeBSD.org>

Sync up with head (up to r288341).


# a1cb6af1 17-Sep-2015 Dimitry Andric <dim@FreeBSD.org>

Merge ^/head r287680 through r287877.


# 7665e341 16-Sep-2015 Mateusz Guzik <mjg@FreeBSD.org>

sysctl: switch sysctllock to a sleepable rmlock, take 2

This restores r285125. Previous attempt was reverted due to a bug in rmlocks,
which is fixed since r287833.


# f94594b3 12-Sep-2015 Baptiste Daroussin <bapt@FreeBSD.org>

Finish merging from head, messed up in previous attempt


# b5ff185e 12-Sep-2015 Baptiste Daroussin <bapt@FreeBSD.org>

Merge from head


# ab875b71 14-Aug-2015 Navdeep Parhar <np@FreeBSD.org>

Catch up with head, primarily for the 1.14.4.0 firmware.


Revision tags: release/10.2.0
# 1347814c 07-Aug-2015 Dimitry Andric <dim@FreeBSD.org>

Merge ^/head r285924 through r286421.


# 4ae1e3c7 30-Jul-2015 Mateusz Guzik <mjg@FreeBSD.org>

Revert r285125 until rmlocks get fixed.

Right now there is a chance that sysctl unregister will cause reader to
block on the sx lock associated with sysctl rmlock, in which case kernels
with debug e

Revert r285125 until rmlocks get fixed.

Right now there is a chance that sysctl unregister will cause reader to
block on the sx lock associated with sysctl rmlock, in which case kernels
with debug enabled will panic.

show more ...


# 635b2e1e 08-Jul-2015 Dimitry Andric <dim@FreeBSD.org>

Merge ^/head r285153 through r285283.


# 6f99ea05 06-Jul-2015 Patrick Kelsey <pkelsey@FreeBSD.org>

Don't acquire sysctlmemlock in userland_sysctl() when the old value
pointer is NULL, as in that case there are no userland pages that
could potentially be wired. It is common for old to be NULL and

Don't acquire sysctlmemlock in userland_sysctl() when the old value
pointer is NULL, as in that case there are no userland pages that
could potentially be wired. It is common for old to be NULL and
oldlenp to be non-NULL in calls to userland_sysctl(), as this is used
to probe for the length of a variable-length sysctl entry before
retrieving a value. Note that it is typical for such calls to be made
with an uninitialized value in *oldlenp, so sysctlmemlock was
essentially being acquired at random (depending on the uninitialized
value in *oldlenp being > PAGE_SIZE or not) for these calls prior to
this patch.

Differential Revision: https://reviews.freebsd.org/D2987
Reviewed by: mjg, kib
Approved by: jmallett (mentor)
MFC after: 1 month

show more ...


# 4cd9b24e 04-Jul-2015 Dimitry Andric <dim@FreeBSD.org>

Merge ^/head r284737 through r285152.


# ee5f66f8 04-Jul-2015 Mateusz Guzik <mjg@FreeBSD.org>

sysctl: get rid of sysctl_lock/unlock

Inline their contents into the only consumer.


# d5fc115a 04-Jul-2015 Mateusz Guzik <mjg@FreeBSD.org>

sysctl: remove a debugging printf which crept in with r285125


# b8633775 04-Jul-2015 Mateusz Guzik <mjg@FreeBSD.org>

sysctl: switch sysctllock to a sleepable rmlock

The lock is almost never taken for writing.


# 416ba5c7 22-Jun-2015 Navdeep Parhar <np@FreeBSD.org>

Catch up with HEAD (r280229-r284686).


# 98e0ffae 27-May-2015 Simon J. Gerraty <sjg@FreeBSD.org>

Merge sync of head


# 4bf53d0b 04-Apr-2015 Baptiste Daroussin <bapt@FreeBSD.org>

Merge from HEAD


# e6e746bf 25-Mar-2015 Glen Barber <gjb@FreeBSD.org>

MFH: r278968-r280640

Sponsored by: The FreeBSD Foundation


# 38668c60 25-Mar-2015 Hans Petter Selasky <hselasky@FreeBSD.org>

Implement a simple OID number garbage collector. Given the increasing
number of dynamically created and destroyed SYSCTLs during runtime it
is very likely that the current new OID number limit of 0x7

Implement a simple OID number garbage collector. Given the increasing
number of dynamically created and destroyed SYSCTLs during runtime it
is very likely that the current new OID number limit of 0x7fffffff can
be reached. Especially if dynamic OID creation and destruction results
from automatic tests. Additional changes:

- Optimize the typical use case by decrementing the next automatic OID
sequence number instead of incrementing it. This saves searching time
when inserting new OIDs into a fresh parent OID node.

- Add simple check for duplicate non-automatic OID numbers.

MFC after: 1 week

show more ...


# 502702c6 24-Mar-2015 Hans Petter Selasky <hselasky@FreeBSD.org>

Make sure tunable sysctls are only fetched once. The existing code can
re-register sysctls when destroying sysctl contexts or when moving
sysctls from one tree to another.


# ab91c9a7 24-Mar-2015 Hans Petter Selasky <hselasky@FreeBSD.org>

Correct string pointer offset for error printout.


12345678910>>...26