[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <9fed831a-b311-4a23-8f3a-eb7ddff9b102@www.fastmail.com>
Date: Thu, 12 Aug 2021 11:01:36 -0700
From: "Andy Lutomirski" <luto@...nel.org>
To: "Eric W. Biederman" <ebiederm@...ssion.com>
Cc: "David Hildenbrand" <david@...hat.com>,
"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>,
"Linus Torvalds" <torvalds@...ux-foundation.org>,
"Andrew Morton" <akpm@...ux-foundation.org>,
"Thomas Gleixner" <tglx@...utronix.de>,
"Ingo Molnar" <mingo@...hat.com>, "Borislav Petkov" <bp@...en8.de>,
"H. Peter Anvin" <hpa@...or.com>,
"Al Viro" <viro@...iv.linux.org.uk>,
"Alexey Dobriyan" <adobriyan@...il.com>,
"Steven Rostedt" <rostedt@...dmis.org>,
"Peter Zijlstra (Intel)" <peterz@...radead.org>,
"Arnaldo Carvalho de Melo" <acme@...nel.org>,
"Mark Rutland" <mark.rutland@....com>,
"Alexander Shishkin" <alexander.shishkin@...ux.intel.com>,
"Jiri Olsa" <jolsa@...hat.com>,
"Namhyung Kim" <namhyung@...nel.org>,
"Petr Mladek" <pmladek@...e.com>,
"Sergey Senozhatsky" <sergey.senozhatsky@...il.com>,
"Andy Shevchenko" <andriy.shevchenko@...ux.intel.com>,
"Rasmus Villemoes" <linux@...musvillemoes.dk>,
"Kees Cook" <keescook@...omium.org>,
"Greg Ungerer" <gerg@...ux-m68k.org>,
"Geert Uytterhoeven" <geert@...ux-m68k.org>,
"Mike Rapoport" <rppt@...nel.org>,
"Vlastimil Babka" <vbabka@...e.cz>,
"Vincenzo Frascino" <vincenzo.frascino@....com>,
"Chinwen Chang" <chinwen.chang@...iatek.com>,
"Michel Lespinasse" <walken@...gle.com>,
"Catalin Marinas" <catalin.marinas@....com>,
"Matthew Wilcox (Oracle)" <willy@...radead.org>,
"Huang Ying" <ying.huang@...el.com>,
"Jann Horn" <jannh@...gle.com>, "Feng Tang" <feng.tang@...el.com>,
"Kevin Brodsky" <Kevin.Brodsky@....com>,
"Michael Ellerman" <mpe@...erman.id.au>,
"Shawn Anastasio" <shawn@...stas.io>,
"Steven Price" <steven.price@....com>,
"Nicholas Piggin" <npiggin@...il.com>,
"Christian Brauner" <christian.brauner@...ntu.com>,
"Jens Axboe" <axboe@...nel.dk>,
"Gabriel Krisman Bertazi" <krisman@...labora.com>,
"Peter Xu" <peterx@...hat.com>,
"Suren Baghdasaryan" <surenb@...gle.com>,
"Shakeel Butt" <shakeelb@...gle.com>,
"Marco Elver" <elver@...gle.com>,
"Daniel Jordan" <daniel.m.jordan@...cle.com>,
"Nicolas Viennot" <Nicolas.Viennot@...sigma.com>,
"Thomas Cedeno" <thomascedeno@...gle.com>,
"Collin Fijalkovich" <cfijalkovich@...gle.com>,
"Michal Hocko" <mhocko@...e.com>,
"Miklos Szeredi" <miklos@...redi.hu>,
"Chengguang Xu" <cgxu519@...ernel.net>,
Christian König <ckoenig.leichtzumerken@...il.com>,
linux-unionfs@...r.kernel.org,
"Linux API" <linux-api@...r.kernel.org>,
"the arch/x86 maintainers" <x86@...nel.org>,
linux-fsdevel@...r.kernel.org, linux-mm@...ck.org
Subject: Re: [PATCH v1 0/7] Remove in-tree usage of MAP_DENYWRITE
On Thu, Aug 12, 2021, at 10:48 AM, Eric W. Biederman wrote:
> "Andy Lutomirski" <luto@...nel.org> writes:
> I had a blind spot, and Florian Weimer made a very reasonable request.
> Apparently userspace for shared libraires uses MAP_PRIVATE.
>
> So we almost don't care if the library is overwritten. We loose some
> efficiency and apparently there are some corner cases like the library
> being extended past the end of the exiting file that are problematic.
>
> Given that MAP_PRIVATE for shared libraries is our strategy for handling
> writes to shared libraries perhaps we just need to use MAP_POPULATE or a
> new related flag (perhaps MAP_PRIVATE_NOW) that just makes certain that
> everything mapped from the executable is guaranteed to be visible from
> the time of the mmap, and any changes from the filesystem side after
> that are guaranteed to cause a copy on write.
>
> Once we get that figured out we could consider getting rid of deny-write
> entirely.
Are all of the CoW bits in good enough shape for this to work without just immediately CoWing the whole file? In principle, write(2) to a file should be able to notice that it needs to CoW some pages, but I doubt that this actually works.
--Andy
Powered by blists - more mailing lists