git: 2ce06d25431a - main - sbuf: make assertion message a lot more useable

The branch main has been updated by bz:

URL: https://cgit.FreeBSD.org/src/commit/?id=2ce06d25431a6c96ef5719165cb73e138a0ed89c

commit 2ce06d25431a6c96ef5719165cb73e138a0ed89c
Author:     Bjoern A. Zeeb <bz@FreeBSD.org>
AuthorDate: 2026-03-18 14:43:15 +0000
Commit:     Bjoern A. Zeeb <bz@FreeBSD.org>
CommitDate: 2026-03-21 21:16:43 +0000

    sbuf: make assertion message a lot more useable
    
    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
    Reviewed by:    jhb
    Differential Revision: https://reviews.freebsd.org/D55919
---
 sys/kern/subr_sbuf.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/sys/kern/subr_sbuf.c b/sys/kern/subr_sbuf.c
index 27e18c114afd..c5673e871df4 100644
--- a/sys/kern/subr_sbuf.c
+++ b/sys/kern/subr_sbuf.c
@@ -124,8 +124,8 @@ _assert_sbuf_state(const char *fun, struct sbuf *s, int state)
 {
 
 	KASSERT((s->s_flags & SBUF_FINISHED) == state,
-	    ("%s called with %sfinished or corrupt sbuf", fun,
-	    (state ? "un" : "")));
+	    ("%s called with %sfinished or corrupt sbuf %p { s_flags %#010x }, "
+		"state %#010x", fun, (state ? "un" : ""), s, s->s_flags, state));
 }
 
 #define	assert_sbuf_integrity(s) _assert_sbuf_integrity(__func__, (s))