[Samba] smbd Crash

[Bruno MACADRE]

Jeremy Allison a écrit :
> On Fri, Oct 02, 2009 at 10:43:07AM +0200, Bruno MACADRE wrote:
>   
>> Hi,
>>
>> 	I don't stop to have problems with samba :s ...
>>
>> 	Now after having workaround the bug of scanning all LDAP users for each
>> connexion... smbd crash very often.
>>
>> 	In some workstation log files i can see something like this :
>>
>> ...
>> [2009/10/01 16:28:12,  2] smbd/open.c:580(open_file)
>>   baala opened file .profiles/firefox/cookies.sqlite-journal read=No
>> write=No (numopen=20)
>> [2009/10/01 16:28:12,  2] smbd/close.c:612(close_normal_file)
>>   baala closed file .profiles/firefox/cookies.sqlite-journal
>> (numopen=19) NT_STATUS_OK
>> *** glibc detected *** /usr/sbin/smbd: realloc(): invalid next size:
>> 0x0955c5c8 ***
>> ======= Backtrace: =========
>> /lib/tls/i686/cmov/libc.so.6[0xb7cca604]
>> /lib/tls/i686/cmov/libc.so.6[0xb7cce1b1]
>> /lib/tls/i686/cmov/libc.so.6(realloc+0x106)[0xb7cceee6]
>> /usr/sbin/smbd(Realloc+0x7d)[0x834326d]
>> /usr/sbin/smbd(brl_lock+0x4a3)[0x82d1f23]
>> /usr/sbin/smbd(do_lock+0x147)[0x82cc517]
>> /usr/sbin/smbd[0x8120467]
>> /usr/sbin/smbd[0x8121e7a]
>> /usr/sbin/smbd(reply_trans2+0x6ef)[0x8123b5f]
>> /usr/sbin/smbd[0x8145848]
>> /usr/sbin/smbd[0x81481ad]
>> /usr/sbin/smbd[0x8148bd2]
>> /usr/sbin/smbd(run_events+0x13c)[0x8353cac]
>> /usr/sbin/smbd(smbd_process+0x791)[0x8147cd1]
>> /usr/sbin/smbd[0x8623a25]
>> /usr/sbin/smbd(run_events+0x13c)[0x8353cac]
>> /usr/sbin/smbd[0x8353f4e]
>> /usr/sbin/smbd(_tevent_loop_once+0x9b)[0x835458b]
>> /usr/sbin/smbd(main+0xc12)[0x8624732]
>> /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe5)[0xb7c71775]
>> /usr/sbin/smbd[0x80c3e91]
>> ======= Memory map: ========
>>     
>
> This is almost certainly bug 6776 which I just
> committed a fix for.
>
> I'm planning a back-port, what specific Samba
> version do you need the fix for ?
>
> Jeremy.
>   

Thanks for this fix, i've patched my Samba 3.4.2 with your fix and the 
locktest2 works fine... Actualy i can't say if this fix solve my 
problem, i've disabled mounting CIFS on my linux boxes because my 
student can't compile on CIFS share (cf my message related to this 
problem), so for instance i've tranformed my CIFS shares in NFS 
shares.... it's less secure but it works...

But the bug 6776 describe a behavior really near of my problem. I will 
tell you if i can re-enabled CIFS on my linux boxes a day !

Thanks for your fix !
Bruno