Winbindd using 100% of CPU. Any solution?

[Jeremy Allison]

On Tue, Nov 19, 2013 at 03:31:55PM -0800, Richard Sharpe wrote:
> Hi folks,
> 
> We are seeing the same problem as in
> http://samba.2283325.n4.nabble.com/Winbind-using-100-CPU-td4646572.html
> 
> This is with Samba 3.6.12+ under FreeBSD.
> 
> Does anyone have a solution?

Ask Jim for his DLIST_ macro changes.

From that link:

-----------------------------------------------------------------------------
I see this in the parent winbind log.  The last 3 entries are changes 
I made to the dlist macros within winbind only.  you can see a 2 
second delay and then a second add of the same item to the child 
winbind list.  No entries in between (and a production system so there 
is reluctance to increase the debug level). 

[2013/03/14 09:08:57.795585,  3] 
winbindd/winbindd_getpwnam.c:56(winbindd_getpwnam_send) 
  getpwnam xx+xxxxxxxxx-112$ 
[2013/03/14 09:08:57.796185,  3] 
winbindd/winbindd_getpwnam.c:56(winbindd_getpwnam_send) 
  getpwnam xx+yyyyyyy 
[2013/03/14 09:09:00.077660,  0] 
winbindd/winbindd_dual.c:1399(fork_domain_child) 
  adding 0x7ff91105a000 to list at 0x7ff911053510 
[2013/03/14 09:09:02.435367,  0] 
winbindd/winbindd_dual.c:1399(fork_domain_child) 
  adding 0x7ff91105a000 to list at 0x7ff91105a000 
[2013/03/14 09:09:02.435510,  0] lib/util.c:1117(smb_panic) 
  PANIC (pid 28628): duplicate 
-----------------------------------------------------------------------------

We need it to panic if a duplicate gets added, then
you can track down why with gsb.