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
F167368739: D55919.id174090.diff
Fri, Aug 21, 10:02 AM
F167359775: D55919.id174090.diff
Fri, Aug 21, 7:23 AM
Unknown Object (File)
Sun, Aug 16, 9:02 PM
Unknown Object (File)
Sat, Aug 15, 8:13 AM
Unknown Object (File)
Wed, Aug 12, 12:45 PM
Unknown Object (File)
Wed, Aug 12, 12:43 PM
Unknown Object (File)
Wed, Aug 12, 7:40 AM
Unknown Object (File)
Tue, Aug 11, 11:36 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