Bug 3075 - Signal 11 when wbinfo -r a particular user
Signal 11 when wbinfo -r a particular user
Status: RESOLVED FIXED
Product: Samba 3.0
Classification: Unclassified
Component: winbind
3.0.20
x86 Linux
: P3 normal
: none
Assigned To: Samba Bugzilla Account
Samba QA Contact
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2005-09-08 17:02 UTC by Tom Hibbert
Modified: 2005-09-29 08:52 UTC (History)
0 users

See Also:


Attachments
smb.conf from the affected machine (600 bytes, application/octet-stream)
2005-09-08 17:05 UTC, Tom Hibbert
no flags Details
pertinent winbind log fragment (113.58 KB, application/octet-stream)
2005-09-08 17:06 UTC, Tom Hibbert
no flags Details
valgrind output: 1 of 7 (7.70 KB, application/octet-stream)
2005-09-08 17:09 UTC, Tom Hibbert
no flags Details
valgrind output: 2 of 7 (11.61 KB, application/octet-stream)
2005-09-08 17:09 UTC, Tom Hibbert
no flags Details
valgrind output: 3 of 7 (3.46 KB, application/octet-stream)
2005-09-08 17:09 UTC, Tom Hibbert
no flags Details
valgrind output: 4 of 7 (4.20 KB, application/octet-stream)
2005-09-08 17:11 UTC, Tom Hibbert
no flags Details
valgrind output: 5 of 7 (4.20 KB, application/octet-stream)
2005-09-08 17:12 UTC, Tom Hibbert
no flags Details
valgrind output: 6 of 7 (5.46 KB, text/plain)
2005-09-08 17:12 UTC, Tom Hibbert
no flags Details
valgrind output: 7 of 7 (4.29 KB, application/octet-stream)
2005-09-08 17:13 UTC, Tom Hibbert
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Tom Hibbert 2005-09-08 17:02:44 UTC
We are experiencing a consistent crash here in an ADS scenario authenticating 
against Windows 2000 Server SP4 Update Rollup 1. 
 
This machine is running samba/winbindd for the purpose of authenticating squid 
users. The system is Debian Sarge. We are running the latest Samba 3.0.20. 
 
We noticed that Squid was failing to authenticate a particular user, so we had 
a look at winbind to find out what was happening. Then we found that when we 
ran wbinfo -r on the user, it reliably segfaults with signal 11. It probably 
occurs with other users, too, but we havent run through all of them as it 
doesnt seem likely to bring any extra information. 
 
I've recompiled samba with --enable-debug and --enable-developer to improve 
debugging. 
 
Andrew Bartlett on #samba-technical requested we get a valgrind trace of what 
is going on. I personally dont have much experience with Valgrind and the Samba 
HOWTO section on "Bugs" doesnt cover it either, so I've gone ahead and attached 
the full valgrind log output. 
 
No pertinent information appears on the event viewer on the domain controller.
Comment 1 Tom Hibbert 2005-09-08 17:05:18 UTC
Created attachment 1417 [details]
smb.conf from the affected machine
Comment 2 Tom Hibbert 2005-09-08 17:06:53 UTC
Created attachment 1418 [details]
pertinent winbind log fragment
Comment 3 Tom Hibbert 2005-09-08 17:09:11 UTC
Created attachment 1419 [details]
valgrind output: 1 of 7
Comment 4 Tom Hibbert 2005-09-08 17:09:33 UTC
Created attachment 1420 [details]
valgrind output: 2 of 7
Comment 5 Tom Hibbert 2005-09-08 17:09:58 UTC
Created attachment 1421 [details]
valgrind output: 3 of 7
Comment 6 Tom Hibbert 2005-09-08 17:11:37 UTC
Created attachment 1422 [details]
valgrind output: 4 of 7
Comment 7 Tom Hibbert 2005-09-08 17:12:17 UTC
Created attachment 1423 [details]
valgrind output: 5 of 7
Comment 8 Tom Hibbert 2005-09-08 17:12:44 UTC
Created attachment 1424 [details]
valgrind output: 6 of 7
Comment 9 Tom Hibbert 2005-09-08 17:13:08 UTC
Created attachment 1425 [details]
valgrind output: 7 of 7
Comment 10 Gerald (Jerry) Carter 2005-09-29 08:52:36 UTC
We think that the crashes are resolved in 3.0.20a.  Please retest
the current SAMBA_3_0_RELEASE tree.