From: Petr Tesarik <ptesarik@suse.cz>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] fs/Kconfig: default to no mandatory locking
Date: Tue, 28 Jan 2020 14:53:47 +0100 [thread overview]
Message-ID: <20200128145347.5e4fc5db@ezekiel.suse.cz> (raw)
[-- Attachment #1: Type: text/plain, Size: 644 bytes --]
If the help text says this code is dead, the option itself should
not default to y.
Signed-off-by: Petr Tesarik <ptesarik@suse.com>
---
fs/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/Kconfig b/fs/Kconfig
index 7b623e9fc1b0..fc60b8bbebc2 100644
--- a/fs/Kconfig
+++ b/fs/Kconfig
@@ -103,7 +103,7 @@ config FILE_LOCKING
config MANDATORY_FILE_LOCKING
bool "Enable Mandatory file locking"
depends on FILE_LOCKING
- default y
+ default n
help
This option enables files appropriately marked files on appropriely
mounted filesystems to support mandatory locking.
--
2.16.4
[-- Attachment #2: Digitální podpis OpenPGP --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2020-01-28 14:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-28 13:53 Petr Tesarik [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-01-28 14:28 [PATCH] fs/Kconfig: default to no mandatory locking Petr Tesarik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200128145347.5e4fc5db@ezekiel.suse.cz \
--to=ptesarik@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).