summaryrefslogtreecommitdiffstats
path: root/sys (follow)
Commit message (Collapse)AuthorAgeFilesLines
...
* match on 300 series pchjsg2019-05-081-2/+4
|
* regenjsg2019-05-082-2/+257
|
* add more Intel 300 Series PCH idsjsg2019-05-081-1/+52
|
* Fix kernel compile with DEBUG_AGINTC.ccardenas2019-05-081-2/+1
| | | | ok phessler, deraadt
* Modify the buffer cache to always flip recovered DMA buffers high.beck2019-05-082-32/+123
| | | | | | | | This also modifies the backoff logic to only back off what is requested and not a "mimimum" amount. Tested by me, benno@, tedu@ anda ports build by naddy@. ok tedu@
* Use the same completion queue for both the send and receive queues.jmatthew2019-05-071-2/+2
| | | | | We don't get any benefit from having separate queues (yet), and the tx completion queue seems to stall sometimes if it's on its own.
* Fix delay logic: measure w/ uptime, pack timeval correctly. ok krw@cheloha2019-05-071-4/+4
|
* always rearm completion queues as leaving them disarmed would lead to rxjmatthew2019-05-071-7/+4
| | | | | | or tx completion stalling. (also replace a line dlg didn't mean to remove)
* align the rx buffer to ETHER_ALIGNdlg2019-05-071-2/+3
| | | | | | | this will probably change as the rx handling grows to cope with the hardware max mru. ok jmatthew@
* use MCX_PAGE_SIZE when calculating number of pages for queuesdlg2019-05-071-6/+9
| | | | | | PAGE_SIZE might be the same, but isn't on sparc64 at least. ok jmatthew@
* Fix thinko in previous. The .bss clearing was overzealous and overwrotevisa2019-05-061-3/+3
| | | | a part of the free memory list, terminating it prematurely.
* Bring back lockf deadlock detection from the dead. Back in 2007, the deadlockanton2019-05-061-53/+55
| | | | | | | | | | | | | detection broke while changing the owner of a lock from struct proc to struct filedesc/file. Instead of keeping track of the owning proc for each lock, introduce a new list for all pending blocked locks. This list is scanned before waiting on a blocking lock in order to determine if sleeping would cause a deadlock. The new implementation is serialized by the recently added locking to the same subsystem, meaning that acquiring the kernel lock is no longer necessary. ok visa@
* Enforce store/load order when setting or clearing AST flag on mips64visa2019-05-063-3/+22
| | | | | | | | | | | | | | Make sure that any preceding stores become visible to other CPUs before setting the AST flag in need_resched() and signotify(). This should prevent a very unlikely case with inter-CPU ASTs where the receiving CPU uses stale state. When clearing the AST flag in ast(), ensure that the clearing store is performed before any other memory accesses in the AST handler. Otherwise, there is a slight risk of losing an AST request that gets posted while the handler is running. OK guenther@
* Issue write-write barrier before sending IPI on mips64visa2019-05-061-10/+25
| | | | | | | | The barrier ensures that any lockless state changes become visible to other CPUs before the IPI is sent. Otherwise, a receiving CPU might still observe an old state when it processes the interrupt. OK guenther@
* Fix unintentional delay of ASTs on MP mips64visa2019-05-061-23/+29
| | | | | | | | | | | | Make the interrupt and trap return paths check for ASTs with interrupts disabled. If there is no pending request, interrupts are kept disabled until return to userspace. This fixes delayed processing of an AST request that arrives from another CPU after the AST flag has been checked but before the CPU has finished the return path. The IPI that follows the setting of the AST flag forces kernel re-entry and recheck of AST. Noticed by guenther@
* Fix a logic error when configuring the driver to use msi.kevlo2019-05-061-2/+2
|
* Whitespace removalmlarkin2019-05-061-5/+5
| | | | Pointed out by Jerome Pinot
* Whitespace removalmlarkin2019-05-062-6/+6
| | | | Pointed out by Jerome Pinot
* Whitespace removalmlarkin2019-05-061-2/+2
| | | | Pointed out by Jerome Pinot
* Whitespace removalmlarkin2019-05-0612-41/+41
| | | | Pointed out by Jerome Pinot
* Whitespace removalmlarkin2019-05-063-6/+6
| | | | Pointed out by Jerome Pinot
* Whitespace removalmlarkin2019-05-062-7/+7
| | | | Pointed out by Jerome Pinot
* Whitespace and extra semicolon removal.mlarkin2019-05-061-2/+2
| | | | Pointed out by Jerome Pinot
* Getting too tight. Surrender a littlederaadt2019-05-051-2/+2
|
* Add support for the EFI Random Number Generator Protocol and use it to XORkettenis2019-05-053-5/+92
| | | | | | random data into the buffer that we feed the kernel. ok deraadt@, mlarkin@
* Use the .bss for the bootstrap stack of mips_init(). This way the memoryvisa2019-05-052-9/+24
| | | | | | | | region is properly allocated by the firmware. Move the .bss clearing to locore.S because the section has to be ready when the stack is taken into use. This additionally makes the C environment more consistent at the start of mips_init().
* Call cpu_unidle() from need_resched() on mips64 like mostvisa2019-05-051-2/+4
| | | | other architectures.
* Turn need_resched() and signotify() into proper functions on mips64.visa2019-05-053-14/+21
|
* regenkettenis2019-05-052-19/+24
|
* Harmonize AMD CPU/APU devices.kettenis2019-05-053-14/+15
| | | | ok jsg@
* let users try mcx(4)deraadt2019-05-042-2/+4
|
* 3 bytes of kernel stack address space were leaked into on-disk directories.deraadt2019-05-041-2/+4
| | | | | | | | | | | | | | | | | | | | | | | | With some gritty work up to 254 bytes can be discovered. More details at https://svnweb.freebsd.org/changeset/base/347066 The impact on OpenBSD is very limited: 1 - such stack bytes can be found in raw-device reads, from group operator. If you can read the raw disks you can undertake other more powerful actions. 2 - read(2) upon directory fd was disabled July 1997 because I didn't like how grep * would display garbage and mess up the tty, and applying vis(3) for just directory reads seemed silly. read(2) was changed to return 0 (EOF). Sep 2016 this was further changed to EISDIR, so you still cannot see the bad bytes. 3 - In 2013 when guenther adapted the getdents(2) directory-reading system call to 64-bit ino_t, the userland data format changed to 8-byte-alignment, making it incompatible with the 4-byte-alignment UFS on-disk format. As a result of code refactoring the bad bytes were not copied to userland. Bad bytes will remain in old directories on old filesystems, but nothing makes those bytes user visible. There will be no errata or syspatch issued. I urge other systems which do expose the information to userland to issue errata quickly, since this is a 254 byte infoleak of the stack which is great for ROP-chain building to attack some other bug. Especially if the kernel has no layout/link-order randomization ... ok kettenis jca millert otto ...
* Silence "Uunable to acquire AGP" message since we don't support AGP on allkettenis2019-05-041-0/+2
| | | | AGP-capable chipsets and probably never will.
* Remove some junk that we don't use.kettenis2019-05-041-12/+1
| | | | ok patrick@
* Add DIR_ROUNDUP define, from Kirk McKusickderaadt2019-05-041-1/+2
| | | | ok millert otto kettenis
* Removed all diagnostic, calling printf() here might create a recursion.mpi2019-05-041-9/+1
| | | | Should be revisited once logwakeup() is fixed.
* Relax the check in knote_{de,en}queue: don't panic w/o KERNEL_LOCK().mpi2019-05-041-3/+9
| | | | | | | Use splassert_fail() instead, please set kern.splassert to 2 and report the corresponding stack trace if you see a warning. ok dlg@
* fix array bounds check in ixl_search_link_speed()jsg2019-05-041-2/+2
| | | | ok dlg@
* drm/i915/bios: assume eDP is present on port A when there is no VBTjsg2019-05-041-0/+1
| | | | | | | | | | From Thomas Preston 6e0473633af059a559ce7b4cbaa51e389c94085e in mainline linux Makes inteldrm(4) work on James Hastings's 'HP Stream Laptop 14-cb1XX' a Gemini Lake system where finding the VBT fails. ok kettenis@
* Improve the interaction between efifb(4), inteldrm(4) and radeondrm(4)kettenis2019-05-0415-69/+160
| | | | | | | | | | | | | | | | when we have a serial console by introducing the notion of a "primary" graphics device. The primary graphics device is the one set up and used by firmware (BIOS, UEFI). The goal is to make sure that wsdisplay0 and drm0 reliably attach to the primary graphics device such that X works out of the box even if you have multiple cards or if you are using a serial console. This also fixes the situation where inteldrm(4) or radeondrm(4) would take over the console on UEFI systems even if the kernel was booted with a serial console. ok jsg@
* drm: Fix drm_release() and device unplugjsg2019-05-041-4/+2
| | | | | | From Noralf Tronnes c5eb9a424ebd2d9f9e3cccdf2bfbb415c2921261 in linux 4.19.y/4.19.39 3f04e0a6cfebf48152ac64502346cdc258811f79 in mainline linux
* Add mcx(4), a driver for Mellanox ConnectX-4 (and later) Ethernetjmatthew2019-05-042-1/+5473
| | | | | | | controllers, written by dlg@ and me based on the cut down non-NDA programming reference manual Mellanox were nice enough to release. ok dlg@ deraadt@
* Add missing bridge_getbif(), reported by jsg@.mpi2019-05-031-1/+2
|
* An if_put() was missing in one branch of bridge_process(). Thisbluhm2019-05-031-1/+2
| | | | | | caused a hanging "ifconfig bridge0 destroy" and a subsequent uvm fault. reported and tested by Hrvoje Popovski; OK visa@
* Make VOP_ADVLOCK() safe to use without kernel lockvisa2019-05-031-6/+2
| | | | | | | | | | | All non-dummy implementations of VOP_ADVLOCK() rely on lf_advlock() which is now safe to use without the kernel lock. Because VOP_ADVLOCK() does not make the vnode dirty, it is unnecessary to keep track of in-flight vnode lock operations and the updating of vnode->v_inflight can be dropped from VOP_ADVLOCK(). This makes VOP_ADVLOCK() safe to use without the kernel lock. OK tedu@ mpi@
* Revert "drm/i915/fbdev: Actually configure untiled displays"jsg2019-05-031-7/+5
| | | | | | From Dave Airlie 2bc7ce32eb21b094b3ae3e489017fabfe72b4dda in linux 4.19.y/4.19.38 9fa246256e09dc30820524401cdbeeaadee94025 in mainline linux
* Add a print function to mainbus(4) such that it prints unconfigured deviceskettenis2019-05-021-3/+52
| | | | | | just like we do for simplebus(4). ok patrick@, visa@
* Avoid running the activate function for a partially attached ehci(4) driver.kettenis2019-05-021-4/+8
| | | | | | | | | The Realtek DASH ehci(4) doesn't have a properly set SBRN register which prevents us from fully attaching the device. This would result in a panic during suspend because the activate function will access register that aren't mapped. ok deraadt@
* Reset root port after last STP interface is removed.mpi2019-05-021-5/+13
| | | | Prevent use-after-free reported by Hrvoje Popovski.
* works on newer AMD Ryzen APUs/CPUs as wellkettenis2019-05-021-1/+2
| | | | ok deraadt@, mlarkin@
Copyright © 1996 – 2023 Jason A. Donenfeld. All Rights Reverse Engineered.