Situational Deadlock in Samba 3.0.1

Jeremy Allison jra at
Mon Jan 26 19:48:22 GMT 2004

On Mon, Jan 26, 2004 at 06:50:57AM -0800, Esh, Andrew wrote:
> I have a repeatable test which gets an smbd process stuck in a condition where it won't ever let a client reconnect. The test reboots a host that is running Samba, and leaves a Windows client running which had been connected to the host. Afterward, the Windows client appears to have retained some connection state which Samba is unaware of, and Samba won't accept the state. Here is the log message I am seeing:
> [2004/01/22 15:46:17, 2, pid=4193, effective(0, 0), real(0, 0)] smbd/uid.c:change_to_user(141)
>   change_to_user: Invalid vuid used 101 or vuid not permitted access to share.
> I have reviewed the code at that point, and an invalid vuid should be rejected. It is being checked against a list, which I assume is built during the run life of the smbd. Rebooting the host explains why it was cleared.

Can you attach to this with gdb and get some internal state so we
know what is going on ?



More information about the samba-technical mailing list