Age | Commit message (Collapse) | Author |
|
|
|
- Eliminate the redundant bits of code for MTU handling; From Brad
|
|
to accomodate a wide character. GitHub issue 2336.
|
|
llvm 9 and later take more care not to inline cmpxchg8b/cx8 with
-march=i486 instead calling __atomic_* functions. This in turn breaks
the build of a large number of ports.
To avoid having to add a lock or conditionally building individual ports
with -march=i586 change the default so 64 bit atomics will always be
available.
ok patrick@ sthen@ deraadt@
|
|
These two interfaces have been entirely unused since introduction.
Remove them and thin the "timeout" namespace a bit.
Discussed with mpi@ and ratchov@ almost a year ago, though I blocked
the change at that time. Also discussed with visa@.
ok visa@, mpi@
|
|
|
|
ok hackroom
tested by plenty
|
|
|
|
joint work markus@ patrick@ bluhm@
|
|
This happens when there's only one component (e.g. "/foo"). This
bug has been present since June 1990 when it was commited to mountd.c
SCCS version 5.9.
Note: the bug is on the second changed line, the first line is changed
for visual consistency.
From CheriBSD via FreeBSD
ok millert@ deraadt@
|
|
Commit v1.77 introduced remote kcov support for timeouts. We need to
tweak a few things to make our support more correct:
- Set to_process for barrier timeouts to the calling thread's parent
process. Currently it is uninitialized, so during timeout_run() we
are passing stack garbage to kcov_remote_enter(9).
- Set to_process to NULL during timeout_set_flags(9). If in the
future we forget to properly initialize to_process before reaching
timeout_run(), we'll pass NULL to kcov_remote_enter(9).
anton@ says this is harmless. I assume it is also preferable to
passing stack garbage.
- Save a copy of to_process on the stack in timeout_run() before
calling to_func to ensure that we pass the same process pointer
to kcov_remote_leave(9) upon return. The timeout may be freely
modified from to_func, so to_process may have changed when we
return.
Tested by anton@.
ok anton@
|
|
complain (actually useful this time)
ok millert
|
|
Triggered by jmc@ apparently misunderstanding the intention of the
text and fixing a grammatical error in a way that wasn't ideal,
so i guess he wouldn't have been the only one to find the previous
version hard to understand.
OK jmc@
|
|
ok mpi@
|
|
ok mpi@
|
|
|
|
Reported by Peter J. Philipp.
ok mvs@ deraadt@
|
|
ok patrick@
|
|
Reminded by jmc
|
|
Add missing TPMR section to ifconfig(8) by moving the commands from the
driver's manual to it (copy/paste) and document the ioctl(2) interface in
tpmr(4).
Indenting tpmr's first EXAMPLE while here; from jmc.
OK jmc
|
|
the WSDISPLAYIO_GETSCREENTYPE ioctl. This ensures that they always match
the currently loaded font metrics.
Previously, wsfontload(8) hardcoded the default height and width values
for the font to be loaded as 12x22 when using framebuffer consoles, and
as 8x16 when in text mode. The 12x22 value wasn't correct in case we
felt back to the smaller 8x16 font for screen widths smaller than 960px,
and wasn't valid anymore since we replaced Gallant 12x22 by Spleen 12x24
on all architectures but sparc64.
OK jcs@, mpi@
|
|
it back to tty*0.
This is needed to restore working defaults in wsfontload(8).
OK jcs@, mpi@
|
|
Spotted by schwarze@, discussed with kn@ and schwarze@
|
|
done under both the KERNEL_LOCK() and NET_LOCK().
|
|
From Steve Cohen
5aa4eb5a6d915cf00bf104ddd76e1adbc3dabdc4 in linux 5.7.y/5.7.13
8490d6a7e0a0a6fab5c2d82d57a3937306660864 in mainline linux
|
|
From Peilin Ye
dd4672ba579a78f14dab65062d95c16f0835947b in linux 5.7.y/5.7.13
543e8669ed9bfb30545fd52bc0e047ca4df7fb31 in mainline linux
|
|
From Mazin Rezk
ee27c88788b88c9c1c75e3a9ce580c79c2dba009 in linux 5.7.y/5.7.13
fde9f39ac7f1ffd799a96ffa1e06b2051f0898f1 in mainline linux
|
|
From Alex Deucher
f53aaf88742ccee0e9aa4ed7d700ceeb434d9a7a in linux 5.7.y/5.7.13
87004abfbc27261edd15716515d89ab42198b405 in mainline linux
|
|
doesn't overlap when searching forwards.
|
|
tpmr is a trivial bridge and has no specific ioctls, so to distinguish
it from the rest we must rely on the interface name; assuming that it
is tpmr because neither is_bridge() nor is_switch() return success is
not possible due to the way ifconfig is designed: it runs all *_status()
commands for all interface types.
OK dlg
|
|
This is to reduce duplicate code and prepare for bridge_status() to cover
all bridge like interfaces: bridge(4), switch(4) and tpmr(4).
OK dlg
|
|
|
|
in a X.X/powerpc64 directory. Like miniroot, these skip the "boot -> bsd.rd"
sequence, and boot bsd.rd directly because of disk-discovery issues not
yet resolved in the boot code.
with debugging help from gkoehler and kettenis
|
|
|
|
|
|
Fixes a bunch of panics reported by syzkaller.
ok florian@
Reported-by: syzbot+02f2e07964a89ab65ea4@syzkaller.appspotmail.com
Reported-by: syzbot+c26b058a499ce38f689f@syzkaller.appspotmail.com
Reported-by: syzbot+62af76d8cb7c09ac017c@syzkaller.appspotmail.com
Reported-by: syzbot+d70144b3ae2ec068e318@syzkaller.appspotmail.com
Reported-by: syzbot+3c87ca9873bfd0492f5c@syzkaller.appspotmail.com
Reported-by: syzbot+323549177062adb80f84@syzkaller.appspotmail.com
Reported-by: syzbot+e745c1c29d960337ce14@syzkaller.appspotmail.com
Reported-by: syzbot+91da988a445013baf925@syzkaller.appspotmail.com
Reported-by: syzbot+747cbcbbed6318542061@syzkaller.appspotmail.com
Reported-by: syzbot+ca5efa23e00130bc8000@syzkaller.appspotmail.com
Reported-by: syzbot+731ab8c9a0342ace4189@syzkaller.appspotmail.com
Reported-by: syzbot+6c80b815a0ff8f09be69@syzkaller.appspotmail.com
Reported-by: syzbot+7939d2c4bc9a5dfa707a@syzkaller.appspotmail.com
Reported-by: syzbot+e893fb0259640a314d06@syzkaller.appspotmail.com
Reported-by: syzbot+b6a3447070ae8ffcb125@syzkaller.appspotmail.com
Reported-by: syzbot+23c0824b688f28c79c1b@syzkaller.appspotmail.com
Reported-by: syzbot+6cc72412d8ddcf87f8a1@syzkaller.appspotmail.com
|
|
|
|
TX improvement. It's all Jonathon's code so assert his copyright.
Submitted by Jonathon Fletcher.
Tested by jcs@, Mikolaj Kucharski, Jonathon Fletcher and myself.
ok jmatthew@
|
|
ok jsing@ tb@
|
|
the random subsystem.
ok deraadt@
|
|
related mbufs. Each mbuf(9) passed to these queues stores the pointer to
corresponding pipex(4) session referenced as `m_pkthdr.ph_cookie'. When
session was destroyed its reference can still be in these queues so we
have use after free issue while pipexintr() dereference it.
I removed `pipexinq', `pipexoutq' and pipexintr(). This not only allows
us to avoid issue described above, but also removes unnecessary context
switch in packet processing. Also it makes code simpler.
ok mpi@ yasuoka@
|
|
|
|
A client should only send a status_request as part of the CH.
Pointed out by Michael Forney
ok inoguchi jsing
|
|
The current code might cause a client to send a status_request
containing a CertificateStatusRequest with its certificate. This
makes no sense.
Pointed out by Michael Forney
ok inoguchi jsing
|
|
According to RFC 8446, 4.4.2.1, a server may request that a client
present an OCSP response with its certificate by sending an empty
status_request extension as part of the certificate request. The
current code expects a full CertificateStatus structure, which is
only sent if the server sends an OCSP response with its certificate.
This causes interoperability issues with Go's TLS server and with
newer GnuTLS where we would abort the handshake with a decode_error
alert and length mismatch error.
Issue reported and diagnosed by Michael Forney
Problem also found by Mikolaj Kucharski and inoguchi.
ok inoguchi jsing
|
|
|
|
|
|
|
|
changes with LLVM 10.
found by kettenis@
ok deraadt@
|
|
|