Date: Mon, 29 Jul 1996 20:59:27 +0900 (JST) From: Michael Hancock <michaelh@cet.co.jp> To: hackers@FreeBSD.ORG Subject: kernel assertions Message-ID: <Pine.SV4.3.93.960729203716.28611B-100000@parkplace.cet.co.jp> In-Reply-To: <199607290924.SAA00390@chiota>
next in thread | previous in thread | raw e-mail | index | archive | help
Any comments on introducing an assertion macro for kernel code that panics
if the expression is false and does nothing otherwise. It would also be
very cool to preprocess it out with something like a -NDEBUG flag. It
could be called KASSERT or KERN_ASSERT.
Benefits:
1) You write most of your code assuming the parameters are correct. This
would get rid of a few if ... then ... else's.
2) You define your function requirements clearly to callers of your
function.
An example follows below:
Original version
----------------
/*
* remove the buffer from the appropriate free list
*/
void
bremfree(struct buf * bp)
{
int s = splbio();
if (bp->b_qindex != QUEUE_NONE) {
TAILQ_REMOVE(&bufqueues[bp->b_qindex], bp, b_freelist);
bp->b_qindex = QUEUE_NONE;
} else {
panic("bremfree: removing a buffer when not on a queue");
}
splx(s);
}
KERN_ASSERT version
---------------
/*
* remove the buffer from the appropriate free list
*/
void
bremfree(struct buf * bp)
{
int s = splbio();
KERN_ASSERT(bp->b_qindex != QUEUE_NONE)
TAILQ_REMOVE(&bufqueues[bp->b_qindex], bp, b_freelist);
bp->b_qindex = QUEUE_NONE;
splx(s);
}
This was a simple example but I'm sure it could make code a lot less
intricate in other places.
Confident performance freaks can preprocess away a few clock cycles. This
could add up for frequently called functions.
--
Mike Hancock
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.SV4.3.93.960729203716.28611B-100000>