[3.0.1 BUG] when encrypt password = no (not sure, but patch provided)

[Luca Bolcioni]

Hi all,

I'm using samba 3.0.1 with encrypt password = no.

If I smbmount a share on my fileserver everything goes the
usual way, but if I immediately umount it I get the following
error:


Jan 22 15:17:51 samba smbd[30527]:  ============================= 
Jan 22 15:17:51 samba smbd[30527]: [2004/01/22 15:17:51, 0]
lib/fault.c:fault_report(37) 
Jan 22 15:17:51 samba smbd[30527]:   INTERNAL ERROR: Signal 11 in pid
30527 (3.0.1) 
Jan 22 15:17:51 samba smbd[30527]:   Please read the appendix Bugs of
the Samba HOWTO collection 
Jan 22 15:17:51 samba smbd[30527]: [2004/01/22 15:17:51, 0]
lib/fault.c:fault_report(39) 
Jan 22 15:17:51 samba smbd[30527]:  ============================= 
Jan 22 15:17:51 samba smbd[30527]: [2004/01/22 15:17:51, 0]
lib/util.c:smb_panic(1400) 
Jan 22 15:17:51 samba smbd[30527]:   PANIC: internal error 
Jan 22 15:17:51 samba smbd[30527]: [2004/01/22 15:17:51, 0]
lib/util.c:smb_panic(1407) 
Jan 22 15:17:51 samba smbd[30527]:   BACKTRACE: 9 stack frames: 
Jan 22 15:17:51 samba smbd[30527]:    #0 smbd(smb_panic+0x14e)
[0x818f56e] 
Jan 22 15:17:51 samba smbd[30527]:    #1 smbd [0x817f787] 
Jan 22 15:17:51 samba smbd[30527]:    #2 smbd [0x42029098] 
Jan 22 15:17:51 samba smbd[30527]:    #3 smbd(invalidate_vuid+0xc0)
[0x8084bd0] 
Jan 22 15:17:51 samba smbd[30527]:    #4 smbd(invalidate_all_vuids+0x1f)
[0x8084c8f] 
Jan 22 15:17:51 samba smbd[30527]:    #5 smbd(exit_server+0x84)
[0x81ec054] 
Jan 22 15:17:51 samba smbd[30527]:    #6 smbd(main+0x6d4) [0x81ec8b4] 
Jan 22 15:17:51 samba smbd[30527]:    #7 smbd(__libc_start_main+0x95)
[0x42017499] 
Jan 22 15:17:51 samba smbd[30527]:    #8 smbd(ldap_msgfree+0x6d)
[0x80768a1] 
Jan 22 15:17:51 samba smbd[30527]: 


If I use encrypt password = yes the bug does not appear.


Just for my curiosity I looked the code and noticed that the
segfault was on data_blob_free() of the session_key in the vuid
struct.

As this is the first time I look the samba code, I don't know whether
the patch attached to this email (a very stupid one as a matter of
facts) fixes the  bug or not. Hope it helps .....

Let me know if you need further indications on how to reproduce 
the panic error.



Luca