[Samba] CIFS VFS: in dmesg when Linux accesses eComStation's (OS/2) FAT filesystem shares

[Jeremy Allison]

On Thu, Apr 23, 2020 at 02:59:18AM -0400, Felix Miata via samba wrote:
> Items in dmesg when FAT share's are accessed from web browser:
> CIFS VFS: bogus file nlink value 0

nlink should never be zero. If an SMB server
returns that, then the CIFSFS client will have
to fake it to 1 at least.

> When accessed from FC/L (OFM (orthodox filemanager)):
> CIFS VFS: illegal date, month 0 day: 0
> 
> When the share is initially mounted:
> CIFS: Attempting to mount //hostname/E
> Use of the less secure dialect vers=1.0 is not recommended unless required for
> access to very old servers
> CIFS VFS: Send error in QFSAttributeInfo = -95
> 
> /etc/fstab entry for //hostname/E:
> //hostname/E /smbmnt/hostname/E cifs
> ro,credentials=/etc/samba/hostname.cred,sec=lanman,vers=1.0,servern=HOSTNAME,domain=MYHOST,port=139,dir_mode=0555,file_mode=0664,noserverino,noauto
> 0 0
> 
> Kernel, Samba and CIFS client versions:
> Linux 00srv 4.12.14-lp151.28.44-default #1 SMP Fri Mar 20 18:20:20 UTC 2020
> (dbf1aea) x86_64 x86_64 x86_64 GNU/Linux
> cifs-utils-6.9-lp151.4.3.1.x86_64
> samba-4.9.5+git.296.3dd62eee45e-lp151.2.21.1.x86_64
> samba-client-4.9.5+git.296.3dd62eee45e-lp151.2.21.1.x86_64
> 
> What needs to be done to quiet dmesg when these file access occur? These didn't
> occur until some not all that recent updates to Samba/CIFS versions, maybe a year
> or more, I'm not sure, but ISTR once upon a time complete silence from such touches.

Can you send in a wireshark trace of the client talking to
the OS/2 server ?