Page MenuHomeFreeBSD

sbuf: make assertion message a lot more useable
ClosedPublic

Authored by bz on Mar 18 2026, 4:00 PM.
Tags
None
Referenced Files
Unknown Object (File)
Thu, Jun 25, 3:46 AM
Unknown Object (File)
Sat, Jun 20, 10:14 AM
Unknown Object (File)
Thu, Jun 18, 7:38 AM
Unknown Object (File)
Wed, Jun 17, 8:27 AM
Unknown Object (File)
Tue, Jun 16, 9:28 PM
Unknown Object (File)
Tue, Jun 16, 10:31 AM
Unknown Object (File)
Mon, Jun 8, 5:40 PM
Unknown Object (File)
May 23 2026, 3:01 PM
Subscribers

Details

Summary

Saying that we are called with an (un)finished or corrupted sbuf
is like saying "error" (though [un]finished is an extra hint).

Add the pointer to the sbuf so one could easily check it,
add the flags we are checking so one could see quickly about
a possible state mismatch.

Given we already dereference the pointer in the KASSERT there is no
extra harm adding it to the message.

Found while: testing lindebugfs changes
Sponsored by: The FreeBSD Foundation
MFC after: 3 days

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable