BSD Commit Log Search

   vmm(4): handle proper injection during mov ss/sti shadow on vmx

   arm the interrupt window when we have something to inject but are in a mov ss
   or sti interrupt shadow

   ok dv

   re-arrange rtrd 660 AF_UNIX connect(), setgroups/setresuid/setresgid
   privdrop, and first pledge() above the innocuous getopt() block.
   ok tb

   use err() and warn(), and various knf and include reduction
   (-portable will revisit this in the next round, and then we're good)

   rpki-client: don't treat a duplicate CCR MFT as fatal

   It is possible to concoct situations where two PPs serve byte identical
   manifests. Then CCR generation errors with "CCR MFT tree corrupted".

   Handle this situation gracefully and only warn about the weird situation.
   There are more problems in the vicinity that need fixing but that's for
   after the release.

   Reported by eur1ka qq com. Diff is a tweaked version of the suggested fix.

   ok job

   rpki-client: hoist ccr_mft_free() next to ccr_mft_new()

   part of a larger diff that was ok job

   warning early about rtrd connection failure is nice, even if there
   is a later warning also when it tries to use the socket

   output-rtrx: add some missing includes to help portable

   with input from deraadt.
   ok claudio

   sys/qwz: unwind cold startup failures

   Based on sys/dev/ic/qwx.c,v 1.134

   Track powerup and completed core initialization so failed cold starts
   reset hardware before reclaiming initialized DMA resources. Release
   partial TX allocations and RX rings; ordinary interface down and up
   continues to retain firmware.

   OK: stsp@

   sys/qwz: skip uninitialized CE polling

   Based on sys/dev/ic/qwx.c,v 1.135

   Track successful CE initialization to decide whether completion
   polling is valid; provide dircet TX buffer reclamation for cold
   cleanup after hardware reset, when ring polling is no longer safe.

   OK: stsp@

   sys/qwz: allocate management maps at attach

   Backport of sys/dev/ic/qwx.c,v 1.139 , sys/dev/ic/qwxvar.h,v 1.39
   and sys/dev/pci/if_qwx_pci.c,v 1.40

   OK: stsp@

   sys/qwz: retain the host VIF

   Backport of sys/dev/ic/qwx.c,v 1.138 and sys/dev/ic/qwxvar.h,v 1.38

   OK: stsp@

   sys/qwz: initialize QRTR before power-up

   Backport of sys/dev/ic/qwx.c,v 1.132

   OK: stsp@

   sys/qwz: propagate firmware startup errors

   Backport of sys/dev/ic/qwx.c,v 1.128

   OK: stsp@

   sys/qwz: mark running after MAC startup

   Backport of sys/dev/ic/qwx.c,v 1.122 and sys/dev/ic/qwx.c,v 1.134

   OK: stsp@

   sys/qwz: retain HAL allocations on resume

   Based on sys/dev/ic/qwx.c,v 1.97 and sys/dev/ic/qwx.c,v 1.136

   Preserve HAL allocation pointers across reinitialization: reuse qwz
   allocated ring configuration and claer retained pointer memory. On
   failure, free only allocations made by the current attempt.

   OK: stsp@

   sys/qwz: wait for cookie pool allocations

   Backport of sys/dev/ic/qwx.c,v 1.127

   OK: stsp@

   sys/qwz: wait for startup allocations

   Backport of sys/dev/ic/qwx.c,v 1.127

   OK: stsp@

   For allocations between half a page and a page (which are moved
   towards the end) we don't clear the proper region with freezero().
   Instead, the clearing is done from the start of the page. So fix that.
   Reported by Acts1631

   ok deraadt@

   differentiate the two qualcomm wifi drivers by well-understood names
   Wi-Fi 6 and Wi-Fi 7, even if it looks a bit like puke
   discussed with kettenis

   handle EINPROGRESS and carry errno through.
   OK deraadt@

   Fix softraid rebuild on disks with 4096-byte sectors.

   Problem found, suggested diffs, and testing by Dariusz Swiderski.

   ok claudio@ "makes release" deraadt@

   correct include order

   use __packed; ok rcovelli

   Add option -r to output tables directly to the rtrd(8) controller socket.
   OK deraadt@

   set_dist_point_name(): tiny tweak to restore previous behavior

   Allocate fnm before allocating *pdp. This way a second call to to
   set_dist_point_name() has a tiny little chance of succeeding.

   ok beck ("I strongly suspect this will never matter anywhere.")

   libcrypto: remove support for nameRelativeToCRLIssuer

   Drop support for nameRelativeToCRLIssuer from the CRL Distribution Point
   extension. Per RFC 5280, 4.2.1.13, conforming CAs SHOULD not use it, which
   is sound advice since this garbage was eating memory for breakfast before
   signature thanks to the wonderful gem that is the extension cache.

   One has to wonder why this was needed in libcrypto... This isn't worth
   fixing so off to the bit bucket it goes.

   from tb, ok beck jsing

   libssl: Avoid potential overread on interrupted retransmission in DTLS

   from OpenSSL via jsing

   this is errata/7.8/060_libressl.patch.sig

   Add NULL checks for clients that may not have identified yet, GitHub
   issue 5663.

   libcrypto: remove support for nameRelativeToCRLIssuer

   Drop support for nameRelativeToCRLIssuer from the CRL Distribution Point
   extension. Per RFC 5280, 4.2.1.13, conforming CAs SHOULD not use it, which
   is sound advice since this garbage was eating memory for breakfast before
   signature thanks to the wonderful gem that is the extension cache.

   One has to wonder why this was needed in libcrypto... This isn't worth
   fixing so off to the bit bucket it goes.

   from tb, ok beck jsing

   libssl: Avoid potential overread on interrupted retransmission in DTLS

   from OpenSSL via jsing

   this is errata/7.9/024_libressl.patch.sig

   libcrypto: remove support for nameRelativeToCRLIssuer

   Drop support for nameRelativeToCRLIssuer from the CRL Distribution Point
   extension. Per RFC 5280, 4.2.1.13, conforming CAs SHOULD not use it, which
   is sound advice since this garbage was eating memory for breakfast before
   signature thanks to the wonderful gem that is the extension cache.

   One has to wonder why this was needed in libcrypto... This isn't worth
   fixing, so off to the bit bucket it goes.

   ok beck jsing

   Do not format times that localtime_r and ctime_r cannot convert, from
   Alexandre Fiori.