Subject: Re: crash in ntfs read?
To: Jaromir Dolecek <jdolecek@NetBSD.org>
From: Steven M. Bellovin <smb@cs.columbia.edu>
List: current-users
Date: 05/12/2005 10:56:26
In message <20050512134858.GA7934@home.chello.upc.cz>, Jaromir Dolecek writes:
>> ntfs_vgetex(c1eb2000,2738,80,0,2) at netbsd:ntfs_vgetex+0x18f
>
>Can you post what gdb writes if you do 'list *(ntfs_vgetex+0x18f)' ?
>
>> ntfs_ntvattrget(c1eafa00,c31f2880,90,c075e71c,0) at netbsd:ntfs_ntvattrget+0
>x1b0
>> ntfs_ntlookupfile(c1eafa00,d73ce0b0,d7cbbe98,d7cbbe84,c26ece00) at netbsd:nt
>fs_ntlookupfile+0x81
>> ntfs_lookup(d7cbbd94,0,d7cbbdac,c0402bf2,c064f540) at netbsd:ntfs_lookup+0x1
>a4
>> VOP_LOOKUP(d73ce0b0,d7cbbe84,d7cbbe98,e,d7cbbdd4) at netbsd:VOP_LOOKUP+0x2e
>> lookup(d7cbbe74,cb7d0800,400,d7cbbe8c,d7cbbe24) at netbsd:lookup+0x225
>> namei(d7cbbe74,8061b50,60,0,8061c40) at netbsd:namei+0x124
>> sys___lstat13(ccf92634,d7cbbf64,d7cbbf5c,118,202) at netbsd:sys___lstat13+0x
>58
>> syscall_plain() at netbsd:syscall_plain+0x17e
>> --- syscall (number 280) ---
>> 0xbdbbd907:
>> End traceback...
>

I don't have a symbol table for that kernel, so it doesn't produce 
anything.  I've booted a newer kernel, with -g; I expect another crash 
within a few days...

		--Prof. Steven M. Bellovin, http://www.cs.columbia.edu/~smb