witness: add tunables debug.witness.lock_order_{data_count,hash_size}
Add tunable debug.witness.lock_order_data_count to allow adjusting the
number of witness lock order data entries (stacks) without recompiling
the kernel. This may help to display stacks when a lock order reversal
is reported but the number of entries is exhausted before recording the
first lock order, by allowing the user to reboot with an adjusted
tunable and try again.
Tunable debug.witness.lock_order_hash_size is also provided to allow the
hash table load factor to be managed, though that is not required.
Also tweak witness_lock_order_add to avoid computing a hash when it
won't be needed because the lock order data entries are exhausted.
Reviewed by: kib, markj
Sponsored by: Dell Inc.
Differential Revision: https://reviews.freebsd.org/D57600
witness: actually set read-only tunables in time for witness_startup
SYSCTL_XXX with CTLFLAG_RDTUN and without CTLFLAG_NOFETCH should not be
used for values that are needed before SI_SUB_KLD. Otherwise they are
tuned after they are needed. Set CTLFLAG_RDTUN | CTLFLAG_NOFETCH for
the debug.witness.witness_count and debug.witness.skipspin sysctls and
add separate tunables for them, which run at SI_SUB_TUNABLES time, i.e.,
in time for witness_startup.
Reviewed by: kib, markj
Sponsored by: Dell Inc.
Differential Revision: https://reviews.freebsd.org/D57613
documentation: Turn on verbose asciidoctor build
The other builds are verbose by default.
This will increase consistency and reduce cargo-culting.
Discussed with: dch, kevans
math/py-petsc4py: remove deprecated dry_run parameter from build_ext
...to fix build with newer setuptools
While here, correct name of file for stripping
Co-authored by: Hiroo Ono
Approved by: maintainer timeout
PR: 294431
Event: FreeBSD Developer Summit June 2026
Event: BSDCan 2026
documentation: Modernize custom macros
Convert our custom macros to output asciidoctor instead of raw html,
silencing 6500 warnings. This will enable us to turn verbose builds
on, which will enable us to actually understand what is going on in
the doc tree.
Reviewed by: dch, kevans
python.mk: fix ${PYTHON_PLATFORM} for 3.14+
3.14 and later do not include the FreeBSD major version in the string.
Event: FreeBSD Developer Summit June 2026
Event: BSDCan 2026
devel/libisofs: Update 1.5.6 => 1.5.8.pl02
Changelog:
libisofs-1.5.8.pl02.tar.gz Fri May 22 2026
===============================================================================
* Bug fix: iso_local_get_projid() without flag bit5 returned
ISO_PROJID_NO_OPEN_LOCAL on dangling symlinks
* Bug fix: Compile time error with --disable-lfa-flags --enable-projid
libisofs-1.5.8.pl01.tar.gz Tue Apr 07 2026
===============================================================================
* Bug fix: iso_image_set_ignore_aclea() inverted the setting for reading
the XFS-style project id from disk files
* Silenced error messages about ioctl(FS_IOC_FSGETXATTR)
libisofs-1.5.8.tar.gz Thu Apr 02 2026
===============================================================================
* Bug fix: File path of imported BIOS boot image was forgotten when it gets
overwritten by a file of the same name. Thanks Brian C. Lane.
[39 lines not shown]
handbook: Remove sectnumlevels
Asciidoctor documentation says sectnumlevels from 0-5 are accepted.
Since every chapter sets this value to 6, it is not being parsed and
does not do anything.
Discussed with: bcr
nfs_clvnops.c: Fix the case where va_flags are being cleared
Commits c5d72d2 and 3b6d4c6 broke the case where the
archive/hidden/system attributes are being set false
(UF_ARCHIVE, UF_HIDDEN or UF_SYSTEM bits being cleared.)
and the NFS server does not support those attributes.
These patches only checked for support if the
archive/hidden/system attributes were non-zero.
This patch fixes the problem.
PR: 296088
Tested by: Joshua Kinard <freebsd at kumba.dev>
MFC after: 1 week
Fixes: c5d72d29fe0e ("nfsv4: Add support for the NFSv4 hidden and system attributes")
