This is a display of mostly-automatically-classified git commits from 2026-09-21 to 2026-09-27.
This report is still in progress.
DEBUG: This version of the report is primarily for checking the classifiers, and therefore contains extra information (in this colour).
Table of contents and commits per category:
| (0) | Highlighted commits (these are copies, not in stats) | |
| 0 | 0.0% | Userland programs |
| 9 | 30.0% | Documentation |
| 11 | 36.7% | Hardware support |
| 2 | 6.7% | Networking |
| 3 | 10.0% | System administration |
| 0 | 0.0% | Libraries |
| 0 | 0.0% | Filesystems |
| 4 | 13.3% | Kernel |
| 0 | 0.0% | Build system |
| 0 | 0.0% | Internal organizational stuff |
| 1 | 3.3% | Testing |
| 0 | 0.0% | Style, typos, and comments |
| 0 | 0.0% | Contrib code |
| 0 | 0.0% | Reverted commits |
| 0 | 0.0% | Unclassified commits |
| 30 | 100% | total |
| Technical notes about this page |
debug: info about the automatic classification
| num | % | num changed | stage |
|---|---|---|---|
| 9 | 30.0% | 0 | 02-filenames_wildcards |
| 1 | 3.3% | 0 | 02b-filenames_wildcards2 |
| 13 | 43.3% | 0 | 03-filenames_plain1 |
| 7 | 23.3% | 0 | 04-filenames_plain2 |
| 0 | 0.0% | 0 | Manually-classified commits |
| 0 | 0.0% | 0 | Unclassified commits |
debug: more stats
| num | % | stage |
|---|---|---|
| 0 | 0.0% | Misclassified commits |
| 30 | 100.0% | Classified commits, no corrections |
debug: groups
| 0 | 0.0% | num in revert |
| 0 | 0.0% | num in fixes |
| 9 | 30.0% | num in consecutive |
| 9 | 30.0% | Commits in groups |
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 --
Commits about commands found in man section 1 (other than networking).
-- no commits in this category this week --
Man pages, release notes, etc.
This driver is for NTT DoCoMo 3G cellular equiment, which afaict all went offline six months ago. Tidy up the entry until we can remove it. MFC after: 3 days
debug: classified in
02-filenames_wildcards by
'.*\.[1-9]'
+ Update SYNOPSIS to the new standard format + Rename CONFIGURATION to the usual LOADER TUNABLES + Adjust tunable markup for inclusion in the search index + Editorial nit: Unwind a parenthetical MFC after: 3 days
debug: classified in
02-filenames_wildcards by
'.*\.[1-9]'
MFC after: 3 days
debug: classified in
02-filenames_wildcards by
'.*\.[1-9]'
MFC after: 3 days
debug: classified in
02-filenames_wildcards by
'.*\.[1-9]'
MFC after: 3 days
debug: classified in
02-filenames_wildcards by
'.*\.[1-9]'
+ Update SYNOPSIS to the new standard format + Give this a clearer description in apropos + Give this a clearer description in hardware note + Spinoff SYSCTL VARIABLES from HARDWARE + Pet linter for long lines and trailing punctuation + Tag SPDX MFC after: 3 days
debug: classified in
02-filenames_wildcards by
'.*\.[1-9]'
MFC after: 3 days
debug: classified in
02-filenames_wildcards by
'.*\.[1-9]'
MFC after: 3 days
debug: classified in
02-filenames_wildcards by
'.*\.[1-9]'
Also add a missing Cd tag for consistency. MFC after: 3 days
debug: classified in
02-filenames_wildcards by
'.*\.[1-9]'
Hardware drivers and architecture-specific code.
And replace inline assembly Sponsored by: Arm Ltd Differential Revision: https://reviews.freebsd.org/D59482
debug: classified in
03-filenames_plain1 by
'sys/arm64/'
arm64/smmu: Move smmu later We need to wait for the interrupt drivers to attach before the smmu driver. As both of these happened at BUS_PASS_INTERRUPT + BUS_PASS_ORDER_MIDDLE there was no guarantee this would happen in the correct order. Fix by moving the smmu driver to BUS_PASS_ORDER_LATE. Sponsored by: Arm Ltd Differential Revision: https://reviews.freebsd.org/D59485
debug: classified in
03-filenames_plain1 by
'sys/arm64/'
arm64/smmu: Start handling errata Handle the Arm MMU-600 erratum 1076982 where when we poll for a sync command completion we can't use the wait-for-event instruction. This is in preparation for later adding support for polling for sync command completion and is not an issue on stable branches. Sponsored by: Arm Ltd Differential Revision: https://reviews.freebsd.org/D59486
debug: classified in
03-filenames_plain1 by
'sys/arm64/'
arm64/smmu: Split out waiting for sync completion In preparation for adding a non-MSI method split out waiting for sync completions from smmu_sync. While here fix the loop to wait for sync timeout to the worst case Linux uses. Sponsored by: Arm Ltd Differential Revision: https://reviews.freebsd.org/D59487
debug: classified in
03-filenames_plain1 by
'sys/arm64/'
arm64/smmu: Support polling for sync completion When the hardware doesn't support MSIs we need to poll to wait for sync operations to complete. Add support for this to support booting on this hardware. Sponsored by: Arm Ltd Differential Revision: https://reviews.freebsd.org/D59488
debug: classified in
03-filenames_plain1 by
'sys/arm64/'
arm64/smmu: Only MSI poll when cache-coherent Only use the MSI polling method when we support MSIs and the SMMU is cache-coherent. The SMMU writes to a memory location. If it is not cache-coherent then the CPU may read the existing value in its cache and miss the signal the sync operation has completed. Sponsored by: Arm Ltd Differential Revision: https://reviews.freebsd.org/D59489
debug: classified in
03-filenames_plain1 by
'sys/arm64/'
vmm: Normalize a zero PIT count before starting channel 0 pit_timer_start_cntr0() does not schedule a callout when the initial count is zero. The counter write handler normalizes a programmed zero count only after calling it, leaving an initially unarmed channel 0 without a scheduled timer event. Move the existing normalization before the timer-start call. Retain the historical 0xffff representation of a zero count. Reviewed by: markj MFC after: 2 weeks Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D59749
debug: classified in
03-filenames_plain1 by
'sys/amd64/'
vmm: Synchronize long-mode state when emulating CR0 writes vmx_emulate_cr0_access() sets EFER.LMA and the IA-32e guest VM-entry control when enabling paging with EFER.LME set, but does not clear them when disabling paging. This can leave an inconsistent guest state that fails VM entry. Update both fields in either direction based on EFER.LME and the CR0 value written to the VMCS. Use the mask-adjusted CR0 value so the resulting state remains consistent with the VMX fixed-bit requirements. Reviewed by: markj MFC after: 2 weeks Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D59756
debug: classified in
03-filenames_plain1 by
'sys/amd64/'
vmm: Fix a page wiring leak in MOVS emulation When emulating a MOVS from MMIO to guest RAM, the kernel's vm_copy_setup() wires the destination pages. If the subsequent MMIO read fails, emulate_movs() skips vm_copy_teardown(), leaking the page wire references acquired during setup. Run vm_copy_teardown() regardless of the MMIO read result, and only copy the value to guest memory if the read succeeds. Preserve the existing error return. This matches illumos change 13309. Reviewed by: markj Obtained from: illumos 83cd75bb2949d26e6eb38ddefc60fdeed1909643 MFC after: 2 weeks Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D59823
debug: classified in
03-filenames_plain1 by
'sys/amd64/'
vmm: Re-arm the PIT callout for square wave mode The 8254's square wave mode (mode 3) is periodic, with the same interrupt rate as the rate generator mode (mode 2), but vatpit_callout_handler() only re-arms the channel 0 callout for TIMER_RATEGEN. A guest that programs mode 3 therefore receives a single IRQ0 and no further timer interrupts. Re-arm the callout for TIMER_SQWAVE as well, matching illumos change 13301. Reviewed by: markj Obtained from: illumos 93d78aba5b32996fc2ae893a6237a0d3972f86b2 MFC after: 2 weeks Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D59816
debug: classified in
03-filenames_plain1 by
'sys/amd64/'
Also explicitly specify .cfi_sections to emit the cfi bytecode into the loadable .eh_frame section. Reviewed by: mchoo Sponsored by: The FreeBSD Foundation MFC after: 1 week Differential revision: https://reviews.freebsd.org/D59838
debug: classified in
03-filenames_plain1 by
'sys/amd64/'
Network-related commands, library, and kernel.
When performing an unconnected sendto() on a v6 UDP socket in a classic
jail, we were not applying the usual policy of replacing the loopback
addr with the jail's primary IP. Compare with, e.g., udp6_connect() or
the IPv4 udp_send(). Fix that.
Reported by: Yuxiang Yang, Yizhou Zhao, Ao Wang, Xuewei Feng, Qi Li,
and Ke Xu from Tsinghua University using GLM-5.1 from Z.ai
Reviewed by: bz, glebius
MFC after: 2 weeks
Sponsored by: The FreeBSD Foundation
Differential Revision: https://reviews.freebsd.org/D59772
debug: classified in
03-filenames_plain1 by
'sys/netinet6/'
When one pfsync host clears states it informs its peers about this.
While processing such messages, in pfsync_in_clr() we failed to take the
interface name into account.
This meant that if one host cleared states on one interface the peers
would clear all states, not just those on the affected interface.
Actually check for the interface in pfsync_in_clr()
Sponsored by: Rubicon Communications, LLC ("Netgate")
debug: classified in
03-filenames_plain1 by
'sys/netpfil/'
Stuff in man section 8 (other than networking).
Currently, bhyveload(8) does not validate the supplied disk image path. For example, it allows passing the /dev/null device, which later fails in userboot because it does not support DIOCGSECTORSIZE and DIOCGMEDIASIZE ioctls (see userdisk_init() in stand/userboot/userboot/userboot_disk.c). Fix that by checking DIOCGSECTORSIZE and DIOCGMEDIASIZE ioctls early. A similar check already exists in bhyve(8). While here, make cb_diskioctl() report the obtained sector size instead of hard-coding 512. Reviewed by: markj MFC after: 2 weeks Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D59253
debug: classified in
04-filenames_plain2 by
'usr.sbin/'
EDK2's QemuBootOrderLib inspects the bootorder file provided via fw_cfg and requires it to be NUL-terminated. Otherwise, it rejects the supplied bootorder and falls back to its default boot order. Currently, bhyve registers bootorder with qemu_fwcfg_add_file() using bootorder_len returned by open_memstream(), which excludes the trailing NUL byte. Fix that by passing bootorder_len + 1 to qemu_fwcfg_add_file() so the fw_cfg payload is properly NUL-terminated. PR: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279720 Reviewed by: markj Found with: codex (gpt-5.6-sol) MFC after: 1 week Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D59859
debug: classified in
04-filenames_plain2 by
'usr.sbin/'
Differential Revision: https://reviews.freebsd.org/D59602 MFC after: 3 weeks PR: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=289923 Reviewed by: bnovkov
debug: classified in
04-filenames_plain2 by
'usr.sbin/'
-- no commits in this category this week --
-- no commits in this category this week --
Kernel stuff (other than networking, filesystems, and drivers).
Calling dtrace_copy and dtrace_copystr with the kaddr and uaddr arguments inversed does not work with PAN. Rename them dtrace_copyin_pan and dtrace_copyinstr_pan, respectively, and implement dtrace_copyout_pan and dtrace_copyoutstr_pan. Avoid excessive faulting by checkin DTrace's CPU flags. Implement the trick from OpenSolaris/Illumos of only checking the flags when crossing into a new page, altough more effectively by examining the vaddr instead of the count. Reviewed by: markj MFC after: 3 weeks Differential Revision: https://reviews.freebsd.org/D59449
debug: classified in
04-filenames_plain2 by 'sys/'
__func__ is a variable not a string literal so pass it to printf. This only manifest when KLD_DEBUG was defined so wasn't tested by an kernel including LINT. Reported by: Mark Millard <marklmi@yahoo.com> Sponsored by: Innovate UK
debug: classified in
04-filenames_plain2 by 'sys/'
Without this, no kernel config contained this option so it was easy to break. Sponsored by: Innovate UK
debug: classified in
04-filenames_plain2 by 'sys/'
Otherwise vfs_report_lockf() can race with lf_purgelocks() while the latter is freeing active lock entries without any locks held. Reviewed by: kib MFC after: 2 weeks Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D59768
debug: classified in
04-filenames_plain2 by 'sys/'
-- no commits in this category this week --
-- no commits in this category this week --
Helps to mitigate failures due to timeout in CI on emulated architectures: https://ci.freebsd.org/job/FreeBSD-main-riscv64-test/16565/testReport/usr.bin.gh-bc/ MFC after: 3 days Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D59547
debug: classified in
02b-filenames_wildcards2 by
'usr.bin/.*/tests/.*'
These could go in other categories, but it's more clear if they're here instead.
-- no commits in this category this week --
-- no commits in this category this week --
-- no commits in this category this week --
Not classified automatically, and waiting for manual attention.
-- no commits in this category this week --
Dates:
cgit.freebsd.org/src. Git accurately records the
order of commits, but not their dates.Automatic grouping:
This reverts commit \\b([0-9a-fA-F]{40})\\b
and the hash was found in this week's commits.
Automatic categories:
Source code:
Generated with commits-periodical 0.21 at 2026-09-21 19:44:48+00:00.
This work is supported by Tarsnap Backup Inc.
Alternate version: 2026-09-21 (release)