On January 16, [EMAIL PROTECTED] wrote:
>
> Unable to handle kernel NULL pointer dereference at virtual address 00000003
> c01ccf91
> *pde = 00000000
> Oops: 0002
> CPU: 0
> EIP: 0010:[<c01ccf91>]
> Using defaults from ksymoops -t elf32-i386 -a i386
> EFLAGS: 00010086
> eax: ffffffff ebx: c1490400 ecx: cfdeb000 edx: cfeed13c
> esi: cfdeb000 edi: 00001e29 ebp: 00000013 esp: cfba7e80
> ds: 0018 es: 0018 ss: 0018
> Process raid5syncd (pid: 9, stackpage=cfba7000)
> Stack: c01ccfe0 cfdeb000 c1490400 00000000 c01cd430 c1490400 c1490400 0003c53c
> 00001e29 00000013 00000000 00000000 cfba6000 00001000 00000000 00000000
> 00000000 c1490400 c01cf2a8 c1490400 00078a78 00000000 00000000 cfba6000
> Call Trace: [<c01ccfe0>] [<c01cd430>] [<c01cf2a8>] [<c01d708b>] [<c01cf40f>]
>[<c01d63cd>] [<c01074b8>]
> Code: 89 50 04 8b 51 04 8b 01 89 02 c7 41 04 00 00 00 00 c3 8d b6
>
> >>EIP; c01ccf91 <remove_hash+11/30> <=====
> Trace; c01ccfe0 <get_free_stripe+30/50>
....
This is really odd.
It looks like sh->hash_next == -1.
But, sh->hash_next is only ever set from
->hash_next for some other sh, by the line
*sh->hash_pprev = sh->hash_next;
in remove_hash, or to an entry from the stripe_hashtbl array.
and stripe_hashtbl[] is only ever set to the address of a stripe_head,
or to the value of a sh->hash_next, or to zero at initialisation.
Or in short "this cannot happen" :-)
Is there any chance of a memory error?
Has this happened more than once?
NeilBrown
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
