[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAG48ez0hoNb+DsMtzanGMXWdU63GwSvpzFCx5CkQa3Xxxo+Abg@mail.gmail.com>
Date: Thu, 15 Oct 2020 00:29:42 +0200
From: Jann Horn <jannh@...gle.com>
To: Khalid Aziz <khalid.aziz@...cle.com>
Cc: Catalin Marinas <catalin.marinas@....com>,
"David S. Miller" <davem@...emloft.net>,
sparclinux@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>,
Linux-MM <linux-mm@...ck.org>,
kernel list <linux-kernel@...r.kernel.org>,
Christoph Hellwig <hch@...radead.org>,
Anthony Yznaga <anthony.yznaga@...cle.com>,
Will Deacon <will@...nel.org>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>,
Michael Ellerman <mpe@...erman.id.au>,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Paul Mackerras <paulus@...ba.org>,
linuxppc-dev@...ts.ozlabs.org
Subject: Re: [PATCH 1/2] mm/mprotect: Call arch_validate_prot under mmap_lock
and with length
On Wed, Oct 14, 2020 at 11:24 PM Khalid Aziz <khalid.aziz@...cle.com> wrote:
[...]
> current code? What FreeBSD does seems like a reasonable thing to do. Any
> way first thing to do is to update sparc to use arch_validate_flags()
> and update sparc_validate_prot() to not peek into vma without lock. I
> can do that unless Jann wants to rework this 2 patch series with these
> changes.
Ah, if you're willing to take care of that, that'd be nice, please do. :)
Powered by blists - more mailing lists