sin/samba-mirror
1
0
Fork 0
mirror of https://github.com/samba-team/samba.git synced 2025-01-08 21:18:16 +03:00
Code

s3:locking: Fix code spelling

Browse Source 
Signed-off-by: Andreas Schneider <asn@samba.org>
Reviewed-by: Andrew Bartlett <abartlet@samba.org>
This commit is contained in:
Andreas Schneider 2023-07-13 08:50:21 +02:00 committed by Andreas Schneider
parent f64add9947
commit b746f77732
3 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
source3/locking/brlock.c
View File

@ -877,7 +877,7 @@ static NTSTATUS brl_lock_posix(struct byte_range_lock *br_lck,
/*
* Break oplocks while we hold a brl. Since lock() and unlock() calls
* are not symetric with POSIX semantics, we cannot guarantee our
* are not symmetric with POSIX semantics, we cannot guarantee our
* contend_level2_oplocks_begin/end calls will be acquired and
* released one-for-one as with Windows semantics. Therefore we only
* call contend_level2_oplocks_begin if this is the first POSIX brl on

2
source3/locking/locking.c
View File

@ -435,7 +435,7 @@ void locking_close_file(files_struct *fsp,
/*
* Unlocks must trigger dbwrap_watch watchers,
* normally in smbd_do_unlocking. Here it's done
* implictly, we're closing the file and thus remove a
* implicitly, we're closing the file and thus remove a
* share mode. This will wake the waiters.
*/
brl_close_fnum(br_lck);

2
source3/locking/posix.c
View File

@ -920,7 +920,7 @@ bool set_posix_lock_windows_flavour(files_struct *fsp,
}
/*
* Windows is very strange. It allows read locks to be overlayed
* Windows is very strange. It allows read locks to be overlaid
* (even over a write lock), but leaves the write lock in force until the first
* unlock. It also reference counts the locks. This means the following sequence :
*