On Sun, Jan 17, 1999 at 12:10:12PM -0500, Joseph M . Malicki wrote:
> On Sun, 17 Jan 1999, Stanislav Meduna wrote:
> >I cannot reproduce the crash if I'm doing the find
> >only in the NTFS root. If I do it from /, it comes
> >quite reproducibly (but this is probably only
> >a coincidence).
Hmm, I saw the same / similar Oops the other morning, but as it was 3am
and I had an assignment to hand in, I left alone at the time. I haven't
tried very hard to reproduce it yet, but here is what I found..
Using the same method on this oops report,
Unable to handle kernel NULL pointer dereference at virtual address 00000000
current->tss.cr3 = 00cd7000, |r3 = 00cd7000
*pde = 00000000
Oops: 0002
CPU: 0
EIP: 0010:[<c4814048>]
EFLAGS: 00010202
eax: 00000038 ebx: c3cffee4 ecx: 0000000e edx: 00000038
esi: c0a3ab00 edi: 00000000 ebp: 00000038 esp: c3cffe34
ds: 0018 es: 0018 ss: 0018
Process find (pid: 7917, process nr: 44, stackpage=c3cff000)
..
>>EIP: c4814048 <_end+464f184/4658188>
Trace: c4814b65 <_end+464fca1/4658188>
Trace: c481590f <_end+4650a4b/4658188>
Trace: c4814b4c <_end+464fc88/4658188>
Trace: c4814f5e <_end+465009a/4658188>
Trace: c481abfc <_end+4655d38/4658188>
Trace: c4815b7e <_end+4650cba/4658188>
Trace: c4817bbf <_end+4652cfb/4658188>
Trace: c481abfc <_end+4655d38/4658188>
Trace: c01260ea <sys_newlstat+e/60>
I hand-crafted this call stack :)
ntfs_memcpy
ntfs_put
ntfs_readwrite_attr
ntfs_put
ntfs_find_attr
???????
ntfs_read_attr
ntfs_getdir
???????
> dirrectory..... the odd thing is that i can't see how decode_uni
> would be calling readwrite_attr..... Could you add -DDEBUG to
I reckon that decode_uni wasn't actually called? Is there anything I can
do to help you nail this one? I'll try to remember what I was doing and
see if I can reproduce it..
Cheers,
Steve
-
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/