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, 18 Jan 2019 16:49:30 +1200 From: Linus Torvalds <torvalds@...ux-foundation.org> To: Vlastimil Babka <vbabka@...e.cz> Cc: Josh Snyder <joshs@...flix.com>, Dominique Martinet <asmadeus@...ewreck.org>, Andy Lutomirski <luto@...capital.net>, Dave Chinner <david@...morbit.com>, Jiri Kosina <jikos@...nel.org>, Matthew Wilcox <willy@...radead.org>, Jann Horn <jannh@...gle.com>, Andrew Morton <akpm@...ux-foundation.org>, Greg KH <gregkh@...uxfoundation.org>, Peter Zijlstra <peterz@...radead.org>, Michal Hocko <mhocko@...e.com>, Linux-MM <linux-mm@...ck.org>, kernel list <linux-kernel@...r.kernel.org>, Linux API <linux-api@...r.kernel.org> Subject: Re: [PATCH] mm/mincore: allow for making sys_mincore() privileged On Fri, Jan 18, 2019 at 9:45 AM Vlastimil Babka <vbabka@...e.cz> wrote: > > Or maybe we could resort to the 5.0-rc1 page table check (that is now being > reverted) but only in cases when we are not allowed the page cache residency > check? Or would that be needlessly complicated? I think it would be good fallback semantics, but I'm not sure it's worth it. Have you tried writing a patch for it? I don't think you'd want to do the check *when* you find a hole, so you'd have to do it upfront and then pass the cached data down with the private pointer (or have a separate "struct mm_walk" structure, perhaps? So I suspect we're better off with the patch we have. But if somebody *wants* to try to do that fancier patch, and it doesn't look horrendous, I think it might be the "quality" solution. Linus
Powered by blists - more mailing lists