From: Jeff Layton <jlayton@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Bruce Fields <bfields@fieldses.org>,
linux-fsdevel@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>
Subject: [GIT PULL] file locking change for v5.14
Date: Sat, 21 Aug 2021 07:44:09 -0400 [thread overview]
Message-ID: <31485fdcfad7852abb7f29d73ae0ab718c6357bb.camel@kernel.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1307 bytes --]
The following changes since commit 3dbdb38e286903ec220aaf1fb29a8d94297da246:
Merge branch 'for-5.14' of git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup (2021-07-01 17:22:14 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jlayton/linux.git locks-v5.14
for you to fetch changes up to fdd92b64d15bc4aec973caa25899afd782402e68:
fs: warn about impending deprecation of mandatory locks (2021-08-21 07:32:45 -0400)
----------------------------------------------------------------
Hi Linus,
As discussed on the list, this patch just adds a new warning for folks
who still have mandatory locking enabled and actually mount with "-o
mand". I'd like to get this in for v5.14 so we can push this out into
stable kernels and hopefully reach folks who have mounts with -o mand.
For now, I'm operating under the assumption that we'll fully remove this
support in v5.15, but we can move that out if any legitimate users of
this facility speak up between now and then.
----------------------------------------------------------------
Jeff Layton (1):
fs: warn about impending deprecation of mandatory locks
fs/namespace.c | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
--
Jeff Layton <jlayton@kernel.org>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 862 bytes --]
next reply other threads:[~2021-08-21 11:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-21 11:44 Jeff Layton [this message]
2021-08-21 18:31 ` pr-tracker-bot
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=31485fdcfad7852abb7f29d73ae0ab718c6357bb.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=bfields@fieldses.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®