From: Linus Torvalds <torvalds@linux-foundation.org>
To: Jeff Layton <jlayton@kernel.org>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
"Matthew Wilcox" <willy@infradead.org>,
"Andy Lutomirski" <luto@kernel.org>,
"David Laight" <David.Laight@aculab.com>,
"David Hildenbrand" <david@redhat.com>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Ingo Molnar" <mingo@redhat.com>,
"Borislav Petkov" <bp@alien8.de>,
"H. Peter Anvin" <hpa@zytor.com>,
"Al Viro" <viro@zeniv.linux.org.uk>,
"Alexey Dobriyan" <adobriyan@gmail.com>,
"Steven Rostedt" <rostedt@goodmis.org>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
"Arnaldo Carvalho de Melo" <acme@kernel.org>,
"Mark Rutland" <mark.rutland@arm.com>,
"Alexander Shishkin" <alexander.shishkin@linux.intel.com>,
"Jiri Olsa" <jolsa@redhat.com>,
"Namhyung Kim" <namhyung@kernel.org>,
"Petr Mladek" <pmladek@suse.com>,
"Sergey Senozhatsky" <sergey.senozhatsky@gmail.com>,
"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
"Rasmus Villemoes" <linux@rasmusvillemoes.dk>,
"Kees Cook" <keescook@chromium.org>,
"Greg Ungerer" <gerg@linux-m68k.org>,
"Geert Uytterhoeven" <geert@linux-m68k.org>,
"Mike Rapoport" <rppt@kernel.org>,
"Vlastimil Babka" <vbabka@suse.cz>,
"Vincenzo Frascino" <vincenzo.frascino@arm.com>,
"Chinwen Chang" <chinwen.chang@mediatek.com>,
"Michel Lespinasse" <walken@google.com>,
"Catalin Marinas" <catalin.marinas@arm.com>,
"Huang Ying" <ying.huang@intel.com>,
"Jann Horn" <jannh@google.com>, "Feng Tang" <feng.tang@intel.com>,
"Kevin Brodsky" <Kevin.Brodsky@arm.com>,
"Michael Ellerman" <mpe@ellerman.id.au>,
"Shawn Anastasio" <shawn@anastas.io>,
"Steven Price" <steven.price@arm.com>,
"Nicholas Piggin" <npiggin@gmail.com>,
"Christian Brauner" <christian.brauner@ubuntu.com>,
"Jens Axboe" <axboe@kernel.dk>,
"Gabriel Krisman Bertazi" <krisman@collabora.com>,
"Peter Xu" <peterx@redhat.com>,
"Suren Baghdasaryan" <surenb@google.com>,
"Shakeel Butt" <shakeelb@google.com>,
"Marco Elver" <elver@google.com>,
"Daniel Jordan" <daniel.m.jordan@oracle.com>,
"Nicolas Viennot" <Nicolas.Viennot@twosigma.com>,
"Thomas Cedeno" <thomascedeno@google.com>,
"Collin Fijalkovich" <cfijalkovich@google.com>,
"Michal Hocko" <mhocko@suse.com>,
"Miklos Szeredi" <miklos@szeredi.hu>,
"Chengguang Xu" <cgxu519@mykernel.net>,
"Christian König" <ckoenig.leichtzumerken@gmail.com>,
"linux-unionfs@vger.kernel.org" <linux-unionfs@vger.kernel.org>,
"Linux API" <linux-api@vger.kernel.org>,
"the arch/x86 maintainers" <x86@kernel.org>,
"<linux-fsdevel@vger.kernel.org>" <linux-fsdevel@vger.kernel.org>,
Linux-MM <linux-mm@kvack.org>,
"Florian Weimer" <fweimer@redhat.com>,
"Michael Kerrisk" <mtk.manpages@gmail.com>
Subject: Re: Removing Mandatory Locks
Date: Thu, 19 Aug 2021 13:31:35 -0700 [thread overview]
Message-ID: <CAHk-=wgD-SNxB=2iCurEoP=RjrciRgLtXZ7R_DejK+mXF2etfg@mail.gmail.com> (raw)
In-Reply-To: <a1385746582a675c410aca4eb4947320faec4821.camel@kernel.org>
On Thu, Aug 19, 2021 at 1:18 PM Jeff Layton <jlayton@kernel.org> wrote:
>
> Now that I think about it a little more, I actually did get one
> complaint a few years ago:
>
> Someone had upgraded from an earlier distro that supported the -o mand
> mount option to a later one that had disabled it, and they had an (old)
> fstab entry that specified it.
Hmm. We might be able to turn the "return -EINVAL" into just a warning.
Yes, yes, currently if you turn off CONFIG_MANDATORY_FILE_LOCKING, we
already do that
VFS: "mand" mount option not supported
warning print, but then we fail the mount.
If CONFIG_MANDATORY_FILE_LOCKING goes away entirely, it might make
sense to turn that warning into something bigger, but then let the
mount continue - since now that "mand" flag would be purely a legacy
thing.
And yes, if we do that, we'd want the warning to be a big ugly thing,
just to make people very aware of it happening. Right now it's a
one-liner that is easy to miss, and the "oh, the mount failed" is the
thing that hopefully informs people about the fact that they need to
enable CONFIG_MANDATORY_FILE_LOCKING.
The logic being that if you can no longer enable mandatory locking in
the kernel, the current hard failure seems overly aggressive (and
might cause boot failures and inability to fix/report things when it
possibly keeps you from using the system at all).
Linus
next prev parent reply other threads:[~2021-08-19 20:32 UTC|newest]
Thread overview: 82+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-12 8:43 [PATCH v1 0/7] Remove in-tree usage of MAP_DENYWRITE David Hildenbrand
2021-08-12 8:43 ` [PATCH v1 1/7] binfmt: don't use MAP_DENYWRITE when loading shared libraries via uselib() David Hildenbrand
2021-08-12 8:43 ` [PATCH v1 2/7] kernel/fork: factor out atomcially replacing the current MM exe_file David Hildenbrand
2021-08-12 9:17 ` Christian Brauner
2021-08-12 8:43 ` [PATCH v1 3/7] kernel/fork: always deny write access to " David Hildenbrand
2021-08-12 10:05 ` Christian Brauner
2021-08-12 10:13 ` David Hildenbrand
2021-08-12 12:32 ` Christian Brauner
2021-08-12 12:38 ` David Hildenbrand
2021-08-12 16:51 ` Linus Torvalds
2021-08-12 19:38 ` David Hildenbrand
2021-08-12 8:43 ` [PATCH v1 4/7] binfmt: remove in-tree usage of MAP_DENYWRITE David Hildenbrand
2021-08-12 8:43 ` [PATCH v1 5/7] mm: remove VM_DENYWRITE David Hildenbrand
2021-08-12 8:43 ` [PATCH v1 6/7] mm: ignore MAP_DENYWRITE in ksys_mmap_pgoff() David Hildenbrand
2021-08-12 8:43 ` [PATCH v1 7/7] fs: update documentation of get_write_access() and friends David Hildenbrand
2021-08-12 12:20 ` [PATCH v1 0/7] Remove in-tree usage of MAP_DENYWRITE Florian Weimer
2021-08-12 12:47 ` David Hildenbrand
2021-08-12 16:17 ` Eric W. Biederman
2021-08-12 17:32 ` Eric W. Biederman
2021-08-12 17:35 ` Andy Lutomirski
2021-08-12 17:48 ` Eric W. Biederman
2021-08-12 18:01 ` Andy Lutomirski
2021-08-12 18:10 ` Linus Torvalds
2021-08-12 18:47 ` Eric W. Biederman
2021-08-13 9:05 ` David Laight
[not found] ` <87h7ft2j68.fsf@disp2133>
2021-08-13 20:51 ` Florian Weimer
2021-08-14 0:31 ` Linus Torvalds
2021-08-14 0:49 ` Andy Lutomirski
2021-08-14 0:54 ` Linus Torvalds
2021-08-14 0:58 ` Linus Torvalds
2021-08-14 1:57 ` Al Viro
2021-08-14 2:02 ` Al Viro
2021-08-14 9:06 ` David Hildenbrand
2021-08-14 7:53 ` Christian Brauner
2021-08-14 19:52 ` David Laight
2021-08-26 17:48 ` Andy Lutomirski
2021-08-26 21:47 ` David Hildenbrand
2021-08-26 22:13 ` Eric W. Biederman
2021-08-27 8:22 ` David Laight
2021-08-27 15:58 ` Eric W. Biederman
2021-09-01 8:28 ` David Hildenbrand
2021-08-27 10:18 ` Christian Brauner
2021-08-14 3:04 ` Matthew Wilcox
2021-08-17 16:48 ` Removing Mandatory Locks Eric W. Biederman
2021-08-17 16:50 ` David Hildenbrand
2021-08-18 9:34 ` Rodrigo Campos
2021-08-19 19:18 ` Jeff Layton
2021-08-19 20:03 ` Willy Tarreau
2021-08-19 18:39 ` Jeff Layton
2021-08-19 19:15 ` Linus Torvalds
2021-08-19 19:55 ` Eric Biggers
2021-08-19 20:18 ` Jeff Layton
2021-08-19 20:31 ` Linus Torvalds [this message]
2021-08-19 21:43 ` Jeff Layton
2021-08-19 22:32 ` Linus Torvalds
2021-08-20 8:30 ` David Laight
2021-08-23 7:55 ` Geert Uytterhoeven
2021-08-23 8:14 ` David Laight
2021-08-20 13:43 ` Steven Rostedt
2021-08-20 16:06 ` Linus Torvalds
2021-08-20 2:10 ` Matthew Wilcox
2021-08-20 6:36 ` Amir Goldstein
2021-08-20 7:14 ` Amir Goldstein
2021-08-20 12:27 ` Jeff Layton
2021-08-20 12:38 ` Willy Tarreau
2021-08-20 13:03 ` Jeff Layton
2021-08-20 13:11 ` Willy Tarreau
2021-08-20 16:30 ` Kees Cook
2021-08-20 19:17 ` H. Peter Anvin
2021-08-20 21:29 ` Jeff Layton
2021-08-21 12:45 ` Jeff Layton
2021-08-23 22:15 ` J. Bruce Fields
2021-08-20 22:31 ` Matthew Wilcox
2021-08-18 7:51 ` [PATCH v1 0/7] Remove in-tree usage of MAP_DENYWRITE Christian Brauner
2021-08-18 15:42 ` J. Bruce Fields
2021-08-19 13:56 ` Eric W. Biederman
2021-08-19 14:33 ` J. Bruce Fields
2021-08-20 12:54 ` Jeff Layton
[not found] ` <162943109106.9892.7426782042253067338@noble.neil.brown.name>
2021-08-20 8:25 ` David Laight
2021-08-12 19:24 ` David Hildenbrand
2021-08-12 18:15 ` Florian Weimer
2021-08-12 18:21 ` Linus Torvalds
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='CAHk-=wgD-SNxB=2iCurEoP=RjrciRgLtXZ7R_DejK+mXF2etfg@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=David.Laight@aculab.com \
--cc=Kevin.Brodsky@arm.com \
--cc=Nicolas.Viennot@twosigma.com \
--cc=acme@kernel.org \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=axboe@kernel.dk \
--cc=bp@alien8.de \
--cc=catalin.marinas@arm.com \
--cc=cfijalkovich@google.com \
--cc=cgxu519@mykernel.net \
--cc=chinwen.chang@mediatek.com \
--cc=christian.brauner@ubuntu.com \
--cc=ckoenig.leichtzumerken@gmail.com \
--cc=daniel.m.jordan@oracle.com \
--cc=david@redhat.com \
--cc=ebiederm@xmission.com \
--cc=elver@google.com \
--cc=feng.tang@intel.com \
--cc=fweimer@redhat.com \
--cc=geert@linux-m68k.org \
--cc=gerg@linux-m68k.org \
--cc=hpa@zytor.com \
--cc=jannh@google.com \
--cc=jlayton@kernel.org \
--cc=jolsa@redhat.com \
--cc=keescook@chromium.org \
--cc=krisman@collabora.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=luto@kernel.org \
--cc=mark.rutland@arm.com \
--cc=mhocko@suse.com \
--cc=miklos@szeredi.hu \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=mtk.manpages@gmail.com \
--cc=namhyung@kernel.org \
--cc=npiggin@gmail.com \
--cc=peterx@redhat.com \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=rppt@kernel.org \
--cc=sergey.senozhatsky@gmail.com \
--cc=shakeelb@google.com \
--cc=shawn@anastas.io \
--cc=steven.price@arm.com \
--cc=surenb@google.com \
--cc=tglx@linutronix.de \
--cc=thomascedeno@google.com \
--cc=vbabka@suse.cz \
--cc=vincenzo.frascino@arm.com \
--cc=viro@zeniv.linux.org.uk \
--cc=walken@google.com \
--cc=willy@infradead.org \
--cc=x86@kernel.org \
--cc=ying.huang@intel.com \
/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).