When attempting to connect to a share as the user "HAENGINEERING+kmr", smbd panics. Below is the last command before the panic: I'll attach the full logs and the smb.conf soon. [2003/08/27 13:27:22, 10] lib/system_smbd.c:sys_getgrouplist(113) sys_getgrouplist: user [HAENGINEERS+kmr] [2003/08/27 13:27:22, 0] lib/fault.c:fault_report(36) =============================================================== [2003/08/27 13:27:22, 0] lib/fault.c:fault_report(37) INTERNAL ERROR: Signal 11 in pid 2901 (3.0.0beta3) Please read the appendix Bugs of the Samba HOWTO collection [2003/08/27 13:27:22, 0] lib/fault.c:fault_report(39) =============================================================== [2003/08/27 13:27:22, 0] lib/util.c:smb_panic(1462) PANIC: internal error [2003/08/27 13:27:22, 0] lib/util.c:smb_panic(1469) BACKTRACE: 23 stack frames: #0 smbd(smb_panic+0x14e) [0x81813be]
Created attachment 107 [details] Level 10 log showing panic This is the level 10 log showing the panic occuring.
Created attachment 108 [details] smb.conf
Created attachment 109 [details] Full logs for all connections made This is a tgz containing all of the log files. log.ws161 shows a connection working for user "HAENGINEERS+_testme", log.ws162 shows a similar connection for "HAENGINEERS+kmr" causing smb_panic.
The last thing before the panic is sys_getgrouplist, so I tried a wbinfo -r HAENGINEERS+kmr, and that seemed to work correctly. getent group/passwd also works. Is it possible that one of the groups has too many members? If more information is needed, I can add it. Note: my email account is being slow, so I may not be able to respond quickly.
The user HAENGINEERS+KMR is a member of 42 groups, as reported by: wbinfo -r HAENGINEERS+kmr | wc -l I'm trying to reproduce this on another system (and then I'll try rc1/2).
I've verified that on my local network, with membership in 34 groups, smbd panics. When I'm only a member of 33 groups, it works correctly. I have 300k of level 100 logs, if you're really interested in them. Also: The user HAENGINEERS+KMR was able to prevent this by removing a single group: "Information Technology". Adding this group to a user would make that user cause a panic.
This seems to work correctly in Samba-3.0.0rc2. Tested up to 42 groups.
Thanks fort the feedback (and for letting us know it has been fixed).
originally reported against 3.0.0beta3. CLeaning out non-production release versions.
sorry for the same, cleaning up the database to prevent unecessary reopens of bugs.
database cleanup