| Age | Commit message (Collapse) | Author |
|
check into the inline functions as well the fourth argument for
bpf_attach.
|
|
module which is linked into the kernel and cannot be unloaded.
The main purpose is to get the proper constructors run and create
any /dev nodes necessary for said component. Once more of the
kernel (e.g. networking stack and device drivers) are converted to
MODULE and devfs pops up from somewhere, rump components can be
retired.
|
|
|
|
in libs built with binutils >=2.19. This is a less error-prone
method than the previous where components had to be tagged in the
Makefile as modules (and if they weren't, things broke. and vice
versa).
|
|
stack array isn't large enough.
|
|
to a socket. This happens e.g. when copying large files to SMBFS.
Code reviewed by Antti Kantee.
|
|
|
|
|
|
for orphaned sections to using PROVIDE. What this means is that
unless a rump component internally references that symbol, it will
not be included in the component shared library, and hence cannot
be referenced when the component is loaded. Add a workaround which
works both with 2.16 and 2.19: force a reference to the __start
symbol internally and hence retain it in the resulting library.
|
|
* check for errno before more costly checks
|
|
are present. This works in userspace as opposed relying in link
sets, which fail miserably. Later, when the networking stack
becomes modularized, we can move to a dynamic scheme like with file
systems.
Also, this change allows us to do proper autoconfig, namely attach
the loopback interface iff it is present.
|
|
|
|
non-connected sockets.
|
|
|
|
(it might be a better to chain a few clusters into the iov
instead of just one since we are making the syscall anyway)
* don't overwrite the useful error value
|
|
|
|
* soisdisconnected() TCP sockets if read returns a non-transient error or 0
|
|
|
|
|
|
it's required for rump_nfs to work, but I guess I lost it somewhere.
(yes, it should actually be implemented also)
|
|
|
|
|
|
|
|
|
|
accept etc. is not supported yet. Disconnect is not really supported
either, but doesn't matter in most cases.
|
|
which delegates the work to host kernel sockets. This does not
run the entire kernel TCP/IP stack in userspace and therefore does
not require the ability to send or receive raw packets. This
implies that root priviledges are not required. As already said
above, only supports UDPv4 for now. Extending should be easy.
|