Age | Commit message (Collapse) | Author |
|
Tested by many during the past months, thanks!
ok sthen@
|
|
using the new sets of registers.
|
|
names.
|
|
firmare names on Apple M1 Pro/Max and Apple T2 Macs.
|
|
|
|
divisible by 1400, the last chunk isn't marked with an end flag.
ok tobhe@
|
|
will take care of releasing them, as otherwise initialization would
fail some of the time. That chip also contains 3 of these, so make
sure we reset all of them. Necessary on Apple M1 Pro/Max.
|
|
|
|
bindings.
|
|
|
|
|
|
This time unix(4) sockets garbage collector always destroys any socket
with positive "fp->f_count == unp->unp_msgcount" equation. This is wrong
because unix(4) sockets within SCM_RIGHTS message but closed on sender
side also have this equation positive. Such sockets are not in the loop,
and if garbage collector kill them before they are received, we get
kernel panic.
FreeBSD already has garbage collector reworked to fix this issue [1]. The
logic is pretty simple so import it to our garbage collector.
1. https://reviews.freebsd.org/D23142
ok bluhm@
|
|
a few more chips.
|
|
Reported-by: syzbot+7718c5f69c595f76b298@syzkaller.appspotmail.com
OK bluhm@, OK jmatthew@
|
|
the com(4) devices to match the traditional order one the ISA bus.
ok patrick@, anton@
|
|
This is an old issue in pf(4): whenever new interface appears
in IP stack, we must reload pf.conf to apply 'set skip on ...'
to newly plumbed network interfaces. Time has come to fix it.
The idea is to also create pfi_kif for interfaces, which are
referred by 'set skip on ...'. Such pfi_kif instances are
created/destroyed by pfi_set_flags()/pfi_clear_flags().
claudio@ dragged my attention to this in Gouveia. Also his
feedback helped me to put change into shape.
OK claudio@
|
|
without kernel lock. Unlock the two callers in ip6_input_if() that
have been forgotten.
OK mvs@ kn@
|
|
When a tty device is revoked, the associated knotes should be
invalidated. Otherwise the user processes can keep on receiving
events from the device.
It appears tricky to do the invalidation as part of revocation
in a way that does not allow unwanted event registration or clutter
the tty code. For now, make the knotes invalid lazily before delivery.
OK mpi@
|
|
readelf -d for displaying them.
(lld 13 sets DF_1_PIE on most our binaries)
ok jsg@
|
|
ASUS USB-N10 v2, D-Link DWA-127 rev B1, Edimax EW-7711UAn v2,
various Ralink/MediaTek ids.
ok stsp@
|
|
OK mpi@
|
|
|
|
ASUS USB-N10 v2, D-Link DWA-127 rev B1, Edimax EW-7711UAn v2,
various Ralink/MediaTek ids.
ok stsp@
|
|
ok kettenis@
|
|
found by clang 13; OK tobhe@
|
|
GPIO base register we must not replace the iterator variable with the
index of the pin inside the register.
ok kettenis@
|
|
|
|
Switch libc and ld.so to the generic stubs for these calls.
WARNING: reboot to updated kernel before installing libc or ld.so!
Time for a story...
When gcc (back in 1.x days) first implemented long long, it didn't (always)
pass 64bit arguments in 'aligned' registers/stack slots, with the result that
argument offsets didn't match structure offsets. This affected the nine system
calls that pass off_t arguments:
ftruncate lseek mmap mquery pread preadv pwrite pwritev truncate
To avoid having to do custom ASM wrappers for those, BSD put an explicit pad
argument in so that the off_t argument would always start on a even slot and
thus be naturally aligned. Thus those odd wrappers in lib/libc/sys/ that use
__syscall() and pass an extra '0' argument.
The ABIs for different CPUs eventually settled how things should be passed on
each and gcc 2.x followed them. The only arch now where it helps is landisk,
which needs to skip the last argument register if it would be the first half of
a 64bit argument. So: add new syscalls without the pad argument and on landisk
do that skipping directly in the syscall handler in the kernel. Keep compat
support for the existing syscalls long enough for the transition.
ok deraadt@
|
|
dirty hacks, it is better to protect IPsec input and output with
kernel lock. Not much is lost as crypto needs the kernel lock
anyway. From here we can refine the lock later.
Note that there is no kernel lock in the SPD lockup path. Goal is
to keep that lock free to allow fast forwarding with non IPsec
traffic.
tested by Hrvoje Popovski; OK tobhe@
|
|
|
|
OK anton@
|
|
in vnd ioctl error path.
Reported-by: syzbot+6dde3fda33074a256318@syzkaller.appspotmail.com
OK jsg@ anton@
|
|
if it is supported. Remove it from the global GENERIC config.
OK visa@ claudio@
|
|
missed when unix2dosfn() was changed with msdosfs_conv.c rev 1.15 in 2012
|
|
ok claudio@
|
|
allocated memory could be too short for the list of disks. Retry
allocating enough space until it did not change.
The disk list and duid memory are protected by kernel lock. Use
asserts to mark this explicitly.
Reported-by: syzbot+807423f6868bbfb836bc@syzkaller.appspotmail.com
OK anton@ mpi@
|
|
reliability when bwfm is used as an access point.
ok patrick@
|
|
per packet and improve readability.
ok bluhm@
|
|
From Le Ma
aec5897b277b13acd8f913d777654d4d092a24f1 in linux 5.10.y/5.10.88
f3a8076eb28cae1553958c629aecec479394bbe2 in mainline linux
|
|
From Lang Yu
222cebd995cdf11fe0d502749560f65e64990e55 in linux 5.10.y/5.10.88
aa464957f7e660abd554f2546a588f6533720e21 in mainline linux
|
|
|
|
Pass the correct entry to uvm_fault_unwire_locked().
Reported-by: syzbot+bb2f63f076618e9ed0d3@syzkaller.appspotmail.com
ok kettenis@, deraadt@
|
|
ok anton@, deraadt@
|
|
|
|
is enabled by default, this line does not provide much information.
requested by kettenis@ deraadt@; OK mpi@
|
|
ok anton@
|
|
kern.shminfo.shmseg is set to something ridiculously large.
ok kettenis@ millert@
Reported-by: syzbot+9f1b201cdbc97b19c7f5@syzkaller.appspotmail.com
|
|
vnode twice in the error path.
Tested in snaps for a couple of days.
|
|
not before as we might end up sleeping while acquiring the lock,
introducing a potential race.
Tested in snaps for a couple of days.
ok mpi@
Reported-by: syzbot+c87cdc2905b441c20d39@syzkaller.appspotmail.com
|
|
already does.
|