are SMB TID's specific to the SMB UID used in the tree connect call?

[Jeff Layton-4]

I've been looking at what it will take to implement multisession mounts
in CIFS. Apologies if I'm not using the right terminology here...

I've run up against the following question however. CIFS currently
keeps a list of Tree Connect ID's (TID's) per SMB session. When I
cleaned up this code a while back, my assumption was that TID's should
only be used with the SMB UID that was used to perform the tree connect.

The existing MultiuserMount code in CIFS however violates this rule. It
makes CIFS replace the SMB UID in a call with another one, but the TID
stays the same.

It seems to work fine however. This leads me to believe that it's OK to
use a TID with a different UID. Is that the case?

If so, then will the TID continue to be valid even after the smb
session is torn down?

Thanks,
--
Jeff Layton <jlayton@...>
_______________________________________________
linux-cifs-client mailing list
linux-cifs-client@...
https://lists.samba.org/mailman/listinfo/linux-cifs-client

[Volker Lendecke]

On Wed, Aug 26, 2009 at 03:29:25PM -0500, Christopher R. Hertel wrote:
> If the UID is invalidated using an SMB_COM_LOGOFF_ANDX or such, then the TID
> is still valid.  The TID is valid until a Tree Disconnect is performed or
> the VC is closed.
>
> ...at least, that's what's supposed to happen.  :)

At least from what I'm told SMB2 is different in this
respect.

Volker


_______________________________________________
linux-cifs-client mailing list
linux-cifs-client@...
https://lists.samba.org/mailman/listinfo/linux-cifs-client