#
b272101a |
| 30-Oct-2023 |
Aaron LI <aly@aaronly.me> |
Various minor whitespace cleanups
Accumulated along the way.
|
#
05d02a38 |
| 28-Dec-2023 |
Aaron LI <aly@aaronly.me> |
kernel: Remove unnecessary casts for updated mbuf(9) functions
|
#
8bc4b666 |
| 14-Nov-2023 |
Aaron LI <aly@aaronly.me> |
Minor cleanups to 'sruct domain' definitions
|
#
2b3f93ea |
| 13-Oct-2023 |
Matthew Dillon <dillon@apollo.backplane.com> |
kernel - Add per-process capability-based restrictions
* This new system allows userland to set capability restrictions which turns off numerous kernel features and root accesses. These restricti
kernel - Add per-process capability-based restrictions
* This new system allows userland to set capability restrictions which turns off numerous kernel features and root accesses. These restrictions are inherited by sub-processes recursively. Once set, restrictions cannot be removed.
Basic restrictions that mimic an unadorned jail can be enabled without creating a jail, but generally speaking real security also requires creating a chrooted filesystem topology, and a jail is still needed to really segregate processes from each other. If you do so, however, you can (for example) disable mount/umount and most global root-only features.
* Add new system calls and a manual page for syscap_get(2) and syscap_set(2)
* Add sys/caps.h
* Add the "setcaps" userland utility and manual page.
* Remove priv.9 and the priv_check infrastructure, replacing it with a newly designed caps infrastructure.
* The intention is to add path restriction lists and similar features to improve jailess security in the near future, and to optimize the priv_check code.
show more ...
|
Revision tags: v6.4.0, v6.4.0rc1, v6.5.0, v6.2.2, v6.2.1, v6.3.0, v6.0.1, v6.0.0, v6.0.0rc1, v6.1.0, v5.8.3, v5.8.2, v5.8.1, v5.8.0, v5.9.0, v5.8.0rc1, v5.6.3, v5.6.2 |
|
#
7eaeff3d |
| 07-Aug-2019 |
Roy Marples <roy@marples.name> |
socket: introduce SO_RERROR to detect receive buffer overflow
kernel receive buffers are initially of a limited size and generally the network protocols that use them don't care if a packet gets los
socket: introduce SO_RERROR to detect receive buffer overflow
kernel receive buffers are initially of a limited size and generally the network protocols that use them don't care if a packet gets lost.
However some users do care about lost messages even if not baked into the protocol - such as consumers of route(4) to track state.
POSIX states that read(2) can return an error of ENOBUFS so return this error code when an overflow is detected. Guard this with socket option SO_RERROR so that existing applications which do not care can carry on not caring by default.
Taken-from: NetBSD Reviewed-by: sephe
show more ...
|
Revision tags: v5.6.1, v5.6.0, v5.6.0rc1, v5.7.0, v5.4.3, v5.4.2, v5.4.1, v5.4.0, v5.5.0, v5.4.0rc1, v5.2.2, v5.2.1, v5.2.0, v5.3.0, v5.2.0rc, v5.0.2, v5.0.1, v5.0.0, v5.0.0rc2, v5.1.0, v5.0.0rc1, v4.8.1, v4.8.0, v4.6.2, v4.9.0, v4.8.0rc, v4.6.1 |
|
#
afd2da4d |
| 03-Aug-2016 |
Matthew Dillon <dillon@apollo.backplane.com> |
kernel - Remove PG_ZERO and zeroidle (page-zeroing) entirely
* Remove the PG_ZERO flag and remove all page-zeroing optimizations, entirely. Aftering doing a substantial amount of testing, these
kernel - Remove PG_ZERO and zeroidle (page-zeroing) entirely
* Remove the PG_ZERO flag and remove all page-zeroing optimizations, entirely. Aftering doing a substantial amount of testing, these optimizations, which existed all the way back to CSRG BSD, no longer provide any benefit on a modern system.
- Pre-zeroing a page only takes 80ns on a modern cpu. vm_fault overhead in general is ~at least 1 microscond.
- Pre-zeroing a page leads to a cold-cache case on-use, forcing the fault source (e.g. a userland program) to actually get the data from main memory in its likely immediate use of the faulted page, reducing performance.
- Zeroing the page at fault-time is actually more optimal because it does not require any reading of dynamic ram and leaves the cache hot.
- Multiple synth and build tests show that active idle-time zeroing of pages actually reduces performance somewhat and incidental allocations of already-zerod pages (from page-table tear-downs) do not affect performance in any meaningful way.
* Remove bcopyi() and obbcopy() -> collapse into bcopy(). These other versions existed because bcopy() used to be specially-optimized and could not be used in all situations. That is no longer true.
* Remove bcopy function pointer argument to m_devget(). It is no longer used. This function existed to help support ancient drivers which might have needed a special memory copy to read and write mapped data. It has long been supplanted by BUSDMA.
show more ...
|
Revision tags: v4.6.0, v4.6.0rc2, v4.6.0rc, v4.7.0, v4.4.3, v4.4.2, v4.4.1, v4.4.0, v4.5.0, v4.4.0rc |
|
#
b2244ed9 |
| 15-Sep-2015 |
Sepherosa Ziehau <sephe@dragonflybsd.org> |
kernel: Use fhold() instead of increasing f_count manually
|
Revision tags: v4.2.4, v4.3.1, v4.2.3, v4.2.1, v4.2.0, v4.0.6, v4.3.0, v4.2.0rc, v4.0.5, v4.0.4, v4.0.3, v4.0.2, v4.0.1, v4.0.0, v4.0.0rc3, v4.0.0rc2, v4.0.0rc, v4.1.0, v3.8.2, v3.8.1, v3.6.3, v3.8.0, v3.8.0rc2, v3.9.0, v3.8.0rc, v3.6.2, v3.6.1, v3.6.0, v3.7.1, v3.6.0rc, v3.4.3, v3.4.2, v3.4.1, v3.4.0, v3.4.0rc, v3.5.0, v3.2.2, v3.2.1, v3.2.0, v3.3.0, v3.0.3, v3.0.2, v3.0.1, v3.1.0, v3.0.0 |
|
#
4090d6ff |
| 03-Jan-2012 |
Sascha Wildner <saw@online.de> |
kernel: Use NULL for pointers.
|
#
884717e1 |
| 06-Dec-2011 |
Sascha Wildner <saw@online.de> |
kernel: Replace all usage of MALLOC()/FREE() with kmalloc()/kfree().
|
#
86d7f5d3 |
| 26-Nov-2011 |
John Marino <draco@marino.st> |
Initial import of binutils 2.22 on the new vendor branch
Future versions of binutils will also reside on this branch rather than continuing to create new binutils branches for each new version.
|
Revision tags: v2.12.0, v2.13.0, v2.10.1, v2.11.0, v2.10.0, v2.9.1, v2.8.2, v2.8.1, v2.8.0, v2.9.0, v2.6.3, v2.7.3, v2.6.2, v2.7.2, v2.7.1, v2.6.1, v2.7.0, v2.6.0, v2.5.1, v2.4.1, v2.5.0, v2.4.0, v2.3.2, v2.3.1, v2.2.1, v2.2.0, v2.3.0 |
|
#
08abcb65 |
| 03-Jan-2009 |
Matthew Dillon <dillon@apollo.backplane.com> |
Merge branch 'master' of ssh://crater.dragonflybsd.org/repository/git/dragonfly into devel
|
#
4173863d |
| 30-Dec-2008 |
Matthias Schmidt <matthias@dragonflybsd.org> |
Merge branch 'master' of git://chlamydia.fs.ei.tum.de/dragonfly
|
#
8a27f1c9 |
| 31-Dec-2008 |
Michael Neumann <mneumann@ntecs.de> |
Merge branches 'master' and 'suser_to_priv'
Conflicts:
sys/netinet/ip_carp.c sys/platform/pc64/amd64/machdep.c
|
#
895c1f85 |
| 15-Dec-2008 |
Michael Neumann <mneumann@ntecs.de> |
suser_* to priv_* conversion
|
Revision tags: v2.1.1 |
|
#
716da958 |
| 01-Nov-2008 |
Sepherosa Ziehau <sephe@dragonflybsd.org> |
Install pr_ctlport for the rest of the protocols.
Reported-by: tomas@
|
Revision tags: v2.0.1 |
|
#
978400d3 |
| 06-Jan-2008 |
Sascha Wildner <swildner@dragonflybsd.org> |
Remove bogus checks after kmalloc(M_WAITOK) which never returns NULL.
Reviewed-by: hasso
|
#
e7b4468c |
| 05-Jan-2008 |
Sascha Wildner <swildner@dragonflybsd.org> |
For kmalloc(), MALLOC() and contigmalloc(), use M_ZERO instead of explicitly bzero()ing.
Reviewed-by: sephe
|
#
f15ba1a8 |
| 03-Jun-2007 |
Matthew Dillon <dillon@dragonflybsd.org> |
Catch up a bit with FreeBSD netgraph by replacing *LEN constants with *SIZ constants which already account space for trailing '\0's.
Submitted-by: "Nuno Antunes" <nuno.antunes@gmail.com> Obtained fr
Catch up a bit with FreeBSD netgraph by replacing *LEN constants with *SIZ constants which already account space for trailing '\0's.
Submitted-by: "Nuno Antunes" <nuno.antunes@gmail.com> Obtained from: FreeBSD (sorta).
show more ...
|
#
6d49aa6f |
| 22-Apr-2007 |
Matthew Dillon <dillon@dragonflybsd.org> |
Give the sockbuf structure its own header file and supporting source file. Move all sockbuf-specific functions from kern/uipc_socket2.c into the new kern/uipc_sockbuf.c and move all the sockbuf-speci
Give the sockbuf structure its own header file and supporting source file. Move all sockbuf-specific functions from kern/uipc_socket2.c into the new kern/uipc_sockbuf.c and move all the sockbuf-specific structures from sys/socketvar.h to sys/sockbuf.h.
Change the sockbuf structure to only contain those fields required to properly management a chain of mbufs. Create a signalsockbuf structure to hold the remaining fields (e.g. selinfo, mbmax, etc).
Change the so_rcv and so_snd structures in the struct socket from a sockbuf to a signalsockbuf.
Remove the recently added sorecv_direct structure which was being used to provide a direct mbuf path to consumers for socket I/O. Use the newly revamped sockbuf base structure instead. This gives mbuf consumers direct access to the sockbuf API functions for use outside of a struct socket. This will also allow new API functions to be added to the sockbuf interface to ease the job of parsing data out of chained mbufs.
show more ...
|
#
fa5e758c |
| 21-Apr-2007 |
Matthew Dillon <dillon@dragonflybsd.org> |
Convert all pr_usrreqs structure initializations to the .name = data format.
|
#
0679adc4 |
| 22-Jun-2005 |
Matthew Dillon <dillon@dragonflybsd.org> |
File descriptor cleanup stage 2, remove the separate arrays for file pointers, fileflags, and allocation counts and replace the mess with a single structural array. Also revamp the code that checks
File descriptor cleanup stage 2, remove the separate arrays for file pointers, fileflags, and allocation counts and replace the mess with a single structural array. Also revamp the code that checks whether the file descriptor array is built-in or allocated.
Note that the removed malloc's were doing something weird, allocating 'nf * OFILESIZE + 1' bytes instead of 'nf * OFILESIZE' bytes. I could not find any reason at all why it was doing that. It's gone now anyway.
show more ...
|
#
41e90fed |
| 02-Jun-2005 |
Sascha Wildner <swildner@dragonflybsd.org> |
Remove spl*() calls in netgraph and replace them with critical sections.
|
#
9c70fe43 |
| 04-Mar-2005 |
Jeffrey Hsu <hsu@dragonflybsd.org> |
Convert the struct domain next pointer to an SLIST.
|
#
5e2195bf |
| 17-Feb-2005 |
Joerg Sonnenberger <joerg@dragonflybsd.org> |
GCC supports two pseudo variables to get the function name, __FUNCTION__ and __func__. The latter is C99, prefer that.
|
#
9eeaa8a9 |
| 06-Mar-2004 |
Jeffrey Hsu <hsu@dragonflybsd.org> |
Dispatch upper-half protocol request handling.
|