Page MenuHomeFreeBSD

sbuf: make assertion message a lot more useable
ClosedPublic

Authored by bz on Wed, Mar 18, 4:00 PM.
Tags
None
Referenced Files
F149264239: D55919.diff
Mon, Mar 23, 8:22 AM
Unknown Object (File)
Mon, Mar 23, 3:36 AM
Unknown Object (File)
Mon, Mar 23, 2:50 AM
Unknown Object (File)
Sun, Mar 22, 9:09 PM
Unknown Object (File)
Fri, Mar 20, 5:00 AM
Unknown Object (File)
Wed, Mar 18, 4:06 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