OpenBSD/src mrRlQe6usr.bin/openssl openssl.1

   openssl.1: remove mention of OPENSSL_EC_BIN_PT_COMP

   The need for this compile time option enabling point compression for
   binary curves despite patent issues has been removed in openssl 1.0.0
   (released in 2010).

   [It's really difficult to count the number of bad ideas in the above.]
VersionDeltaFile
1.170+2-16usr.bin/openssl/openssl.1
+2-161 files

OpenBSD/src 9eHYcjTsys/net fq_codel.c

   plug a memory leak when detaching codel ifq disciplines on an interface.

   fqcodel_alloc() takes (moves) ownership of memory allocated as part
   of the pf queue code that sets up the queue discipline, but nothing
   releases it when the discipline is removed from the interface. every
   time you load a pf rulese that uses codel, it temporarily resets
   an interface to priq before creating and attaching new codel
   instances. this means every ruleset load would leak memory, to the
   point where M_DEVBUF allocations exhaust the kernel map.

   this has fqcodel_free() call fqcodel_pf_free to free the now unused
   codel discipline.

   found and fixed by lexi wilson
VersionDeltaFile
1.20+2-2sys/net/fq_codel.c
+2-21 files

OpenBSD/src qLddahqsys/dev/pci if_iavf.c

   iavf(4) can do 64 bit DMA also at bus_dmamem_alloc().

   from Brad Smith; tested by Hrvoje Popovski
VersionDeltaFile
1.28+2-2sys/dev/pci/if_iavf.c
+2-21 files

OpenBSD/src IjoVtgzsys/dev/pci if_vmx.c

   vmx(4) can handle 64 bit DMA transfers.

   from Brad Smith; tested by Hrvoje Popovski
VersionDeltaFile
1.95+10-6sys/dev/pci/if_vmx.c
+10-61 files

OpenBSD/src me0CjzRsys/arch/amd64/amd64 hibernate_machdep.c, sys/arch/i386/i386 hibernate_machdep.c

   Fix a longstanding off-by-one error in hibernate unpack.

   Last year, I made a commit to early-allocate the hibernate data structure
   needed during actual hibernate instead of triyng to allocate it at the
   time of 'ZZZ'. This change exposed an old bug that caused machines to
   be unstable after unhibernate (typically manifesting in pool corruption
   or other difficult to track down bugs).

   The error was due to skipping a page of memory immediately adjacent to
   the hibernate piglet during unpack, effectively leaving that page with
   whatever content it had before image unpack started. If you got lucky, this
   page wasn't in use and you didn't notice anything. But with the fix to do
   early allocation, the chance that the page was in use increased, and
   thus the bug was exposed.

   Big thank you to Walter Alejandro Iglesias for tracking this down and
   providing the diff/root cause.


    [5 lines not shown]
VersionDeltaFile
1.53+2-2sys/arch/amd64/amd64/hibernate_machdep.c
1.63+2-2sys/arch/i386/i386/hibernate_machdep.c
1.9+2-2sys/arch/loongson/loongson/hibernate_machdep.c
+6-63 files

OpenBSD/src i6PZgBRsys/dev/pci if_iwx.c

   Fix Tx performance on iwx(4) BZ devices.

   BZ devices need to be told how long the MAC header is in the offload_assist
   field of the Tx command, even if no offloading features are being used.

   Found by chance while browsing iwlwifi driver git logs.
   See linux.git commit af8bfc7e38a7ad4f8e1663de7ab1463e644050b2
VersionDeltaFile
1.222+3-1sys/dev/pci/if_iwx.c
+3-11 files

OpenBSD/src 2e46eM2sys/dev/pci pcidevs.h pcidevs_data.h

   regen
VersionDeltaFile
1.2120+2-2sys/dev/pci/pcidevs.h
1.2115+2-2sys/dev/pci/pcidevs_data.h
+4-42 files

OpenBSD/src wRCdFuSsys/dev/pci if_ixv.c pcidevs

   ixv(4) prints VF for virtual function and mac address during attach.

   from Hrvoje Popovski and Yuichiro NAITO
VersionDeltaFile
1.3+3-3sys/dev/pci/if_ixv.c
1.2127+2-2sys/dev/pci/pcidevs
+5-52 files

OpenBSD/src iYYXgt7sys/kern kern_pledge.c

   When pledged, if a process receives a bad descriptor the receiver should
   not be killed.  The EPERM approach used for other conditions is good enough.
   from deraadt@; Report from Henry Ford

   this is errata/7.7/028_recvfd.patch.sig
VersionDeltaFile
1.323.4.4+2-2sys/kern/kern_pledge.c
+2-21 files

OpenBSD/src 7MYiqGPsys/kern kern_pledge.c

   When pledged, if a process receives a bad descriptor the receiver should
   not be killed.  The EPERM approach used for other conditions is good enough.
   from deraadt@; Report from Henry Ford

   this is errata/7.8/022_recvfd.patch.sig
VersionDeltaFile
1.333.2.3+2-2sys/kern/kern_pledge.c
+2-21 files

OpenBSD/src 9W0Imhesys/dev/pci pcidevs.h pcidevs_data.h

   regen
VersionDeltaFile
1.2119+2-2sys/dev/pci/pcidevs.h
1.2114+2-2sys/dev/pci/pcidevs_data.h
+4-42 files

OpenBSD/src 9IXjGtrsys/dev/pci pcidevs

   Intel 0x7740 can be either wifi 6e or wifi 7 devices.

   Change "Intel WiFi 6e AX211" to "Intel WiFi AX211" to avoid confusion.
VersionDeltaFile
1.2126+2-2sys/dev/pci/pcidevs
+2-21 files

OpenBSD/src GxI5byOsys/dev/pci if_iwx.c

   Make iwx(4) only attach to BZ devices which have RF type GF (wifi 6e).

   PCI vendor/product IDs can be shared between Intel wifi 6e and wifi 7 devices.
   Wifi 7 devices need different firmware and probably a new driver.
   Avoid matching them.

   Bad match on a wifi 7 device reported by Jesper Wallin.
VersionDeltaFile
1.221+33-2sys/dev/pci/if_iwx.c
+33-21 files

OpenBSD/src 8nwKOfcsbin/pfctl pfctl.c

   pfctl(8) parser must not ignore error from pfctl_optimize_ruleset().
   Ignoring the error may cause pfctl(8) to load inconsistent ruleset
   preventing pf(4) to enforce desired policy.

   Issue reported and fix suggested by berts _from_ fastmail _dot_ com

   'Looks good.' @deraadt
VersionDeltaFile
1.401+3-3sbin/pfctl/pfctl.c
+3-31 files

OpenBSD/src 40MGh62sys/dev/pci if_iwx.c if_iwxreg.h

   sync iwx(4) RX descriptor status field with firmware layout

   Same change was made in iwlwifi about 6 years ago.
   See linux.git commit e365e7de63e5b612d94fb433e38d9414de811f7d

   This matters to us now that we started looking at Rx status bits
   beyond 16 bits in order to check for duplicate subframes in A-MPDUs.

   Found by Coverity (CID 1670294)
   pointed out by and ok jsg@
VersionDeltaFile
1.220+6-6sys/dev/pci/if_iwx.c
1.73+2-4sys/dev/pci/if_iwxreg.h
+8-102 files

OpenBSD/src Tu56LZ9sys/dev/pci if_iwx.c

   Fix support for some older iwx(4) devices broken by changes for BZ support.

   Keep hardware revision info sent to firmware intact for older devices.
   BZ devices store parts of hardware revision information in a new place.
   I accidentally changed the information sent to older devices, which broke
   firmware loading on a subset of AX201/AX210 devices.

   Reported to me by several people, thanks!

   This fix is based on a patch by David Leadbeater.
VersionDeltaFile
1.219+9-3sys/dev/pci/if_iwx.c
+9-31 files

OpenBSD/src lJLiT7xusr.bin/xargs xargs.1

   xargs(1): bump posix spec to 2024

   The spec now documents -0 and -r.

   In addition, the spec notes that specifying both -0 and -E are mutually
   exclusive, leaving the actual behavior unspecified.

   ok deraadt@, guenther@ on the spec version bump
   ok millert@ on documenting the interaction between -0 and -E
VersionDeltaFile
1.30+8-7usr.bin/xargs/xargs.1
+8-71 files

OpenBSD/src PPKsQFMregress/lib/libcrypto/x509/rfc3779 rfc3779.c

   rfc3779 regress: explain where the range comes from
VersionDeltaFile
1.12+5-1regress/lib/libcrypto/x509/rfc3779/rfc3779.c
+5-11 files

OpenBSD/src r11mBN0regress/lib/libcrypto/x509/rfc3779 rfc3779.c

   rfc3779 regress: add an actual range

   This improves the test coverage of make_addressRange() where there is an
   annoyance with unused bits in the RFC 3779 ASN.1 encoding versus trailing
   ones in the network encoding that the X509v3_addr_add_range() API expects.
VersionDeltaFile
1.11+52-1regress/lib/libcrypto/x509/rfc3779/rfc3779.c
+52-11 files

OpenBSD/src sCQVXSTsys/kern kern_pledge.c

   When pledged, if a process receives a bad descriptor the receiver should
   not be killed.  The EPERM approach used for other conditions is good enough.
   Report from Henry Ford
   this will be errata 7.8/022_recvfd.patch and 7.7/028_recvfd.patch
VersionDeltaFile
1.347+2-2sys/kern/kern_pledge.c
+2-21 files

OpenBSD/src qvsTTSSsys/dev/pci/drm/scheduler sched_main.c

   drm/sched: Fix kernel-doc warning for drm_sched_job_done()

   From Yujie Liu
   da09dfc90cb7ed1ab40d675234382f151eeb0563 in linux-6.18.y/6.18.17
   61ded1083b264ff67ca8c2de822c66b6febaf9a8 in mainline linux
VersionDeltaFile
1.16+1-0sys/dev/pci/drm/scheduler/sched_main.c
+1-01 files

OpenBSD/src qHnKy2fsys/dev/pci/drm drm_syncobj.c

   drm/syncobj: Fix handle <-> fd ioctls with dirty stack

   From Julian Orth
   7196a1ff7b9a2ab6d973fe3c1dfc426d8d8ed4d2 in linux-6.18.y/6.18.17
   2e3649e237237258a08d75afef96648dd2b379f7 in mainline linux
VersionDeltaFile
1.18+2-2sys/dev/pci/drm/drm_syncobj.c
+2-21 files

OpenBSD/src LyUxiO1sys/dev/pci/drm/amd/display/dc/core dc_stream.c

   drm/amd/display: Use GFP_ATOMIC in dc_create_stream_for_sink

   From Natalie Vock
   0381584929791c4b989fb0a36a466ae20aea1608 in linux-6.18.y/6.18.17
   28dfe4317541e57fe52f9a290394cd29c348228b in mainline linux
VersionDeltaFile
1.12+1-1sys/dev/pci/drm/amd/display/dc/core/dc_stream.c
+1-11 files

OpenBSD/src Vg8yO7ysys/dev/pci/drm/i915/display intel_dp.c

   drm/i915/dp: Fix pipe BPP clamping due to HDR

   From Imre Deak
   9498fa25a0b0d8c095ce3d1f15d7864228692822 in linux-6.18.y/6.18.17
   fe26ae6ac8b88fcdac5036b557c129a17fe520d2 in mainline linux
VersionDeltaFile
1.32+17-3sys/dev/pci/drm/i915/display/intel_dp.c
+17-31 files

OpenBSD/src mEjXyJ3sys/dev/pci/drm/i915/display intel_dp.c

   drm/i915/dp: Fail state computation for invalid DSC source input BPP values

   From Imre Deak
   99f617ea2ff017b0ba10d5371d83345331091afa in linux-6.18.y/6.18.17
   338465490cf7bd4a700ecd33e4855fee4622fa5f in mainline linux
VersionDeltaFile
1.31+21-7sys/dev/pci/drm/i915/display/intel_dp.c
+21-71 files

OpenBSD/src ouFnkAesys/dev/pci/drm/amd/amdgpu amdgpu_device.c

   drm/amd: Fix hang on amdgpu unload by using pci_dev_is_disconnected()

   From Mario Limonciello
   378dff71efddd15f34124bf9d7c98cd69cd05286 in linux-6.18.y/6.18.17
   f7afda7fcd169a9168695247d07ad94cf7b9798f in mainline linux
VersionDeltaFile
1.94+2-2sys/dev/pci/drm/amd/amdgpu/amdgpu_device.c
+2-21 files

OpenBSD/src aLf49rZsys/dev/pci/drm/amd/amdgpu amdgpu_device.c

   drm/amdgpu: Fix error handling in slot reset

   From Lijo Lazar
   73e8bdf14248136459753252a438177df7ed8c7c in linux-6.18.y/6.18.17
   b57c4ec98c17789136a4db948aec6daadceb5024 in mainline linux
VersionDeltaFile
1.93+10-7sys/dev/pci/drm/amd/amdgpu/amdgpu_device.c
+10-71 files

OpenBSD/src t1IA6Q6sys/dev/pci/drm/amd/amdgpu amdgpu_psp_ta.c

   drm/amdgpu: Fix locking bugs in error paths

   From Bart Van Assche
   5c42d9f8b004905eb441f0eab34662bdacf3192f in linux-6.18.y/6.18.17
   480ad5f6ead4a47b969aab6618573cd6822bb6a4 in mainline linux
VersionDeltaFile
1.8+7-5sys/dev/pci/drm/amd/amdgpu/amdgpu_psp_ta.c
+7-51 files

OpenBSD/src stWCJzGsys/dev/pci/drm/amd/amdgpu amdgpu_aca.c

   drm/amdgpu: Unlock a mutex before destroying it

   From Bart Van Assche
   39ae59e5c1d880176c41ecc2694e0ae81335079d in linux-6.18.y/6.18.17
   5e0bcc7b88bcd081aaae6f481b10d9ab294fcb69 in mainline linux
VersionDeltaFile
1.5+1-0sys/dev/pci/drm/amd/amdgpu/amdgpu_aca.c
+1-01 files

OpenBSD/src IRt3QwAsys/dev/pci/drm/amd/amdgpu amdgpu_userq_fence.c

   drm/amdgpu/userq: Do not allow userspace to trivially triger kernel warnings

   From Tvrtko Ursulin
   1753f5f81ab60a553287f9ee659a6ac363adf8d7 in linux-6.18.y/6.18.17
   7b7d7693a55d606d700beb9549c9f7f0e5d9c24f in mainline linux
VersionDeltaFile
1.2+4-4sys/dev/pci/drm/amd/amdgpu/amdgpu_userq_fence.c
+4-41 files