src/sys/kern/kern_osd.c, branch upstream/11.0.0FreeBSD source treehttps://cgit-dev.freebsd.org/src/atom?h=upstream%2F11.0.02016-04-26T19:57:35Zosd(9): Change array pointer to array pointer type from void*2016-04-26T19:57:35ZConrad Meyercem@FreeBSD.org2016-04-26T19:57:35Zurn:sha1:aa90aec2703c8c85e4109f6714bea675b29fcf75
This is a minor follow-up to r297422, prompted by a Coverity warning. (It's
not a real defect, just a code smell.) OSD slot array reservations are an
array of pointers (void **) but were cast to void* and back unnecessarily.
Keep the correct type from reservation to use.
osd.9 is updated to match, along with a few trivial igor fixes.
Reported by: Coverity
CID: 1353811
Sponsored by: EMC / Isilon Storage Division
Add osd_reserve() and osd_set_reserved(), which allow M_WAITOK allocation2016-03-30T16:57:28ZJamie Grittonjamie@FreeBSD.org2016-03-30T16:57:28Zurn:sha1:320d8421018097b8036064db704edeedfc97d7a4
of an OSD array,
Move the various per-type arrays of OSD data into a single structure array.2016-03-28T22:18:37ZJamie Grittonjamie@FreeBSD.org2016-03-28T22:18:37Zurn:sha1:859f4d06112d80b010536d79ae886e4649d4f486Pull in r267961 and r267973 again. Fix for issues reported will follow.2014-06-28T03:56:17ZHans Petter Selaskyhselasky@FreeBSD.org2014-06-28T03:56:17Zurn:sha1:af3b2549c4ba2ef00a7cbb4cb6836598bf0aefbeRevert r267961, r267973:2014-06-27T22:05:21ZGlen Barbergjb@FreeBSD.org2014-06-27T22:05:21Zurn:sha1:37a107a407cdb47ee0f4c4337e369e9973b34076
These changes prevent sysctl(8) from returning proper output,
such as:
1) no output from sysctl(8)
2) erroneously returning ENOMEM with tools like truss(1)
or uname(1)
truss: can not get etype: Cannot allocate memory
Extend the meaning of the CTLFLAG_TUN flag to automatically check if2014-06-27T16:33:43ZHans Petter Selaskyhselasky@FreeBSD.org2014-06-27T16:33:43Zurn:sha1:3da1cf1e88f8448bb10c5f778ab56ff65c7a6938
there is an environment variable which shall initialize the SYSCTL
during early boot. This works for all SYSCTL types both statically and
dynamically created ones, except for the SYSCTL NODE type and SYSCTLs
which belong to VNETs. A new flag, CTLFLAG_NOFETCH, has been added to
be used in the case a tunable sysctl has a custom initialisation
function allowing the sysctl to still be marked as a tunable. The
kernel SYSCTL API is mostly the same, with a few exceptions for some
special operations like iterating childrens of a static/extern SYSCTL
node. This operation should probably be made into a factored out
common macro, hence some device drivers use this. The reason for
changing the SYSCTL API was the need for a SYSCTL parent OID pointer
and not only the SYSCTL parent OID list pointer in order to quickly
generate the sysctl path. The motivation behind this patch is to avoid
parameter loading cludges inside the OFED driver subsystem. Instead of
adding special code to the OFED driver subsystem to post-load tunables
into dynamically created sysctls, we generalize this in the kernel.
Other changes:
- Corrected a possibly incorrect sysctl name from "hw.cbb.intr_mask"
to "hw.pcic.intr_mask".
- Removed redundant TUNABLE statements throughout the kernel.
- Some minor code rewrites in connection to removing not needed
TUNABLE statements.
- Added a missing SYSCTL_DECL().
- Wrapped two very long lines.
- Avoid malloc()/free() inside sysctl string handling, in case it is
called to initialize a sysctl from a tunable, hence malloc()/free() is
not ready when sysctls from the sysctl dataset are registered.
- Bumped FreeBSD version to indicate SYSCTL API change.
MFC after: 2 weeks
Sponsored by: Mellanox Technologies
Make the rmlock(9) interface a bit more like the rwlock(9) interface:2009-05-29T10:52:37ZRobert Watsonrwatson@FreeBSD.org2009-05-29T10:52:37Zurn:sha1:1a109c1cb0ef3176d2d32e11d8a51d48248bd2e5
- Add rm_init_flags() and accept extended options only for that variation.
- Add a flags space specifically for rm_init_flags(), rather than borrowing
the lock_init() flag space.
- Define flag RM_RECURSE to use instead of LO_RECURSABLE.
- Define flag RM_NOWITNESS to allow an rmlock to be exempt from WITNESS
checking; this wasn't possible previously as rm_init() always passed
LO_WITNESS when initializing an rmlock's struct lock.
- Add RM_SYSINIT_FLAGS().
- Rename embedded mutex in rmlocks to make it more obvious what it is.
- Update consumers.
- Update man page.
Add a constant PR_MAXMETHOD to better define the jail/OSD interface.2009-05-05T05:49:08ZJamie Grittonjamie@FreeBSD.org2009-05-05T05:49:08Zurn:sha1:49939083a0543593d9c2729c7d5a835cfb0ac2dd
Reviewed by: dchagin, kib
Approved by: bz (mentor)
Don't call the OSD destructor if the data slot is NULL2009-04-30T22:43:21ZJamie Grittonjamie@FreeBSD.org2009-04-30T22:43:21Zurn:sha1:3dd4fac97c377820c583cdce806e0761f2e30486
(since it's already not done on unused slots, which are indistinguishable
to the caller).
Approved by: bz (mentor)
Introduce the extensible jail framework, using the same "name=value"2009-04-29T21:14:15ZJamie Grittonjamie@FreeBSD.org2009-04-29T21:14:15Zurn:sha1:b38ff370e42160ae27588ba153f3a80d6f07d969
interface as nmount(2). Three new system calls are added:
* jail_set, to create jails and change the parameters of existing jails.
This replaces jail(2).
* jail_get, to read the parameters of existing jails. This replaces the
security.jail.list sysctl.
* jail_remove to kill off a jail's processes and remove the jail.
Most jail parameters may now be changed after creation, and jails may be
set to exist without any attached processes. The current jail(2) system
call still exists, though it is now a stub to jail_set(2).
Approved by: bz (mentor)