samba - May 2004 - VFS calls after disconnect ?

Hello,

I am developing a VFS module which makes connexions to a database,
and disconnects from the database when SMB_VFS_DISCONNECT is called.
I have trouble when a "map network drive" is started: it seems that a 
double parallel connexion is
made, with a pattern like:
        - SMB_VFS_CONNECT: my module connects to the database
        - SMB_VFS_CONNECT: my module does nothing, since it is already 
initialized
        - some other VFS calls
        - SMB_VFS_DISCONNECT: my module disconnects from the database
        - **** some other VFS call, e.g. VFS_STAT, which fails because I 
disconnected from my database ****
        - SMB_VFS_CONNECT: my module connects to the database
        - then the connection works well

If a Windows program maps the network drive and uses it immediately, it 
can fail if it uses it
before the initial SMB_VFS_DISCONNECT.

The share is used from Windows 2000 Professional.

Is is normal to have the initial double SMB_VFS_CONNECT and 
SMB_VFS_DISCONNECT ?
Should I count the number of SMB_VFS_CONNECT, and really disconnect only 
when the same
number of SMB_VFS_DISCONNECT is called ?
Or did I miss something else ?

Best regards,
Yves Lejeune.

On Mon, May 24, 2004 at 10:03:09AM +0200, yves.lejeune@kodak.com
wrote:
> 
> Is is normal to have the initial double SMB_VFS_CONNECT and 
> SMB_VFS_DISCONNECT ?
> Should I count the number of SMB_VFS_CONNECT, and really disconnect only 
> when the same
> number of SMB_VFS_DISCONNECT is called ?
Yes, use a reference count here.

Jeremy.

Hello,
> > 
> > Is is normal to have the initial double SMB_VFS_CONNECT and 
> > SMB_VFS_DISCONNECT ?
> > Should I count the number of SMB_VFS_CONNECT, and really disconnect 
only 
> > when the same
> > number of SMB_VFS_DISCONNECT is called ?
> 
> Yes, use a reference count here.
I tried to store a reference counter in the "vfs_handle_struct::data" 
field, but it does not help:
when SMB_VFS_CONNECT is called the second time for the same process,
its "vfs_handle_struct::data" field is NULL., so I have nothing to 
increment.

Would you know an other way to manage per-connection data ?

Best regards,
Yves.