BSD Commit Log Search

   in nfs_writerpc() error from server would leak an mbuf

   reported by Andrew Griffiths of Calif
   initial diff from deraadt@ ok miod@

   cleanup when nfsm_srvmtofh1() errors in nfsrv_rename()

   corrects vnode references and namei_pool leak
   reported by Andrew Griffiths of Calif
   initial diff from deraadt@ ok miod@

   move-pane needs -D.

   Revert previous, it is not the right change.

   Disable time expansion if expanding an inner format or more %s are
   needed.

   Remove support for control socket. There's no httpctl, and no known plans
   to implement it.

   OK rsadowski@, kirill@

   Similar to a recent commit in vmd, remove ps_rcsocks from proc.s, which is
   unused.

   OK rsadowski@, kirill@

   Change layout sets to build the layout using the new mechanics, from
   Dane Jensen.

   Instead of fully redrawing the pane when sync ends, only redraw lines
   that have been changed.

   Add a couple of format c/f and c/b to emit colours.

   Use macro instead of hardcoding the name of the file containing NCA history

   OK tb@

   Pass peer to rde_enqueue_updates() to enqueue updates on.

   This allows withdraws to be queued on the peer that caused them and not
   on peerself. Also only enqueue a rib entry once and try to keep FIFO
   order. Before every call to rde_enqueue_updates() would requeue the
   rib entry at the end of the list. Doing this requeue could delay updates
   for long time.  Further optimisation may need to happen here.

   OK tb@

   Do not draw to tty if PANE_REDRAW has been set since it is just going to
   be replaced.

   Add overline for ghostty also, GitHub issue 5309.

   more missing mldsa44-ed25519, based on GHPR696 from
   Loganaden Velvindron

   whitespace

   simplify SIGINFO output: remove list of active channels (too verbose)
   and just display destination and connection duration; requested deraadt@

   Tighten up the introduction a little:

   Mention Match as a conditional directive (previously it only
   mentioned Host)

   Try to use consistent language in the introduction to refer to
   configuration directives (previously it used "parameters" and
   "keywords" interchangeably).

   Mention that comments may appear at the end of the line too, and that
   whitespace at the beginning/end of lines is not significant.

   Move negative-FD checks to before first use.  CID 909998, ok djm@

   fix openlog() arguments, LOG_CONS should not be or'd into facility
   from Ricardo Branco

   ssh -o doesn't support Host or Include options, they are only
   valid in the config file. bz3968 from xspielinbox

   mention mldsa44-ed25519 in usage();
   based on GHPR695 from Loganaden Velvindron

   And some other indentation.

   Fix some indentation.

   Change a malloc to calloc.

   LLVM now emits calls to strlen(3) and wcslen(3).  Redirect those calls to
   our hidden aliases to prevent unnecessary PLT entries (like we already do
   for memmove(3), memcpy(4) and memset(3)).

   ok deraadt@

   login_ldap(8)/ldap(1): fix endless loop

   Goto fail on closed socket and check for evbuffer_add(3) errors, too.

   Original bug was reported by Matthias Pitzl.

   On Tue, Jun 30, 2026 at 11:35:32AM +0200, Martijn van Duren wrote:
   > Could you also make sure other aldap.c users get the fix?

   OK martijn@

   ypldap(8): fix endless loop

   Goto fail on closed socket and check for evbuffer_add(3) errors, too.

   OK martijn@

   partially revert previous to return to 64-byte submission queue
   entries by default, only applying 128-byte entries on APPLE_NVME3
   (T2) where we know it's needed

   the previous change broke APPLE_NVME2 which advertises 128 bytes but
   needs 64

   ok dlg

   Yet another AI assisted report has triggered on the belief that
   kill(2) against 0 (for pgrp) should not be permitted by pledge "proc".
   Nothing validates this premise.  Blocking process group kills would
   break substantial amounts of software in dangeous ways, as it creates
   fragile invarient conditions.  We previously tried to block this belief
   with kern_pledge.c:1.357 by subtly adding "/pgrp" in a comment, but that
   was not effective so try adding "kill(2) may still operate on the
   process group with pid 0." to the manual page.  This is annoying
   because the pledge manual page usually describes what is blocked
   (resulting in process killing) rather than specifically listing
   what allowed.
   Discussed with Ivan Arce