diff options
author | Steve French <sfrench@us.ibm.com> | 2008-12-02 17:24:33 +0000 |
---|---|---|
committer | Steve French <sfrench@us.ibm.com> | 2008-12-26 02:29:10 +0000 |
commit | 13a6e42af8d90e2e8eb7fa50adf862a525b70518 (patch) | |
tree | 5d6021da7bc49b75cca5a0947f89bde7233ebce4 /fs/cifs/CHANGES | |
parent | d5c5605c27c92dac6de1a7a658af5b030847f949 (diff) | |
download | linux-13a6e42af8d90e2e8eb7fa50adf862a525b70518.tar.gz linux-13a6e42af8d90e2e8eb7fa50adf862a525b70518.tar.bz2 linux-13a6e42af8d90e2e8eb7fa50adf862a525b70518.zip |
[CIFS] add mount option to send mandatory rather than advisory locks
Some applications/subsystems require mandatory byte range locks
(as is used for Windows/DOS/OS2 etc). Sending advisory (posix style)
byte range lock requests (instead of mandatory byte range locks) can
lead to problems for these applications (which expect that other
clients be prevented from writing to portions of the file which
they have locked and are updating). This mount option allows
mounting cifs with the new mount option "forcemand" (or
"forcemandatorylock") in order to have the cifs client use mandatory
byte range locks (ie SMB/CIFS/Windows/NTFS style locks) rather than
posix byte range lock requests, even if the server would support
posix byte range lock requests. This has no effect if the server
does not support the CIFS Unix Extensions (since posix style locks
require support for the CIFS Unix Extensions), but for mounts
to Samba servers this can be helpful for Wine and applications
that require mandatory byte range locks.
Acked-by: Jeff Layton <jlayton@redhat.com>
CC: Alexander Bokovoy <ab@samba.org>
Signed-off-by: Steve French <sfrench@us.ibm.com>
Diffstat (limited to 'fs/cifs/CHANGES')
-rw-r--r-- | fs/cifs/CHANGES | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/fs/cifs/CHANGES b/fs/cifs/CHANGES index e078b7aea143..3d848f463c44 100644 --- a/fs/cifs/CHANGES +++ b/fs/cifs/CHANGES @@ -1,3 +1,9 @@ +Version 1.56 +------------ +Add "forcemandatorylock" mount option to allow user to use mandatory +rather than posix (advisory) byte range locks, even though server would +support posix byte range locks. + Version 1.55 ------------ Various fixes to make delete of open files behavior more predictable |