lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Fri, 13 Aug 2021 14:54:43 -1000 From: Linus Torvalds <torvalds@...ux-foundation.org> To: Andy Lutomirski <luto@...nel.org> Cc: "Eric W. Biederman" <ebiederm@...ssion.com>, David Laight <David.Laight@...lab.com>, David Hildenbrand <david@...hat.com>, Linux Kernel Mailing List <linux-kernel@...r.kernel.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-unionfs@...r.kernel.org>, Linux API <linux-api@...r.kernel.org>, "the arch/x86 maintainers" <x86@...nel.org>, "<linux-fsdevel@...r.kernel.org>" <linux-fsdevel@...r.kernel.org>, Linux-MM <linux-mm@...ck.org>, Florian Weimer <fweimer@...hat.com>, Michael Kerrisk <mtk.manpages@...il.com> Subject: Re: [PATCH v1 0/7] Remove in-tree usage of MAP_DENYWRITE On Fri, Aug 13, 2021 at 2:49 PM Andy Lutomirski <luto@...nel.org> wrote: > > I’ll bite. How about we attack this in the opposite direction: remove the deny write mechanism entirely. I think that would be ok, except I can see somebody relying on it. It's broken, it's stupid, but we've done that ETXTBUSY for a _loong_ time. But you are right that we have removed parts of it over time (no more MAP_DENYWRITE, no more uselib()) so that what we have today is a fairly weak form of what we used to do. And nobody really complained when we weakened it, so maybe removing it entirely might be acceptable. Linus
Powered by blists - more mailing lists