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: Tue, 3 Oct 2017 00:45:27 +0200 From: Richard Weinberger <richard.weinberger@...il.com> To: Nicolas Pitre <nicolas.pitre@...aro.org> Cc: Christoph Hellwig <hch@...radead.org>, Alexander Viro <viro@...iv.linux.org.uk>, "linux-mm@...ck.org" <linux-mm@...ck.org>, linux-fsdevel <linux-fsdevel@...r.kernel.org>, "linux-embedded@...r.kernel.org" <linux-embedded@...r.kernel.org>, LKML <linux-kernel@...r.kernel.org>, Chris Brandt <Chris.Brandt@...esas.com> Subject: Re: [PATCH v4 4/5] cramfs: add mmap support On Mon, Oct 2, 2017 at 12:29 AM, Nicolas Pitre <nicolas.pitre@...aro.org> wrote: > On Sun, 1 Oct 2017, Christoph Hellwig wrote: > >> up_read(&mm->mmap_sem) in the fault path is a still a complete >> no-go, >> >> NAK > > Care to elaborate? > > What about mm/filemap.c:__lock_page_or_retry() then? As soon you up_read() in the page fault path other tasks will race with you before you're able to grab the write lock. HTH -- Thanks, //richard
Powered by blists - more mailing lists