Page MenuHomeFreeBSD
Differential D55919

sbuf: make assertion message a lot more useable
ClosedPublic
Actions

Authored by bz on Mar 18 2026, 4:00 PM.
Tags
None
Referenced Files
Unknown Object (File)
Tue, Aug 4, 6:37 AM
Unknown Object (File)
Tue, Aug 4, 4:30 AM
Unknown Object (File)
Tue, Aug 4, 2:05 AM
Unknown Object (File)
Mon, Aug 3, 3:21 AM
Unknown Object (File)
Thu, Jul 30, 7:32 AM
Unknown Object (File)
Thu, Jul 30, 1:50 AM
Unknown Object (File)
Mon, Jul 27, 4:10 PM
Unknown Object (File)
Sun, Jul 19, 5:50 PM
View All 53 Files
Subscribers
imp
olce

Details

Reviewers
jhb
Commits
rGd5d08dea8443: sbuf: make assertion message a lot more useable
rG40be04834308: sbuf: make assertion message a lot more useable
rG2ce06d25431a: sbuf: make assertion message a lot more useable
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

Revision Contents
Changeset List

PathSize
sys/
kern/
4 lines

Diff 174090

View Options

sys/kern/subr_sbuf.c

Loading...