linux-kernel - Re: [PATCH -v2 00/10] Rewrite Motorola MMU page-table layout

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Mon, 9 Mar 2020 12:46:45 +0100
From:   Peter Zijlstra <peterz@...radead.org>
To:     Geert Uytterhoeven <geert@...ux-m68k.org>
Cc:     Will Deacon <will@...nel.org>,
        linux-m68k <linux-m68k@...ts.linux-m68k.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Michael Schmitz <schmitzmic@...il.com>,
        Greg Ungerer <gerg@...ux-m68k.org>
Subject: Re: [PATCH -v2 00/10] Rewrite Motorola MMU page-table layout

On Mon, Mar 09, 2020 at 11:15:31AM +0100, Geert Uytterhoeven wrote:
> Hi Peter, Will
> 
> On Mon, Feb 10, 2020 at 12:16 PM Geert Uytterhoeven
> <geert@...ux-m68k.org> wrote:
> > On Fri, Jan 31, 2020 at 1:56 PM Peter Zijlstra <peterz@...radead.org> wrote:
> > > In order to faciliate Will's READ_ONCE() patches:
> > >
> > >   https://lkml.kernel.org/r/20200123153341.19947-1-will@kernel.org
> > >
> > > we need to fix m68k/motorola to not have a giant pmd_t. These patches do so and
> > > are tested using ARAnyM/68040.
> > >
> > > Michael tested the previous version on his Atari Falcon/68030.
> > >
> > > Build tested for sun3/coldfire.
> > >
> > > Please consider!
> >
> > Thanks, applied and queued for v5.7, using an immutable branch named
> > pgtable-layout-rewrite.
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/geert/linux-m68k.git/log/?h=pgtable-layout-rewrite
> 
> Any plans to use this? Looks like it's still part of linux-next through the m68k
> tree only.

Argh, yes. So we ran into sparc32 also need fixups, and both me and Will
seem to have stalled on fixing that. I'll try and get back to that.