diff options
| author | Jeff Layton <jlayton@kernel.org> | 2022-11-11 08:11:53 -0500 |
|---|---|---|
| committer | Steve French <stfrench@microsoft.com> | 2022-12-11 08:33:31 -0600 |
| commit | 7ecbe92696bb7fe32c80b6cf64736a0d157717a9 (patch) | |
| tree | 4a2d3d21669f0540e770bcb1490ea4a83fec227c /security/integrity | |
| parent | 37ba7b005a7a4454046bd8659c7a9c5330552396 (diff) | |
| download | linux-stable-7ecbe92696bb7fe32c80b6cf64736a0d157717a9.tar.gz linux-stable-7ecbe92696bb7fe32c80b6cf64736a0d157717a9.tar.bz2 linux-stable-7ecbe92696bb7fe32c80b6cf64736a0d157717a9.zip | |
ksmbd: use F_SETLK when unlocking a file
ksmbd seems to be trying to use a cmd value of 0 when unlocking a file.
That activity requires a type of F_UNLCK with a cmd of F_SETLK. For
local POSIX locking, it doesn't matter much since vfs_lock_file ignores
@cmd, but filesystems that define their own ->lock operation expect to
see it set sanely.
Cc: David Howells <dhowells@redhat.com>
Signed-off-by: Jeff Layton <jlayton@kernel.org>
Reviewed-by: David Howells <dhowells@redhat.com>
Acked-by: Namjae Jeon <linkinjeon@kernel.org>
Signed-off-by: Steve French <stfrench@microsoft.com>
Diffstat (limited to 'security/integrity')
0 files changed, 0 insertions, 0 deletions