src/share/man/man9, branch main

OF_getprop.9: update OF_hasprop() signature

2026-04-16T16:15:40+00:00

The return type has been converted to a bool.

Reported by:	manu
Sponsored by:	The FreeBSD Foundation
Fixes:		b60cd486a652 ("ofw: bool-ify OF_hasprop()")

hash(9): introduce hashalloc()/hashfree() KPI

2026-04-12T17:25:51+00:00

This is a more extendable version than traditional hashinit(9).  It allows
different kinds of slot headers with optional locks.

Implement traditional hashinit()/hashdestroy() on top of it.

Reviewed by:		pouria, gallatin
Differential Revision:	https://reviews.freebsd.org/D55904

malloc.9: adjust flag table indentation

2026-03-31T19:55:37+00:00

The current indentation is shorter than all but one of these flags. This
renders much more nicely.

MFC after:	3 days

DEVICE_IDENTIFY.9: Fix function call to detect driver in example code

2026-03-27T14:55:13+00:00

Fixes:          ccabc7c2e556 ("DEVICE_IDENTIFY.9: Modernize description and use cases")
MFC after:      3 days
Sponsored by:   The FreeBSD Foundation

ecn.9: Replace non-ASCII characters

2026-03-19T17:24:49+00:00

Reported by:	maxim
Fixes:		ba4298b05564 ("ecn.9: Add ecn(9) manual")

ecn.9: Add ecn(9) manual

2026-03-19T10:25:53+00:00

Add ecn manual for ip_ecn tunneling functions.

Reviewed by: pauamma_gundo.com, tuexen
Differential Revision: https://reviews.freebsd.org/D53517

crypto_request.9: Fix typo on crypto_initreq arguments

2026-03-16T09:54:13+00:00

The function signature of `crypto_initreq()` was
incorrectly documented.

Signed-off-by:	Zixu Wu 
Reviewed by:	ziaee, pouria
Pull Request:	https://github.com/freebsd/freebsd-src/pull/2077

DEFINE_IFUNC.9: update NOTES

2026-03-12T14:44:46+00:00

ifuncs are now implemented for all architectures, so drop the caveat
statement.

Reviewed by:	kib
Sponsored by:	The FreeBSD Foundation
Differential Revision:	https://reviews.freebsd.org/D55815

Fix typos in manual pages

2026-03-09T18:34:27+00:00

bpf.4: accomodate -> accommodate
hier.7: compatability -> compatibility
namei.9: succesfull -> successful

Signed-off-by: Christos Longros 
Reviewed by: emaste
Differential Revision: https://reviews.freebsd.org/D55746

sys: Don't pass RF_ALLOCATED to bus_alloc_resource*

2026-03-06T21:32:33+00:00

This is a nop as eventually these flags are passed to rman_reserve_resource
which unconditionally sets RF_ALLOCATED in the new flags for a region.
However, it's really a layering violation to use RF_ALLOCATED in relation
to struct resource objects outside of subr_rman.c as subr_rman.c uses
this flag to manage it's internal tracking of allocated vs free regions.

In addition, don't document this as a valid flag in the manual.  I
think the intention here was that if a caller didn't want to pass
RF_ACTIVE or RF_SHAREABLE, they could pass RF_ALLOCATED instead of 0,
but given the layering violation, I think it's best to just pass 0
instead in that case.

NB: The bhnd bus uses RF_ALLOCATED (along with RF_ACTIVE) in a
separate API to manage resource regions that are not struct resource
objects (but a separate wrapper object).  It would perhaps be cleaner
if the chipc_retain_region and chipc_release_region functions used
their own flag constants instead of reusing the rman(9) flags.

Reviewed by:	imp, kib
Differential Revision:	https://reviews.freebsd.org/D55683