Bug 201971 - wrong status_to_posix_error mapping
Summary: wrong status_to_posix_error mapping
Status: NEW
Alias: None
Product: File System
Classification: Unclassified
Component: CIFS (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: fs_cifs
Depends on:
Reported: 2018-12-12 08:58 UTC by omgbebebe
Modified: 2018-12-12 13:12 UTC (History)
1 user (show)

See Also:
Kernel Version: 4.19.7
Tree: Mainline
Regression: No

example code to test shared locks (791 bytes, text/x-csrc)
2018-12-12 08:58 UTC, omgbebebe

Description omgbebebe 2018-12-12 08:58:46 UTC
Created attachment 279959 [details]
example code to test shared locks

While resolving a bug with locks on samba shares we found a strange behavior. When a file locked by one node and we trying to lock it from another node it fail with errno 5 (EIO) but in that case errno must be set to (EACCES | EAGAIN). This isn't happening when we try to lock file second time on same node. In this case it returns EACCES as expected. Also this issue not reproduces when we use SMB1 protocol (vers=1.0 in mount options).

Further investigation showed that the mapping from status_to_posix_error is different for SMB1 and SMB2+ implementations. For SMB1 mapping is [NT_STATUS_LOCK_NOT_GRANTED to ERRlock](https://github.com/torvalds/linux/blob/master/fs/cifs/netmisc.c#L322) to [-EACCES](https://github.com/torvalds/linux/blob/master/fs/cifs/netmisc.c#L66)
but for SMB2+ mapping is [STATUS_LOCK_NOT_GRANTED to -EIO](https://github.com/torvalds/linux/blob/master/fs/cifs/smb2maperror.c#L383)

Quick changes in SMB2+ mapping from EIO to EACCES has fixed our issue.

Is it bug in mappings in SMB2/3 implementation or it is a new behaviour that we should take in account in future?

PS. I attached example code to test shared locks. To reproduce our case it should be executed on same shared file twice.

Expected behavior:

nodeA $ ./share_lock /mnt/server_public/file_samba
File locked successfully.
Press any key to exit...

# in another console
nodeA $ ./share_lock /mnt/server_public/file_samba
fcntl error: 13, Permission denied

Wrong behavior:

nodeA $ ./share_lock /mnt/server_public/file_samba
File locked successfully.
Press any key to exit...

# on second node
nodeB $ ./share_lock /mnt/server_public/file_samba
fcntl error: 5, Input/output error

Note You need to log in before you can comment on or make changes to this bug.