[linux-cifs-client] Symlinks in CIFS client *BROKEN*

[Rob Shinn]

Symlinks on my home directory cause the Linux CIFS client to freeze, 
even when using a Samba backend with CIFS Unix Extensions enabled.

Errors in the syslog look like this

-- Jul 30 21:22:05 dagda kernel: [88044.980000]  CIFS VFS: server not responding
Jul 30 21:22:05 dagda kernel: [88044.980000]  CIFS VFS: server not responding
Jul 30 21:22:05 dagda kernel: [88044.980000]  CIFS VFS: No response for cmd 50 m
id 8596
Jul 30 21:22:05 dagda kernel: [88044.980000]  CIFS VFS: No response for cmd 162 
mid 8597
Jul 30 21:22:05 dagda kernel: [88044.980000]  CIFS VFS: No response for cmd 50 m
id 8593
Jul 30 21:22:05 dagda kernel: [88044.980000]  CIFS VFS: No response for cmd 162 
mid 8601
Jul 30 21:22:05 dagda kernel: [88044.980000]  CIFS VFS: No response for cmd 117 
mid 8600
Jul 30 21:22:05 dagda kernel: [88044.980000]  CIFS VFS: No response for cmd 162 
mid 8599
Jul 30 21:22:08 dagda kernel: [88048.416000]  CIFS VFS: No response for cmd 162 
mid 8598
Jul 30 21:22:08 dagda kernel: [88048.416000]  CIFS VFS: No response for cmd 162 
mid 8588



This is very bad because KDE applications run the DCOPServer which 
creates a symlink in the home directory .DCOPServer/etc.


I'm using version 1.47.  Should I upgrade?  Is this fixed in later 
versions, or still broken?

Please help.  I'm pulling my hair out on this.

--
For a good laugh, call (202) 456-1414