From: Jan Kara <jack@suse.cz>
To: Jeff Layton <jeff.layton@primarydata.com>
Cc: linux-fsdevel@vger.kernel.org
Subject: Deprecated mandatory file locking
Date: Wed, 14 Aug 2019 19:33:45 +0200 [thread overview]
Message-ID: <20190814173345.GB10843@quack2.suse.cz> (raw)
Hello Jeff,
we've got a report from user
(https://bugzilla.suse.com/show_bug.cgi?id=1145007) wondering why his fstab
entry (for root filesystem!) using 'mand' mount option stopped working.
Now I understand your rationale in 9e8925b67a "locks: Allow disabling
mandatory locking at compile time" but I guess there's some work to do wrt
documentation. At least mount(8) manpage could mention that mandatory
locking is broken and may be disabled referencing the rationale in fcntl
manpage? Or the kernel could mention something in the log about failing
mount because of 'mand' mount option? What do you think? Because it took
me some code searching to understand why the mount is actually failing
which we can hardly expect from a normal sysadmin...
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next reply other threads:[~2019-08-14 17:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-14 17:33 Jan Kara [this message]
2019-08-14 17:46 ` Deprecated mandatory file locking Jan Kara
2019-08-15 19:18 ` Jeff Layton
2019-08-16 15:31 ` Jan Kara
2019-11-07 16:15 ` Jan Kara
2019-11-07 18:34 ` Jeff Layton
2019-11-08 10:37 ` Jan Kara
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=20190814173345.GB10843@quack2.suse.cz \
--to=jack@suse.cz \
--cc=jeff.layton@primarydata.com \
--cc=linux-fsdevel@vger.kernel.org \
/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).