Branch :
| Author | Commit | Date | CI | Message |
|---|---|---|---|---|
| 46cdafa7 | 2024-08-06 04:59:18 | Replace sys/time.h with proper includes for using localtime Sure deraadt@ | ||
| 2293e682 | 2024-08-05 23:56:10 | restrict the maximum wait time you can set via BIOCSWTIMEOUT to 5 minutes. this is avoids passing excessively large values to timeout_add_nsec. Reported-by: syzbot+f650785d4f2b3fe28284@syzkaller.appspotmail.com | ||
| afebb9f9 | 2024-08-05 23:52:03 | timeout_add_nsec takes a uint64_t now. | ||
| e7251812 | 2024-08-05 23:51:11 | change the nsec argument to timeout_add_nsec from int to uint64_t you can only fit a couple of nanonseconds into an int, which limited the usefulness of the api. worse, if a large nsec value was passed in it could be cast to a negative int value which tripped over a KASSERT at the top of timeout_add that ends up being called. avoid this footgun by working in the bigger type and doing the same range checks/fixes for other timeout_add wrappers. ok claudio@ mvs@ | ||
| 438cc182 | 2024-08-05 18:47:29 | Unlock KERN_BOOTTIME. microboottime() and following binboottime() are mp-safe and `mb' is local data. ok bluhm | ||
| a4f9b83f | 2024-08-05 18:39:34 | Adjust for arm64_intr_get_parent() changes. ok patrick@ | ||
| 4ad77004 | 2024-08-05 18:37:29 | Fix reporting if critical battery state. ok jca@, mlarkin@ | ||
| 1f1fa3f3 | 2024-08-05 18:36:28 | Add battery sensors. ok phessler@ | ||
| 270a6ceb | 2024-08-05 17:47:29 | Fix bridging IPv6 fragments with pf reassembly. Sending IPv6 fragments over a bridge with pf did not work. During input pf reassembles the packet, and at bridge output it should be refragmented. This is only done for PF_FWD direction, but bridge(4) and veb(4) called pf_test() with PF_OUT argument. OK sashan@ | ||
| ad534f18 | 2024-08-05 15:43:58 | Unlock most of `kern_vars' variables. Add corresponding cases to the kern_sysctl() switch and unlock read-only variables from `kern_vars'. Unlock KERN_SOMAXCONN and KERN_SOMINCONN which are atomically read-only accessed only from solisten(). ok kettenis | ||
| d5cabab1 | 2024-08-05 13:55:34 | The devicetree spec says in section 2.4: If an interrupt-generating device does not have an interrupt-parent property, its interrupt parent is assumed to be its devicetree parent. Implement this aspect of the spec in the same way as Linux does by not just looking at the immediate parent but keep on walking up the tree until we hit a node with an "interrupt-controller" property or a node that has an "interrupt-parent" property. same diff as committed for arm64 yesterday ok patrick@ | ||
| 522bbe49 | 2024-08-05 13:46:16 | Take `sysctl_lock' before kernel lock. ok bluhm | ||
| 2adb8ed0 | 2024-08-05 09:43:26 | sync with base | ||
| 45fb58c6 | 2024-08-05 09:43:07 | sync with upstream (noop for openbsd) | ||
| 12702453 | 2024-08-05 07:16:30 | Remove bogus connect(s, NULL, 0) call The only thing it does is error because of a check added in sockargs() in uipc_syscalls r1.155. As guenther pointed out, this may have been added because of a misreading of the last sentence of the first paragraph of the connect(2) manual. Instead of erroring, this will keep listening if -k is given and otherwise it will close the socket and exit with success. ok guenther jeremy | ||
| 2df0ffa8 | 2024-08-05 06:11:42 | Allow our linker warnings regarding misuse of libc functions to be elevated to errors using the -Wl,--fatal-warnings option. ok robert@ | ||
| 5f1cde00 | 2024-08-05 02:54:42 | drm/i915/dp: Don't switch the LTTPR mode on an active link From Imre Deak 12880cc086deef91e62e2f010750087a3c23fae3 in linux-6.6.y/6.6.44 509580fad7323b6a5da27e8365cd488f3b57210e in mainline linux | ||
| aa0c546b | 2024-08-05 02:52:34 | drm/i915/dp: Reset intel_dp->link_trained before retraining the link From Imre Deak a90e900f71da23a354e9d17f1dc0c654d0ae9ceb in linux-6.6.y/6.6.44 d13e2a6e95e6b87f571c837c71a3d05691def9bb in mainline linux | ||
| cd8dd4c7 | 2024-08-05 02:50:36 | drm/amd/amdgpu: Fix uninitialized variable warnings From Ma Ke e150f0171c0c0c45a373a658358c51c940ed4fd9 in linux-6.6.y/6.6.44 df65aabef3c0327c23b840ab5520150df4db6b5f in mainline linux | ||
| 26d6e9f7 | 2024-08-05 02:47:58 | drm/amdgpu: reset vm state machine after gpu reset(vram lost) From ZhenGuo Yin 323790535237927e1b6a7bc35ddf662c6e7c25cc in linux-6.6.y/6.6.44 5659b0c93a1ea02c662a030b322093203f299185 in mainline linux | ||
| cb2f7175 | 2024-08-05 02:44:55 | drm/dp_mst: Fix all mstb marked as not probed after suspend/resume From Wayne Lin e290feb8b749a06b93ed01d4cf66567cbdf0e85d in linux-6.6.y/6.6.44 d63d81094d208abb20fc444514b2d9ec2f4b7c4e in mainline linux | ||
| f61f9b4d | 2024-08-05 02:42:47 | drm/amdgpu/sdma5.2: Update wptr registers as well as doorbell From Alex Deucher 9d74e50098492e89f319ac6922db3c2062f69340 in linux-6.6.y/6.6.44 a03ebf116303e5d13ba9a2b65726b106cb1e96f6 in mainline linux | ||
| 4d9ba5d1 | 2024-08-05 02:40:00 | drm/i915/gt: Do not consider preemption during execlists_dequeue for gen8 From Nitin Gote 05c0fb20ca3e000a7e966584845731ba4fc950da in linux-6.6.y/6.6.44 65564157ae64cec0f527583f96e32f484f730f92 in mainline linux | ||
| 180eb82d | 2024-08-05 02:37:12 | drm/amd/display: Check for NULL pointer From Sung Joon Kim 4ccd37085976ea5d3c499b1e6d0b3f4deaf2cd5a in linux-6.6.y/6.6.44 4ab68e168ae1695f7c04fae98930740aaf7c50fa in mainline linux | ||
| d7388dee | 2024-08-05 02:35:12 | drm/amdgpu: Remove GC HW IP 9.3.0 from noretry=1 From Tim Van Patten 6d72626808325c1986cbf90b0ce27a59b4291876 in linux-6.6.y/6.6.44 1446226d32a45bb7c4f63195a59be8c08defe658 in mainline linux | ||
| d98eb4da | 2024-08-05 02:33:42 | drm/amdgpu: Check if NBIO funcs are NULL in amdgpu_device_baco_exit From Friedrich Vock 67b4592a7d74e57a5a0929eaf3ae30414ebd39ae in linux-6.6.y/6.6.44 0cdb3f9740844b9d95ca413e3fcff11f81223ecf in mainline linux | ||
| 9456895c | 2024-08-05 02:31:14 | drm/amdgpu: Fix memory range calculation From Lijo Lazar ae1dd0a379e41db7d4773880e6918948668ef3ad in linux-6.6.y/6.6.44 ce798376ef6764de51d8f4684ae525b55df295fa in mainline linux | ||
| 6216c052 | 2024-08-05 02:28:52 | drm/amd/pm: Fix aldebaran pcie speed reporting From Lijo Lazar 0af2e5cb74514877326448becf40365b073b44e2 in linux-6.6.y/6.6.44 b6420021e17e262c57bb289d0556ee181b014f9c in mainline linux | ||
| 5e55c4ed | 2024-08-05 02:26:35 | drm/amdkfd: Fix CU Masking for GFX 9.4.3 From Mukul Joshi cd1885ae4cbf191332ae66f8a214e52fb226ba43 in linux-6.6.y/6.6.44 85cf43c554e438e2e12b0fe109688c9533e4d93f in mainline linux | ||
| 8d1d79aa | 2024-08-04 22:28:08 | ppoll() is in POSIX-2024. Update #include visibility and manpages and add restrict qualifiers. While here, rename the BUGS section to CAVEATS since they're really "these probably don't do what you want" notes and not things that need fixing. ok millert@ | ||
| f4fd31f8 | 2024-08-04 20:10:38 | Fix typo. ok kettenis@ | ||
| ba9b1da2 | 2024-08-04 20:06:04 | bump datasize for armv7's pbuild user, some software has grown over the years OK jca@ | ||
| 6651361e | 2024-08-04 17:51:49 | sync | ||
| fb33ed87 | 2024-08-04 16:31:02 | add intelpmc(4) entry; | ||
| 5dbfd905 | 2024-08-04 15:30:08 | Add battery status support for the x1e80100. This SoC needs a second firmware and requires us to shut down an initial "light" firmware that was presumably loaded bu the system firmware. For now the required firmwares are not packaged and need to be copied from the Windows install. ok patrick@ | ||
| 0daf8d66 | 2024-08-04 14:21:09 | intelpmc(4) | ||
| fa6a043a | 2024-08-04 12:01:18 | The devicetree spec says in section 2.4: If an interrupt-generating device does not have an interrupt-parent property, its interrupt parent is assumed to be its devicetree parent. Implement this aspect of the spec in the same way as Linux does by not just looking at the immediate parent but keep on walking up the tree until we hit a node with an "interrupt-controller" property or a node that has an "interrupt-parent" property. ok patrick@ | ||
| 6635b7e6 | 2024-08-04 11:05:18 | Add intelpmc(4), a driver for the power management controller found on various Intel SoCs. The driver takes care of calling the AML methods needed to enter low power idle states during suspend-to-idle (S0i). The driver also implements some debug code that prints the residency of various power states in dmesg. Based on some earlier code by jcs@ ok jcs@ | ||
| 2544af8f | 2024-08-04 09:42:23 | Make a little effort to treate CRLF as LF in config files. GitHub issue 3720. | ||
| 8262b9c0 | 2024-08-04 09:35:30 | The Linux console has some bugs with bright colours. It seems likely that it is emulating them by setting a bright (or bold) flag; however, when the colour is changed from a bright colour (say SGR 96) to a non-bright (say SGR 36), the flag is not reset, so the new colour remains as bright. SGR 39 (default colour) also does not reset, so you end up with the bright default colour. Work around this by sending SGR 0 when switching away from a bright colour, and disable AX for TERM=linux. Also make the check for AX simpler and do not check for the op capability is not actually used. GitHub issue 3976. | ||
| fa40d634 | 2024-08-04 09:01:18 | -l should be before -r, pointed out by jmc a while ago. | ||
| d3278555 | 2024-08-04 08:53:43 | Adjust the logic when deleting last buffer to better preserve the selection: if selecting the element below the deleted one fails (because as the last one), select the one above it instead. From Daniel Mueller, GitHub issue 4043. | ||
| 00b011bc | 2024-08-04 08:39:38 | Use paste_is_empty to check if there are no buffers since paste_get_top will return NULL if there are no automatic buffers. | ||
| 79ebf24a | 2024-08-04 08:15:36 | x509_vfy.c: drop some unnecessary parentheses | ||
| 61a108c8 | 2024-08-04 05:18:28 | - sort SEE ALSO - radiusd_file(8) is section 8, not 5 | ||
| 563222a6 | 2024-08-04 03:56:57 | Use "module" for the modules. Add a link to radiusd_file(8) from radiusd_eap2mschap(8). | ||
| 234b89c8 | 2024-08-03 23:06:56 | A dozen interfaces in <endian.h> were standardized in POSIX-2024 as expected | ||
| 493aa139 | 2024-08-03 22:23:32 | Set system ID field in the PVD to OpenBSD This matches what we use in mkybrid. From Crystal Kolipe. | ||
| 8e0d42cd | 2024-08-03 22:00:31 | The maximum count is SKEY_MAX_SEQ + 1 not SKEY_MAX_SEQ - 1. Sequence numbers are in the range [0, SKEY_MAX_SEQ] inclusive. This means the maximum value for the -n option (count) should be SKEY_MAX_SEQ + 1. From Denis Bodor. | ||
| fb60ec6a | 2024-08-03 21:12:16 | Update awk to the July 28, 2024 version. * Fixed readcsvrec resize segfault when reading csv records longer than 8k. * Rewrite if-else chain in quoted as a switch. | ||
| 4af81b37 | 2024-08-03 20:13:23 | The improbable occurred: strlcpy(3) and strlcat(3) are in POSIX-2024. memmem(3) was also added. Update #include visibility and manpages and add restrict qualifiers. "never thought I'd see this day" millert@ | ||
| dfc5f6fe | 2024-08-03 20:09:24 | mkostemp(3) and reallocarray(3) are in POSIX-2024: adjust #include visibility and update the reallocarray(3) manpage ok millert@ | ||
| 80eb38ce | 2024-08-03 13:06:37 | The EC_KEY method should use the EC_KEY index, not RSA Unbreaks ssh's t-agent-pkcs11-cert regress reported by anton. ok jsing | ||
| ef8f2a3f | 2024-08-03 07:45:26 | Bump CRYPTO_EX_DATA_MAX_INDEX to 32 rust-openssl tests do something weird and need lots of ex data (one index for each registered callback, for example). This makes the regress pass again. noticed by anton ok jsing | ||
| efea1aaa | 2024-08-03 07:43:33 | Use proper size for allocating indexes It's a double pointer, so we should allocate a pointer size, not the entire struct. This saves roughly 500B per class. CID 507397 ok jsing | ||
| 946c9001 | 2024-08-03 04:53:01 | Document SSL_CTX_set_cert_store From Kenjiro Nakayama | ||
| dcd96ea6 | 2024-08-03 04:50:27 | Prepare to provide SSL_CTX_set1_cert_store() SSL_CTX_set_cert_store() should have been called SSL_CTX_set0_cert_store() since it takes ownership of the store argument. Apparently a few people ran into the issue of not bumping the refcount themselves, leading to use after frees about 10 years ago. This is a quite rarely used API and there are no misuses in the ports tree, but since someone did the work of writing a diff, we can still add it. Needless to say that SSL_CTX_get_cert_store() obviously has the exact same issue and nobody seems to have thought of adding a get0 or get1 version to match... Fixes https://github.com/libressl/openbsd/issues/71 From Kenjiro Nakayama | ||
| f4d0a262 | 2024-08-02 22:24:51 | Code patch out the retpoline in the signal trampoline just like the others. Nudged, test, and ok deraadt@ | ||
| 04933f16 | 2024-08-02 22:14:54 | The {get,set}res[ug]id(2) family are in POSIX-2024's XSI option, so adjust the #include visibility and update the manpage. ok millert@ | ||
| 58e8bf10 | 2024-08-02 21:08:47 | nc(1): remove useless function pointer dereferencing ok tb@ | ||
| 141c93e2 | 2024-08-02 16:02:35 | Fix previous Arguably the want_protocol entries in various of these tests are incorrect but I'll leave that for another day. | ||
| 0c5dcecc | 2024-08-02 15:02:22 | Adjust tls regress for protocol parsing fixes This mostly reverts what was done by beck in Tallinn and adjust tlstest to add new test cases and now failing connection tests. | ||
| 6a16e2b3 | 2024-08-02 15:00:01 | libtls: fix legacy protocol parsing Redefining TLS_PROTOCOL_TLSv1_0 and TLS_PROTOCOL_TLSv1_1 to be the same as TLS_PROTOCOL_TLSv1_2 had undesired side effects, as witnessed in the accompanying regress tests. The protocol string all:tlsv1.0 would disable TLSv1.2 (so only enable TLSv1.3) and tlsv1.2:!tlsv1.1 would disable all protocols. It makes more sense to ignore any setting of TLSv1.0 and TLSv1.1, so if you request 'tlsv1.1' you get no protocol, but 'all:!tlsv1.1' will enable the two supported protocols TLSv1.3 and TLSv1.2. Restore the defines to their original values and adjust the parsing code to set/unset them. Issue reported by Kenjiro Nakayama Fixes https://github.com/libressl/openbsd/issues/151 with/ok jsing | ||
| 953cd95b | 2024-08-02 14:35:56 | regen | ||
| d800346e | 2024-08-02 14:34:45 | Push kernel lock down to sysctl(2). Unlock few obvious immutable or read-only variables from "kern.*" and "hw.*" paths. Keep the rest variables locked as before, include pages wiring. Use new sysctl_vs{,un}lock() functions introduced for thar purpose. In kern.* path: - KERN_OSTYPE, KERN_OSRELEASE, KERN_OSVERSION, KERN_VERSION - immutable; - KERN_NUMVNODES - read-only access to integer; - KERN_MBSTAT - read-only access to per-CPU counters; In hw.* path: - HW_MACHINE, HW_MODEL, HW_NCPUONLINE, HW_PHYSMEM, HW_VENDOR, HW_PRODUCT, HW_VERSION, HW_SERIALNO, HW_UUID, HW_PHYSMEM64 - immutable; - HW_USERMEM and HW_USERMEM64 - `physmem' is immutable, uvmexp.wired is mutable but integer; read-only access to localy stored difference between `physmem' and uvmexp.wired; - `hw_vars' - read-only access to integers; some of them like HW_BYTEORDER and HW_PAGESIZE are immutable; ok bluhm kettenis | ||
| 723f2f96 | 2024-08-02 14:02:33 | free class->indexes in CRYPTO_cleanup_all_ex_data() ok jsing | ||
| 682f074d | 2024-08-02 12:43:55 | Backout previous. It was incompleted and too early. | ||
| dc174772 | 2024-08-02 10:48:54 | Rewrite CRYPTO_EX_DATA. CRYPTO_EX_DATA exists as a way to allow an application to attach data to various components in libcrypto and libssl. The general idea is that there are various "classes" (e.g. RSA) and an application can get an "index" (which can have new/dup/free functions provided). The application can then use the index to store a pointer to some form of data within that class, for later retrieval. However, even by OpenSSL standards, this is an insane API. The current implementation allows for data to be set without calling new, indexes can be used without allocation, new can be called without actually getting an index and dup can be called either after new or without new (see regress and RSA_get_ex_new_index(3)/CRYPTO_set_ex_data(3) for more details). On top of this, the previous "overhaul" of the code was written to be infinitely extensible. For now, the rewrite intends to maintain the existing behaviour - once we bed this down we can attempt to ratchet the API requirements and require some sort of sensible sequence. The only intentional change is that there is now a hard limit on the number of indexes that can be allocated (previously there was none, relying only on ENOMEM). ok tb@ | ||
| ce337326 | 2024-08-02 09:28:35 | Switch off unreferenced power resources in DVACT_POWERDOWN instead of DVACT_SUSPEND. Fixes an issue with (un)hibernate where we don't attach xhci(4) controllers, which would make is turn the xhci(4) off inadvertedly because its power resource wasn't referenced. ok mlarkin@ | ||
| 36d39fd5 | 2024-08-02 05:00:35 | sync | ||
| 92f420e6 | 2024-08-02 04:59:55 | bump minor after yesterday's symbol addition requested by kettenis | ||
| e8780c77 | 2024-08-02 04:59:23 | Put exported symbols of libz under our own control This adds a Symbols.list containing the exported symbols like in other libraries in base. If upstream adds new API this won't necessarily need a bump on our side. help/ok kettenis | ||
| c1d8b5d1 | 2024-08-02 01:53:21 | getentropy(2) is in POSIX-2024, so adjust the #include visibility, change the "too much" error to EINVAL, add GETENTROPY_MAX to <limits.h> (via sys/syslimits.h), and update the manpage. ok deraadt@ | ||
| 22230ae7 | 2024-08-01 21:55:48 | Add qcgpio at fdt. ok kettenis@ | ||
| 64e5b687 | 2024-08-01 17:19:01 | Run socket splice idle timeout without kernel lock. OK mvs@ | ||
| 05fd5574 | 2024-08-01 16:25:34 | Bump libsndio pkg-config version to 1.10.0 ok tb@ | ||
| 33f846a6 | 2024-08-01 14:44:34 | bump posix spec from 2008 -> 2024; no documented changes. | ||
| 55a46d88 | 2024-08-01 14:36:27 | sndiod: Fix insufficent check of input from clients Fixes possible sndiod(8) crashes caused by a global table overread triggered by the client. Found and analysed by Henry Ford <henryfordkjv at gmail.com>, thanks! ok blumh, help from millert, mlarkin | ||
| 4cef13ba | 2024-08-01 14:30:17 | bump posix spec 2008 -> 2024; no change noted from 2008 spec, but i've added -h to the list of extensions. that was an omission from our 2008 notes, rather than a change in the spec. | ||
| 20b6c1a1 | 2024-08-01 14:08:38 | bump posix spec 2008 -> 2024; | ||
| ca1e11fc | 2024-08-01 14:08:07 | bump posix spec 2008 -> 2024; | ||
| d83b63cc | 2024-08-01 11:53:03 | Add device tree mapping for Samsung Galaxy Book4 Edge. ok kettenis@ | ||
| d3638ce2 | 2024-08-01 11:13:19 | virtio: Fix dmamap_sync calls Add some missing bus_dmamap_sync calls, noticed with SEV and based on an earlier diff by hshoexer@. Some of the required syncing is done in virtio_check_vq(). Make sure to use that function instead of calling call the virtqueue done function directly from device specific drivers. For viogpu this means that we cannot poll with virtio_dequeue() but must use virtio_check_vq() instead. To make this more clear, rename viogpu_vq_wait() into viogpu_vq_done(). While there, set the DRIVER_OK flag even earlier. It must be set before using any virtqueue. ok kettenis@ | ||
| df51ca29 | 2024-08-01 06:04:22 | Remove a comment that was committed by accident | ||
| 0a218225 | 2024-08-01 04:03:10 | sync with src | ||
| a225ed82 | 2024-08-01 04:02:26 | sync with upstream This adds a new public API, deflateUsed(), so is technically a minor bump. Nothing will be using this anytime soon, so no shared library bump. discussed with deraadt during c2k24 | ||
| ed4f4290 | 2024-08-01 01:43:08 | Possible to read the core file of a process. | ||
| 77474275 | 2024-08-01 00:58:14 | Use arc4random_uniform(n) instead of "% n". | ||
| 1258aca7 | 2024-08-01 00:05:16 | Change the routing entry of the pool addresses from blackhole to reject. This is better because the routing cache can be purged by the reject. | ||
| 7be11c1d | 2024-07-31 17:09:23 | bump posix spec 2008 -> 2024; | ||
| 873f0a37 | 2024-07-31 12:00:18 | add a random amount of time (up to 4 seconds) to the grace login time. ok deraadt@ djm@ | ||
| 9ae74e5e | 2024-07-31 10:07:33 | Add ufshci(4) at fdt support. This lets me boot the Samsung Galaxy Book4 Edge in DT mode with ufshci(4), based on a WIP DTB file. ok kettenis@ | ||
| 8e776806 | 2024-07-31 05:36:13 | quote the book title (%T) reference, to prevent formatters (in this case groff) stumbling over literal words that match macro names; | ||
| 075c50c2 | 2024-07-30 19:47:05 | Make the Samsung Galaxy Book4 Edge (x1e80100) boot in ACPI mode; Until now the kernel did panic during early boot because we couldn't respond to the battery requests sent to the 0xa1 "bus". This (dummy) driver registers a 0xa1 region space very early, and responds with a static zero value to satisfy the battery requests on 0xa1, which let us boot successfully to multi-user. In the future this machine should be operated in FDT mode, and an improved AML parsing interface might make this workaround obsolete also for RAMDISK. Help and OK kettenis@, deraadt@ | ||
| 317edbb4 | 2024-07-30 19:16:49 | bump posix ref 2008 -> 2024; | ||
| 0262ea74 | 2024-07-30 13:58:02 | fold the "timespec" info into the options list (since "time_arg" is already there). move the information of "time_arg" matching touch -t to the "time_arg" description, instead of "timespec". ok millert | ||
| 7f786bdd | 2024-07-30 13:55:11 | bump posix spec from 2008 to 2024; ok millert | ||
| 5e1af158 | 2024-07-30 13:41:15 | Exports the statistics when PIPEXDSESSION. Found by ymatsui at iij. ok mvs | ||
| 539ef4cc | 2024-07-30 13:28:27 | sched_yield() is not strong enough to overflow the recv buffer on some systems. Use a proper sleep using usleep(100) instead. | ||
| 0ecb11e1 | 2024-07-30 09:07:00 | On arm64, check whether the CPU has the BT feature to determine the expected outcome of the test. |