FreeBSD git weekly: 2026-10-26 to 2026-11-01

Introduction

This is a display of mostly-automatically-classified git commits from 2026-10-26 to 2026-11-01.

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.

manpages: Fix unusual Xr order

manpages: Fix unusual Xr order

manpages: Fix unusual Xr order

manpages: Fix unusual Xr order

manpages: Fix unusual Xr order

manpages: Fix unusual Xr order

manpages: Fix unusual Xr order

manpages: Fix unusual Xr order

In-tree Clang is unaware of the N2680 fixed-width modifier `w` and emits
a warning when used.

PR:             https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=299631
Reviewed by:    imp
Differential Revision: https://reviews.freebsd.org/D60939

Hardware support Expand section Collapse section

Hardware drivers and architecture-specific code.

Testing on a Dell AMD Ryzen AI 5 PRO 435 laptop shows that the same
diagnostic information is valid.

Reviewed by:    obiwac
Sponsored by:   The FreeBSD Foundation

Krackan Point has the same quirks as the Phoenix SMU it would seem.

Reported by:    emaste
Sponsored by:   The FreeBSD Foundation

When the kernel is started directly by SBI firmware, locore.S maps only
the 1GB region that contains the kernel, and initriscv() reads the DTB
through that mapping at the physical address passed in a1.  If the
firmware put the DTB in another 1GB region, as QEMU does with more than
1GB of RAM, fake_preload_metadata() faults before the console is up and
the kernel hangs.

Also map the 1GB region that contains the DTB.

This fixes direct kernel booting without FreeBSD loader(8).

PR:             https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=299088
Reviewed by:    mhorne
Fixes:          https://cgit.freebsd.org/src/commit/?id=bfb857546984 ("riscv: Construct an identity map in locore.S")
MFC after:      1 week
Signed-off-by:  Rick Richard <rick@sloservers.com>

The diagnostics array contained expected modules to be loaded but the
checking logic checked for if a devclass of that name existed instead.

Have the diagnostics array contain the devclass instead as well as the
module to load for the hint string.

Furthermore, check tha the number of devices is greater than 0 so that
leftover devclasses from unloaded modules don't skip the hint.

Reported by:    emaste
Reviewed by:    emaste
Fixes:  https://cgit.freebsd.org/src/commit/?id=758578370f6b ("amdsmu: Hints on what to do if IP block blocking S0i3")
Sponsored by:   The FreeBSD Foundation
Pull Request:   https://ron-dev.freebsd.org/FreeBSD/src/pulls/70

Networking Expand section Collapse section

Network-related commands, library, and kernel.

Since SCTP keeps fibnum in the SCTP protocol control block,
the code can't just defer the processing to the IPv4 or IPv6
layer. Therefore it needs to be implemented in the the SCTP
layer and it needs to call the socket layer function.

PR:             https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=300091
Reviewed by:    tuexen
Fixes:          https://cgit.freebsd.org/src/commit/?id=caccbaef8e26 ("socket: Move SO_SETFIB handling to protocol layers")
MFC after:      3 days
MFC to:         stable/14
MFC to:         stable/15

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).

-- no commits in this category this week --

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