FreeBSD git weekly: 2026-07-20 to 2026-07-26

Introduction

This is a display of mostly-automatically-classified git commits from 2026-07-20 to 2026-07-26.

This report is still in progress.

Table of contents and commits per category:

Highlighted commits Expand section Collapse section

For extra visibility, these are copies of commits found in other sections. Most (if not all) come from the commit message containing "Relnotes:", or commits modifying UPDATING.

-- no commits in this category this week --

Userland programs Expand section Collapse section

Commits about commands found in man section 1 (other than networking).

-- no commits in this category this week --

Documentation Expand section Collapse section

Man pages, release notes, etc.

-- no commits in this category this week --

Hardware support Expand section Collapse section

Hardware drivers and architecture-specific code.

-- no commits in this category this week --

Networking Expand section Collapse section

Network-related commands, library, and kernel.

-- no commits in this category this week --

System administration Expand section Collapse section

Stuff in man section 8 (other than networking).

-- no commits in this category this week --

Libraries Expand section Collapse section

-- no commits in this category this week --

Filesystems Expand section Collapse section

-- no commits in this category this week --

Kernel Expand section Collapse section

Kernel stuff (other than networking, filesystems, and drivers).

on attach of the knote.  It is same as for NOTE_EXIT when attaching to
the exiting process.

Reviewed by:    markj
Sponsored by:   The FreeBSD Foundation
MFC after:      1 week
Differential revision:  https://reviews.freebsd.org/D58327

When transferring a thread with near 100% CPU statistics (but not 100%;
up to 57.5/59≈97.46%) to a CPU where the enqueue offset is ahead of at
least 2 from the dequeue one, which requires peculiar conditions to
happen (transfer triggered by a bind request or cpuset change, or during
balancing if a thread or more existed from a brief amount of time on the
origin CPU), the transferred thread can get placed after the dequeue
offset, effectively making it appear as a high priority one unduly,
causing latency increase for other threads.

The change here was missed when changing the enqueue and dequeue offsets
update mechanism to recover pre-256-queue-runqueue ULE anti-starvation
and fairness behavior.  That change opened up the possibility that these
two offsets are apart by more than one.

Reviewed by:    markj
Discussed with: Minsoo Choo <minsoo@minsoo.io>
Fixes:          https://cgit.freebsd.org/src/commit/?id=6792f3411f6d ("sched_ule: Recover previous nice and anti-starvation behaviors")
MFC after:      2 weeks
Sponsored by:   The FreeBSD Foundation
Differential Revision:  https://reviews.freebsd.org/D57829

Build system Expand section Collapse section

-- no commits in this category this week --

Internal organizational stuff Expand section Collapse section

-- no commits in this category this week --

Testing Expand section Collapse section

-- no commits in this category this week --

Style, typos, and comments Expand section Collapse section

These could go in other categories, but it's more clear if they're here instead.

-- no commits in this category this week --

Contrib code Expand section Collapse section

-- no commits in this category this week --

Reverted commits Expand section Collapse section

-- no commits in this category this week --

Unclassified commits Expand section Collapse section

Not classified automatically, and waiting for manual attention.

-- no commits in this category this week --

Technical notes

Dates:

• The dates are "approximate" because git has no record of exactly when each commit was added. The "author date" and "commit date" are text fields controlled by each committer, not the actual date the commit reaches cgit.freebsd.org/src. Git accurately records the order of commits, but not their dates.

Automatic grouping:

• "Commit & revert pair" groups were automatically grouped when a commit's (full) message contained

  This reverts commit \\b([0-9a-fA-F]{40})\\b

  and the hash was found in this week's commits.
• "Commit group #" groups were automatically grouped when 3 or more consecutive commits by the same author had the same category and summary prefix.

Automatic categories:

• Commits were (mostly) automatically classified based on regex pattern-matching on the commit's modified files, summary, or the whole commit message. The goal is to have the system automatically classify 95% of the commits, with 95% accuracy; then we'll manually check the results and fix the incorrectly-classified and unclassified commits.

Source code:

• https://github.com/Tarsnap/freebsd-git-weekly