| Age | Commit message (Collapse) | Author |
|---|
|
torture tested on amd64, i386 and macppc
ok beck mpi stefan
"the change looks right" deraadt
|
|
our own.
From Michal Mazurek, ok mmcc@
|
|
|
|
- modify B_DMA handling to be in vfs_biomem.c
- change buffer allocation to try allocations with NOWAIT and to throw away clean pages
if allocation fails - allocate with WAITOK only if you can't throw away enough pages to
succeed
"probably sound" deraadt@
|
|
set and get parameters. This is much simpler.
ok semarie, armani, tweaks from jmc
|
|
prepend chroot value *after* canonization and not before.
|
|
order ("a += b > c" is the same as "a += (b > c)" which is wrong here)
ok jca@
|
|
All its callers got reviewed and converted to
use uiomove() properly.
ok deraadt@
|
|
ok beck@ deraadt@
|
|
considered.
ok deraadt@
|
|
|
|
|
|
it factorizes path resolution in resolvpath() function, and use it in
sys_pledge() and pledge_namei().
please note that wl_paths is still disabled.
|
|
- rewrite canonpath() to not require extra byte before shrinking
- make canonpath() error not fatal for the caller (proposition from tedu@)
ok millert@ tedu@ deraadt@
|
|
So if vop_generic_revoke() does not unmount because the mount point
is busy, this could result in a mount point without a valid device.
It is better to check and sleep in a loop to avoid a corrupt mount
point.
OK natano@ krw@
|
|
from Michal Mazurek
|
|
don't want to change the current value"
it changes only the `request' argument behaviour when NULL is passed:
previously it was traited as "" was passed.
with help from jmc@ for man-page
OK tb@ on previous version
|
|
of the hibernate path and starts preparing for some other work in here
|
|
|
|
|
|
ok mpi@ millert@
|
|
for generating and parsing them.
ok mpi@ naddy@ millert@ deraadt@
|
|
in the buffer cache.
When the Dynamic Buffer Cache has been introduced bread_cluster()
became the replacement of cluster_read(). However this function
did not consider the B_CACHE flag of the first buffer of a cluster
like its predecessor did.
This improves a lot read operations on MSDOSFS while reducing the
number of DMA operations.
ok beck@
|
|
them in sys/proc.h has been removed with compat_linux
diff from Michal Mazurek (akfaew (at) jasminek.net)
|
|
|
|
the XXX has been there since 1.1, even back in netbsd, and im too
lazy to go back further to try and see why it is there. either way
it is meaningless.
suggested by mikeb@ and mpi@
|
|
link_maxhdr is best explained as the space reserved before an ip
packet payload for link headers, the most common of which is ethernet.
16 was a good choice when the only traffic we really did was ip
over ethernet, but now there are commonly used transports that are
bigger, specifically 802.11 traffic and vlan/vlan encapsulations,
that justify bumping it up.
i chose 64 because it would also allow enough space for encapsulations
like etherip or gif.
this reduces the size of the smallest packet that can fit into an
mbuf before more storage needs to be suffixed, but because most
traffic is either full sized (ie, already bigger than a single mbuf)
or tiny packets (think tcp ACKS, keystrokes over ssh, or dns requests)
the impact is negligible.
ok stsp@ mpi@ sthen@ mikeb@
|
|
compat/common/compat_util.c to dev/systrace.c, the one place they
are used, and remove the remaining kernel references to compat/*.
ok visa@
|
|
emulations left; ok millert@ deraadt@, jmc@ (man pages)
|
|
Remove "option COMPAT_LINUX" and everything directly tied to it from the
kernel and the corresponding man page documentation.
ok visa@ guenther@
|
|
if a physical interface receives a multicast/broadcast packet and
has carp interfaces on it, that packet needs to be copied for
reception by each of those carp interfaces.
previously it was using m_copym2, but that doesn't respect the
alignment of the source packet. this meant the ip header in the
copies were aligned incorrectly for the network stack, which breaks
strict alignment archs.
m_dup_pkt lets carp specify that the payload needs an ETHER_ALIGN
adjustment, so the ip header inside will be aligned correctly.
reported and tested by anthony eden who hit this on armv7
i reproduced the problem on sparc64 and verified the fix on amd64
and sparc64
ok mpi@ mikeb@ deraadt@
|
|
not a tty. Fixes a pledge failure in telnet when piping the output.
OK deraadt@
|
|
says. Move code belonging to diagnostics in the #ifdef DIAGNOSTIC part
and add a KASSERT that makes sure that we do not run beyond uio_iov.
Diff from Martin Natano.
|
|
|
|
ok mpi@
|
|
OK sthen@
|
|
|
|
preventing integer truncation.
Diff from Martin Natano
ok kettenis@
|
|
usb devices) and return ENOTTY rather than terminating the
caller program. Found by Michael Reed <m.reed at mykolab.com>
ok semarie, deraadt
|
|
|
|
ok millert@
|
|
the socket type and dlg@ is interested in the pointers for ddb show
socket.
OK deraadt@ dlg@
|
|
ok mpi@ bluhm@
|
|
|
|
should help inspecting socket issues in the future.
enthusiasm from mpi@ bluhm@ deraadt@
|
|
Use 115200 the default speed for buffer sizing in ttymalloc(). A lot
of devices call ttymalloc(0) so this affects quite a few of them.
Increases the buffer size for 9600 < baud <= 115200 from 1k to 4k.
Make ppp use the lo/hi watermarks from the tty layer which are
adjusted according to speed + buffer size. The previous fixed values
of 100 and 400 were way too small
Make pty call ttymalloc() with baud == 1000000, which is the common
value used in the tree for "fast".
ok deraadt@
|
|
and somove() panic messages.
OK phessler@ benno@ deraadt@ mpi@
|
|
ok deraadt@
|
|
The current code has already setted it by default since 1.74
any pledge failure tries to make a coredump (default rules for coredump still
applies: so setuid binaries don't create them locally).
ok deraadt@
|
|
This will allow to pledge vmd(8)'s vmm and vm processes, so that VMs
themselves run "sandboxed", including their host-side virtio layer.
It will remain disabled for now (in userland) to not get into the way
of ongoing development and upcoming changes in vmd and the ioctl
interface.
OK mlarkin@ deraadt@ "kernel side in, but not the callers in userland"
|
