summaryrefslogtreecommitdiffstats
path: root/sys/kern/kern_syscalls.c
Commit message (Collapse)AuthorAgeFilesLines
* Count number of threads that enter and leave dynamically registeredkib2010-06-281-1/+55
| | | | | | | | | | syscalls. On the dynamic syscall deregistration, wait until all threads leave the syscall code. This somewhat increases the safety of the loadable modules unloading. Reviewed by: jhb Tested by: pho MFC after: 1 month
* Introduce SYSCALL_INIT_HELPER and SYSCALL32_INIT_HELPER macros andkib2010-03-191-0/+30
| | | | | | | | | neccessary support functions to allow registering dynamically loaded syscalls from the MOD_LOAD handlers. Helpers handle registration failures semi-automatically. Reviewed by: jhb MFC after: 2 weeks
* Various style fixes. 7 space indent is just odd.jhb2008-09-181-74/+74
|
* Make system call modules a bit more robust:jhb2006-08-011-1/+11
| | | | | | | | | | | | | | | - If we fail to register the system call during MOD_LOAD, then note that so that we don't try to deregister it or invoke the chained event handler during the subsequent MOD_UNLOAD event. Doing the deregister when the register failed could result in trashing system call entries. - Add a SI_SUB_SYSCALLS just before starting up init and use that to register syscall modules instead of SI_SUB_DRIVERS. Registering system calls as late as possible increases the chances that any other module event handlers or SYSINITs in a module are executed to initialize the data in a kld before a syscall dependent on that data is able to be invoked. MFC after: 3 days
* Do a pass over all modules in the kernel and make them return EOPNOTSUPPphk2004-07-151-0/+3
| | | | | | | | for unknown events. A number of modules return EINVAL in this instance, and I have left those alone for now and instead taught MOD_QUIESCE to accept this as "didn't do anything".
* Use __FBSDID().obrien2003-06-111-2/+3
|
* - Lock down the ``module'' structure by adding an SX lock that is used byarr2002-03-181-0/+5
| | | | | | | | | all the global bits of ``module'' data. This commit adds a few generic macros, MOD_SLOCK, MOD_XLOCK, etc., that are meant to be used as ways of accessing the SX lock. It is also the first step in helping to lock down the kernel linker and module systems. Reviewed by: jhb, jake, smp@
* KSE Milestone 2julian2001-09-121-4/+4
| | | | | | | | | | | | | | Note ALL MODULES MUST BE RECOMPILED make the kernel aware that there are smaller units of scheduling than the process. (but only allow one thread per process at this time). This is functionally equivalent to teh previousl -current except that there is a thread associated with each process. Sorry john! (your next MFC will be a doosie!) Reviewed by: peter@freebsd.org, dillon@freebsd.org X-MFC after: ha ha ha ha
* sysvipc loadable.alfred2000-12-011-1/+8
| | | | | | new syscall entry lkmressys - "reserved loadable syscall" Make syscall_register allow overwriting of such entries (lkmressys).
* Trim unused options (or #ifdef for undoc options).peter1999-10-111-5/+0
| | | | Submitted by: phk
* $Id$ -> $FreeBSD$peter1999-08-281-1/+1
|
* Call the chained module handler before unregistering the syscall so thatdfr1999-06-271-5/+12
| | | | | | | errors can be detected. Submitted by: "A.Yu.Isupov" <isupov@moonhe.jinr.ru> PR: kern/12239
* Move lkmnosys() from kern_lkm.c to here.peter1999-01-171-1/+13
|
* Implement a mechanism for a module to report a small amount of moduledfr1999-01-091-1/+4
| | | | | specific data back to the user via kldstat(2). Use that mechanism in the syscall handler to report the syscall number used.
* Implement support for adding syscalls in KLD modules.dfr1999-01-091-0/+94
Submitted by: Assar Westerlund <assar@sics.se>
OpenPOWER on IntegriCloud