aboutsummaryrefslogtreecommitdiffstats
path: root/fs/locks.c
diff options
context:
space:
mode:
authorJeff Layton <jlayton@kernel.org>2019-08-15 15:21:17 -0400
committerJeff Layton <jlayton@kernel.org>2019-08-16 12:13:48 -0400
commitdf2474a22c42ce419b67067c52d71da06c385501 (patch)
tree5de33b456cf345e487089d640689b5aa468224d7 /fs/locks.c
parentlocks: Fix procfs output for file leases (diff)
downloadlinux-dev-df2474a22c42ce419b67067c52d71da06c385501.tar.xz
linux-dev-df2474a22c42ce419b67067c52d71da06c385501.zip
locks: print a warning when mount fails due to lack of "mand" support
Since 9e8925b67a ("locks: Allow disabling mandatory locking at compile time"), attempts to mount filesystems with "-o mand" will fail. Unfortunately, there is no other indiciation of the reason for the failure. Change how the function is defined for better readability. When CONFIG_MANDATORY_FILE_LOCKING is disabled, printk a warning when someone attempts to mount with -o mand. Also, add a blurb to the mandatory-locking.txt file to explain about the "mand" option, and the behavior one should expect when it is disabled. Reported-by: Jan Kara <jack@suse.cz> Reviewed-by: Jan Kara <jack@suse.cz> Signed-off-by: Jeff Layton <jlayton@kernel.org>
Diffstat (limited to 'fs/locks.c')
0 files changed, 0 insertions, 0 deletions