Alan Cox wrote:
> Its a deliberate debugging trap.
>
> > #if DEBUG
> > if (cachep->flags & SLAB_POISON)
> > if (kmem_check_poison_obj(cachep, objp))
> > BUG();
> > ^^ This one is triggered
>
> Someone freed memory and then
Alan Cox wrote:
Its a deliberate debugging trap.
#if DEBUG
if (cachep-flags SLAB_POISON)
if (kmem_check_poison_obj(cachep, objp))
BUG();
^^ This one is triggered
Someone freed memory and then scribbled on it.
> when this happened, and I was not able to log in onto any console or
> terminal afterwards (probably because tty_open failed very miserably
> on the way?)
Its a deliberate debugging trap.
> #if DEBUG
> if (cachep->flags & SLAB_POISON)
> if
Hello people,
I triggered an "invalid operand" oops in linux-2.4.4-ac9 today, and could
trace it back to the line mm/slab.c:1244. I did nothing really special
when this happened, and I was not able to log in onto any console or
terminal afterwards (probably because tty_open failed very miserably
Hello people,
I triggered an invalid operand oops in linux-2.4.4-ac9 today, and could
trace it back to the line mm/slab.c:1244. I did nothing really special
when this happened, and I was not able to log in onto any console or
terminal afterwards (probably because tty_open failed very miserably
when this happened, and I was not able to log in onto any console or
terminal afterwards (probably because tty_open failed very miserably
on the way?)
Its a deliberate debugging trap.
#if DEBUG
if (cachep-flags SLAB_POISON)
if (kmem_check_poison_obj(cachep, objp))
6 matches
Mail list logo