linux-kernel - Re: [PATCH 4.19 49/81] powerpc: Remove STRICT_KERNEL

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 for Android: free password hash cracker in your pocket

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

Date:   Wed, 27 May 2020 16:32:00 +0200
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Pavel Machek <pavel@...x.de>
Cc:     linux-kernel@...r.kernel.org, stable@...r.kernel.org,
        Russell Currey <ruscur@...sell.cc>,
        Michael Ellerman <mpe@...erman.id.au>,
        Sasha Levin <sashal@...nel.org>
Subject: Re: [PATCH 4.19 49/81] powerpc: Remove STRICT_KERNEL_RWX
 incompatibility with RELOCATABLE

On Wed, May 27, 2020 at 03:28:31PM +0200, Pavel Machek wrote:
> On Tue 2020-05-26 20:53:24, Greg Kroah-Hartman wrote:
> > From: Russell Currey <ruscur@...sell.cc>
> > 
> > [ Upstream commit c55d7b5e64265fdca45c85b639013e770bde2d0e ]
> > 
> > I have tested this with the Radix MMU and everything seems to work, and
> > the previous patch for Hash seems to fix everything too.
> > STRICT_KERNEL_RWX should still be disabled by default for now.
> > 
> > Please test STRICT_KERNEL_RWX + RELOCATABLE!
> 
> I don't believe this is suitable for -stable. Yes, it is needed for
> the next patch, but doing the merge is right solution this time.

Why?  It's always best to keep things as they are in Linus's tree if at
all possible.

thanks,

greg k-h