On Fri, 18 Jun 1999 14:44:39 +0100, Steve Dodd <dirk@loth.demon.co.uk>
said:
>> What's more useful to know is the function that called kfree. It should
>> be on the call trace line of the oops log.
> Unfortunately, I expect what's happened is that something trashed the slab
> allocator's internal data structures a while before, and the kfree() oops is
> just a side effect of this.
That is one possibility. The other possibilities are that we are
trying to free something twice, or that we're following a field from
an already-freed structure, in which cases the stack trace is
enormously useful.
--Stephen
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/