Bug 8064 - Crash in smbd/service.c
Summary: Crash in smbd/service.c
Status: NEW
Alias: None
Product: Samba 3.5
Classification: Unclassified
Component: Domain Control (show other bugs)
Version: 3.5.8
Hardware: All All
: P5 normal
Target Milestone: ---
Assignee: Guenther Deschner
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-06 16:23 UTC by Chuck Short (mail address dead)
Modified: 2011-04-07 19:53 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Chuck Short (mail address dead) 2011-04-06 16:23:52 UTC
Hi,

This was recently reported in launchpad at: 

https://bugs.launchpad.net/ubuntu/+source/samba/+bug/747387

I have included the backtrace here as well:

#0  0x0012e416 in make_connection_snum (sconn=0x6, snum=-1075683360, vuser=0x0, password=..., pdev=0x100fce5 <Address 0x100fce5 out of bounds>, pstatus=0x1101468) at smbd/service.c:1070
        conn = 0x1
        smb_fname_cpath = 0x0
        dev = "\215\000\000\000\000\020t_\342\277 \000\000\000\000\000\000\000\356\a\001\001\274\274X\"", '\000' <repeats 16 times>"\345, \374\000\001h\024\020\001\004\000\000\000\345\374\000\001\r\000\000\000\r\000\000\000-\000\000\000\370\023\020\001_\244\r\001\070\000\000\000\356\a\001\001\000\000\000\000\024\306\000\001\300\023\020\001\360\023\020\001\360\023\020\001\345\374\000\001h\024\020\001\364\377\017\001\300\023\020\001\r\000\000\000\002\000\000\000\001\000\000\000\370\023\020\001\000\000\000\000\000\000\000\020-\000\000\000 ", '\000' <repeats 35 times>, "\v\341\374", '\000' <repeats 66 times>
        ret = <value optimized out>
        addr = "\000\000\000\000\000\000\001\000\000\000@_\342\277\362\317\000\001$_\342\277\000\000\000\000\000\000\000\000\001\000\000\000\340F\177\267\000\000\000\000\016\000\000"
        status = <value optimized out>
        __FUNCTION__ = "make_connection_snum"

If you have any questions please let me know.

Regards
chuck
Comment 1 Volker Lendecke 2011-04-07 19:53:24 UTC
If this is reproducable, would it be possible to run smbd under valgrind --tool=memcheck? Also, could you upload your smb.conf and if you have it a debug level 10 log of smbd leading to this crash?

Thanks,

Volker