committer filter by committer.
@path/to/ filter by path in repository.
committer@path/to/ filter by committer AND path in repository.
abdef0123 filter by commit's SHA hash.
rNNN filter by SVN revision.
rNNN-rMMM filter by SVN revisions range (inclusive).
Multiple filters can be specified separated by spaces or comas in which case they'll be combined using OR operator.
|e713d3a0||imp||May 6, 2021, 7:08 p.m.||boot: fix OBJS to not include BTX's crt0.o
According to comments in the Makefile, to make pxeboot work we need to have crt0.o first. This is needed because the simplified loader in pxeboot assumes that the startup code is at offset 0 in this binary. In normal booting, the start address can be obtained from headers of the binary, but since pxeboot encodes this as a pure binary, it has no way of knowing where that is and assumes 0. Added comments to that effect in the Makefile. We've done this by adding it to OBJS before all the other .o's are added. However, there's a problem. This also adds it to the CLEANFILES variable, which causes it to be removed from multiple places. The dependencies may also cause it to be re-built at a time that's after boot2 is built. This causes installs to fail because at install time boot2 is considered to be out of date and the programs to rebuild it are no longer in the path. Cope with this problem by just adding it to LDFLAGS instead. Glanced at by: kevans ("I thought that went in ages ago") Sponsored by: Netflix Differential Revision: https://reviews.freebsd.org/D28876cgit
|12588ce0||avg||May 6, 2021, 6:49 p.m.||PCI hot-plug: use dedicated taskqueue for device attach / detach
Attaching and detaching devices can be heavy-weight and detaching can sleep waiting for events. For that reason using the system-wide single-threaded taskqueue_thread is not really appropriate. There is even a possibility for a deadlock if taskqueue_thread is used for detaching. In fact, there is an easy to reproduce deadlock involving nvme, pass and a sudden removal of an NVMe device. A pass peripheral would not release a reference on an nvme sim until pass_shutdown_kqueue() is executed via taskqueue_thread. But the taskqueue's thread is blocked in nvme_detach() -> ... -> cam_sim_free() because of the outstanding reference. MFC after: 10 days Sponsored by: CyberSecure Reviewed by: mav, imp Differential Revision: https://reviews.freebsd.org/D30144cgit
|420dbe76||asomers||May 6, 2021, 6:32 p.m.||gmultipath: make physpath distinct from the underlying providers'
zfsd uses a device's physical path attribute to automatically replace a missing ZFS disk when a blank disk is inserted into the same physical slot. Currently gmultipath passes through its underlying providers' physical path attribute. That may cause zfsd to replace a missing gmultipath provider with a newly arrived, single-path disk. That would be bad. This commit fixes that problem by simply appending "/mp" to the underlying providers' physical path, in a manner similar to what geli already does. Sponsored by: Axcient MFC after: 3 weeks Differential Revision: https://reviews.freebsd.org/D29941cgit
|be578b67||glebius||May 6, 2021, 5:19 p.m.||tcp_twcheck(): use correct unlock macro.
This crippled in due to conflict between two last commits 1db08fbe3ff and 9e644c23000. Submitted by: Peter Leicgit
|5d8fd932||rrs||May 6, 2021, 3:22 p.m.||This brings into sync FreeBSD with the netflix versions of rack and bbr.
This fixes several breakages (panics) since the tcp_lro code was committed that have been reported. Quite a few new features are now in rack (prefecting of DGP -- Dynamic Goodput Pacing among the largest). There is also support for ack-war prevention. Documents comming soon on rack.. Sponsored by: Netflix Reviewed by: rscheff, mtuexen Differential Revision: https://reviews.freebsd.org/D30036cgit
|0ec3e991||andrew||May 6, 2021, 7:42 a.m.||Use '.arch_extension crc' in the arm64 crc32 code
We don't care about the base architecture here, just that the crc extension is enabled. Sponsored by: Innovate UKcgit
|916f3dba||trasz||May 6, 2021, 8:33 a.m.||linux(4): make arch_prctl(2) support GET_CET_STATUS, report unknown codes|
|49c894dd||jhibbits||May 6, 2021, 1:57 a.m.||powerpc64: Split out DMAP and non-DMAP implementations of some methods|
|66405796||jhibbits||May 6, 2021, 1:57 a.m.||msun fixes for SPE
Summary: Fix FPU exception management for powerpcspe. Bits are in a different place from the standard FPSCR, so we need to handle the shifting differences. Also, there's no concept of a "software exception" raise, so we need to do exceptional math to trigger the exception from software. Reviewed By: alfredo Differential Revision: https://reviews.freebsd.org/D22824cgit
|d1cb8d11||tuexen||May 5, 2021, 11:02 p.m.||sctp: improve consistency when handling chunks of wrong size
MFC after: 3 dayscgit
|097e8701||imp||May 5, 2021, 9:26 p.m.||fix style nit: space after if|
|d00aff62||imp||May 5, 2021, 9:19 p.m.||provide easy way to disable kld_list loading|
|f009aeda||imp||May 5, 2021, 9:12 p.m.||bsnmpd: Return the correct uptime.
Do not assume that the kernel boot time is invariant. It is not. FreeBSD uses the formula: wall_time = boot_time + uptime where uptime is monotinically increasing and boot_time is adjusted to get the proper time of day. FreeBSD offers a way to retrieve the uptime directly, so use that instead of trying to compute it by subtracting boot_time from wall_time. Sponsored by: Netflix Reviewed by: cy@ Differential Revision: https://reviews.freebsd.org/D30114cgit
|6c34dde8||markj||May 5, 2021, 9:12 p.m.||igmp: Avoid an out-of-bounds access when zeroing counters
When verifying, byte-by-byte, that the user-supplied counters are zero-filled, sysctl_igmp_stat() would check for zero before checking the loop bound. Perform the checks in the correct order. Reported by: KASAN MFC after: 1 week Sponsored by: The FreeBSD Foundationcgit
|9a7c2de3||markj||May 5, 2021, 9:12 p.m.||realloc: Fix KASAN(9) shadow map updates
When copying from the old buffer to the new buffer, we don't know the requested size of the old allocation, but only the size of the allocation provided by UMA. This value is "alloc". Because the copy may access bytes in the old allocation's red zone, we must mark the full allocation valid in the shadow map. Do so using the correct size. Reported by: kp Tested by: kp Sponsored by: The FreeBSD Foundationcgit