summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
* Implement rx filtering using the flow table. Now we have three flow groups,jmatthew2019-06-031-72/+263
| | | | | | | | | | | one that will match any packet, used in promisc mode; one that matches on the low bit of the first byte of the destination mac address, used to receive all multicast packets; and one that matches on the whole destination mac address, used to receive unicast, broadcast and specific multicast addresses. As we add multicast addresses, we create flow entries to match them, but if we run out, we create an all-multicast flow entry. ok dlg@
* - Remove a redundant check within alc_mii_readreg_813x().kevlo2019-06-031-5/+1
| | | | | | | | The PHY address is already checked within alc_miibus_readreg(). - Remove redundant call to alc_stop_queue(). First thing alc_stop_mac() does is call alc_stop_queue(). From Brad
* Switch from bintime_add() et al. to bintimeadd(9).cheloha2019-06-035-65/+243
| | | | | | | | | | | | | | | Basically just make all the bintime routines look and behave more like the timeradd(3) macros. Switch to three-argument forms for structure math, introduce and use bintimecmp(9), and rename the structure conversion routines to resemble e.g. TIMEVAL_TO_TIMESPEC(3). Document all of this in a new bintimeadd.9 page. Code input from mpi@, manpage input from schwarze@. code ok mpi@, docs ok schwarze@, docs probably still ok jmc@
* Change pci_intr_handle_t into a struct and replace duplicated code thatkettenis2019-06-032-169/+38
| | | | | | | | implements mapping of MSI and MSI-X interrupts with new generic functions. Fixes a use-after-free in sone PCI device drivers that call pci_intr_string(9) after pci_intr_establish(9). ok deraadt@
* Change pci_intr_handle_t into a struct and replace duplicated code thatkettenis2019-06-024-183/+102
| | | | | | | | implements mapping of MSI and MSI-X interrupts with new generic functions. Fixes a use-after-free in sone PCI device drivers that call pci_intr_string(9) after pci_intr_establish(9). ok deraadt@
* KNF and sneaky whitespacesderaadt2019-06-021-7/+5
|
* Use a simple hash table to look up blocks by the fast-hash. Also useflorian2019-06-023-45/+179
| | | | | | a rolling computation for the fast-hash.OB With this openrsync is on par with gpl rsync for file updates. From kristaps
* Support prefers-color-scheme: dark.schwarze2019-06-021-8/+21
| | | | | The :visited rule was contributed by <Armin at Besirovic dot com>. Guidance and OK tj@.
* this list file is never usedderaadt2019-06-021-76/+0
|
* first few small steps towards unificationderaadt2019-06-025-15/+21
|
* A few architectures used a "shared ramdisk/Makefile" with invertedderaadt2019-06-021-117/+0
| | | | reach-around for .inc files. That method is now gone.
* have_md is initialized at startup, don't need to do it again laterderaadt2019-06-021-2/+1
| | | | from Hiltjo Posthuma
* spelling; from Hiltjo Posthumaderaadt2019-06-021-2/+2
|
* Repair state and flag bitmasks to match RFC, from Mitchell Kromederaadt2019-06-021-3/+3
| | | | ok claudio
* yacc(1) copies its union so it is not a good place to storenicm2019-06-021-124/+141
| | | | | TAILQ_HEADs. Allocate them instead. Found from a problem reported by sthen@.
* In manpages, don't escape apostrophes as \'; it's rarely what you want.bentley2019-06-025-38/+48
| | | | | Most of these are correct just as '. A few benefit from Ql or \(aq. But if in doubt, just use '.
* spelling/grammar fixes; from larry hynesjmc2019-06-0213-52/+52
|
* Fix incorrect character escape.bentley2019-06-021-3/+3
| | | | From Stephen Gregoratto; thanks!
* Move initialization of limit0 into a dedicated function. This newvisa2019-06-023-24/+28
| | | | | | | | | function is also a proper place for setting up the plimit pool. While here, raise the IPL of the plimit pool to IPL_MPFLOOR, needed in upcoming MP work. OK claudio@
* dump pcie Device Serial Number capability valuesdlg2019-06-021-1/+23
|
* Complete the ld.so boot cleanup: move most libc initialization fromguenther2019-06-028-50/+153
| | | | | | | | | | | | | | | | | _csu_finish() to _libc_preinit(), which is an .init_array function in shared libc (and mark it INITFIRST) or a .preinit_array function in static libc, grabbing the _dl_cb callback there from ld.so. Then in _csu_finish(), invoke the dl_clean_boot() callback to free ld.so's startup bits before main() gets control. Other cleanups this permits: - move various startup structures into .data.rel.ro - the dl* stubs in libc can be strong and call the callbacks provided via _dl_cb - no longer need to conditionalize dlctl() calls on presence of _DYNAMIC original concept and full diff ok kettenis@ ok deraadt@
* Refactor the MAP_STACK feature, and introduce another similar variation:deraadt2019-06-0113-225/+160
| | | | | | | | | Lookup the address that a syscall instruction is executed from, and kill the process if that page is writeable. This brings an aspect of W^X behaviour to W|X mappings (in JITs not yet adapted to W^X). The goal is to remove simple attack methods and force use of ret2libc or other more complicated means. ok kettenis stefan visa
* Update regression test for a maximum sizeof(int32_t) length octets.rob2019-06-011-8/+6
|
* Limit maximum number of length octets to platform independent sizeof(int32_t).rob2019-06-011-2/+5
| | | | | | Problem noticed by bluhm@. Discussed on hackers. ok claudio@
* Bump VM_MAX_KERNEL_ADDRESS so that we have about 16G of KVA. Sincepatrick2019-06-011-2/+2
| | | | | | | | | we need KVA to keep track of all the RAM pages, machines with a lot of memory easily exhaust our KVA space. We need about 1G of KVA per 32G of memory, so with 16G of KVA we can maintain close to 512G of memory. ok kettenis@
* Back out frame pointer elimination optimization.mortimer2019-06-011-11/+0
|
* If only one of -x or -y is given, use the calculated size for thenicm2019-06-011-2/+7
| | | | other. Pointed out by Ben Boeckel.
* Do not eliminate frame pointers on i386. The entire i386 ecosystem assumesmortimer2019-06-011-1/+0
| | | | | it will be there. problem found by naddy@, "heck yeah" kettenis@
* Revert to using the SCHED_LOCK() to protect time accounting.mpi2019-06-0114-101/+54
| | | | | | | | | It currently creates a lock ordering problem because SCHED_LOCK() is taken by hardclock(). That means the "priorities" of a thread should be moved out of the SCHED_LOCK() first in order to make progress. Reported-by: syzbot+8e4863b3dde88eb706dc@syzkaller.appspotmail.com via anton@ as well as by kettenis@
* On machines with large amounts of physical memory we fail to initialize uvmkettenis2019-06-012-13/+66
| | | | | | | | | | because we don't have enough kernel memory available in the early bootstrap phase to allocate the vm_page structures. Fix this by making uvm_growkernel() work before uvm is initialized like we do on other architectures that don't use a direct map and explicitly call it after enumerating the available physical memory with an estimate of how much KVA we need to initialize uvm. ok patrick@
* Fix warnings when building zlib with ZLIB_CONST definedjca2019-06-016-16/+16
| | | | | Probably not very useful (given the lack of feedback) but feels more correct. Kernel part tested with option ZLIB_CONST.
* Make sure that the IMSG_CTL_RESET message is sent immediately.reyk2019-06-011-1/+9
| | | | | | | | | | | | | This fixes an issue that might better be solved in imsg itself. The problem is that IMSG_CTL_RESET does not include an fd while the following messages (IMSG_CFG_RELAY and IMSG_CFG_RELAY_FD) do contain fds. If the receiver gets them in one buffer (via recvmsg), the first fd might be wrongly associated to the IMSG_CTL_RESET message. This is theoretically taken care of by the imsg API, so it is either a bug in relayd's API usage or in imsg itself. "sure" claudio@ as a temporary fix.
* update currency exchange rates;jmc2019-06-011-39/+39
|
* Need stdlib.h, from Ben Boeckel.nicm2019-06-011-1/+2
|
* Recognise Cortex-A65.jsg2019-06-011-1/+4
| | | | ok kettenis@
* drm: Wake up next in drm_read() chain if we are forced to putback the eventjsg2019-06-011-0/+1
| | | | | | From Chris Wilson 00734a9e7329acc48e575f697ee4118998c1dac0 in linux 4.19.y/4.19.47 60b801999c48b6c1dd04e653a38e2e613664264e in mainline linux
* drm/amd/display: Set stream->mode_changed when connectors changejsg2019-05-311-2/+1
| | | | | | From Nicholas Kazlauskas 62e79f4c6bc05c32be43e2532fe12c082429af27 in linux 4.19.y/4.19.47 b9952f93cd2cf5fca82b06a8179c0f5f7b769e83 in mainline linux
* drm/amd/display: Fix Divide by 0 in memory calculationsjsg2019-05-311-5/+15
| | | | | | From Murton Liu fc5293ab6c48710eed5df3b40e808e3a3c560e2d in linux 4.19.y/4.19.47 59979bf8be1784ebfc44215031c6c88ca22ae65d in mainline linux
* drm/amd/display: fix releasing planes when exiting odmjsg2019-05-311-2/+4
| | | | | | From Dmytro Laktyushkin 70611b1b81c4ec8ce99d3c00107e89697ec1f495 in linux 4.19.y/4.19.47 bc2193992b00488f5734613ac95b78ef2d2803ab in mainline linux
* drm/amdgpu: fix old fence check in amdgpu_fence_emitjsg2019-05-311-7/+17
| | | | | | From Christian Koenig d8a36f8418034bacef0b5b73c0822f41646d77ba in linux 4.19.y/4.19.47 3d2aca8c8620346abdba96c6300d2c0b90a1d0cc in mainline linux
* zap trailing whitespace;jmc2019-05-313-8/+8
|
* Fix edge case tests in long form encoding. Regress failure noticed by Bluhm onrob2019-05-311-5/+5
| | | | 32 bit platforms.
* Fix warnings, from Ben Boeckel.nicm2019-05-312-6/+4
|
* document the newer PERMIT_PACKAGE frameworkespie2019-05-311-39/+21
|
* Add MSI-X support.kettenis2019-05-311-28/+39
| | | | ok patrick@
* Use a per-process mutex to protect time accounting instead of SCHED_LOCK().mpi2019-05-3114-54/+101
| | | | | | | Note that hardclock(9) still increments p_{u,s,i}ticks without holding a lock. ok visa@, cheloha@
* Re-enable frame pointer elimination for x86 and mips64 if optimizations aremortimer2019-05-311-0/+12
| | | | | | enabled. ok visa@
* Re-enable RETGUARD leaf function optimization for arm64.mortimer2019-05-313-3/+16
| | | | | | | | It turns out MachineFrameInfo.hasCalls() is unreliable, because it is up to the backends to update this information whenever they add calls to a function, and this does not always happen. ok kettenis@
* Note closefrom(2)'s origins in Solaris 9.cheloha2019-05-311-3/+3
| | | | | | Manpage input from jmc@ and schwarze@, archaeological input from schwarze@. ok schwarze@
* a tidied version of mlarkin/phessler diffs to document options which don;t makejmc2019-05-311-2/+11
| | | | sense on "join" lines;