from time to time smbd crashes when I access network shares. FreeBSD-5.3, samba-3.0.14a I'll try to recompile with debugging information, now just backtrace (gdb) backtrace #0 0x2868e1d7 in kill () from /lib/libc.so.5 #1 0x2868327e in raise () from /lib/libc.so.5 #2 0x286f5627 in abort () from /lib/libc.so.5 #3 0x081a819a in smb_panic2 () #4 0x081a7ff4 in smb_panic () #5 0x08196d25 in fault_report () #6 0x08196d7a in sig_fault () #7 0xbfbfff94 in ?? () #8 0x0000000b in ?? () #9 0x0000000c in ?? () #10 0xbfbfc670 in ?? () #11 0x72662e65 in ?? () #12 0x08196d6c in fault_report () #13 0x081a82be in is_in_path () #14 0x080b45af in dos_mode () #15 0x080a8dde in get_lanman2_dir_entry () #16 0x080aa49c in call_trans2findfirst () #17 0x080b28ae in reply_trans2 () #18 0x080c78f8 in switch_message () #19 0x080c7989 in construct_reply () #20 0x080c7ca2 in process_smb () #21 0x080c87f6 in smbd_process () #22 0x0820e128 in main ()
(In reply to comment #0) I recompiled smbd with -ggdb, backtrace gives more information now (gdb) backtrace #0 0x286f61d7 in kill () from /lib/libc.so.5 #1 0x286eb27e in raise () from /lib/libc.so.5 #2 0x2875d627 in abort () from /lib/libc.so.5 #3 0x081f59d6 in smb_panic2 (why=0x82c2fc2 "internal error", decrement_pid_count=1) at lib/util.c:1561 #4 0x081f580f in smb_panic (why=0x82c2fc2 "internal error") at lib/util.c:1445 #5 0x081e01d2 in fault_report (sig=11) at lib/fault.c:41 #6 0x081e0239 in sig_fault (sig=11) at lib/fault.c:64 #7 0xbfbfff94 in ?? () #8 0x0000000b in ?? () #9 0x0000000c in ?? () #10 0xbfbfd090 in ?? () #11 0x00006169 in ?? () #12 0x081e0228 in fault_report (sig=-1077947424) at lib/fault.c:57 #13 0x081f5c0b in is_in_path (name=0xbfbfe4b0 "rsaenh.dll", namelist=0x830bd88, case_sensitive=0) at lib/util.c:1632 #14 0x080c6dc4 in check_name (name=0xbfbfe4b0 "rsaenh.dll", conn=0x836c000) at smbd/filename.c:404 #15 0x080bc497 in call_trans2qfilepathinfo (conn=0x836c000, inbuf=0x837b000 "", outbuf=0x839c000 "", length=102, bufsize=131072, pparams=0xbfbfe9bc, total_params=30, ppdata=0xbfbfe9b8, total_data=0, max_data_bytes=40) at smbd/trans2.c:2431 #16 0x080c3994 in reply_trans2 (conn=0x836c000, inbuf=0x837b000 "", outbuf=0x839c000 "", length=102, bufsize=131072) at smbd/trans2.c:4474 #17 0x080ddf03 in switch_message (type=50, inbuf=0x837b000 "", outbuf=0x839c000 "", size=102, bufsize=131072) at smbd/process.c:968 #18 0x080ddfba in construct_reply (inbuf=0x837b000 "", outbuf=0x839c000 "", size=102, bufsize=131072) at smbd/process.c:998 #19 0x080de338 in process_smb (inbuf=0x837b000 "", outbuf=0x839c000 "") at smbd/process.c:1098 #20 0x080df108 in smbd_process () at smbd/process.c:1558 #21 0x08271d1b in main (argc=4, argv=0xbfbfec64) at smbd/server.c:951
problem disappeared when I commented netatalk VFS module. no crashes anymore.
severity should be determined by the developers and not the reporter.
maybe someone will want to update the netatalk vfs module.