Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
From:   Michael Ellerman <patch-notifications@ellerman.id.au>
To:     Michael Ellerman <mpe@ellerman.id.au>,
        Paul Mackerras <paulus@samba.org>,
        Christophe Leroy <christophe.leroy@csgroup.eu>,
        Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc:     Finn Thain <fthain@linux-m68k.org>,
        Stan Johnson <userm57@yahoo.com>, linux-kernel@vger.kernel.org,
        linuxppc-dev@lists.ozlabs.org
In-Reply-To: <22831c9d17f948680a12c5292e7627288b15f713.1631817805.git.christophe.leroy@csgroup.eu>
References: <22831c9d17f948680a12c5292e7627288b15f713.1631817805.git.christophe.leroy@csgroup.eu>
Subject: Re: [PATCH] powerpc/lib/sstep: Don't use __{get/put}_user() on kernel addresses
Message-Id: <163584791077.1845480.9899621375066111807.b4-ty@ellerman.id.au>
Date:   Tue, 02 Nov 2021 21:11:50 +1100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Thu, 16 Sep 2021 20:43:36 +0200, Christophe Leroy wrote:
> In the old days, when we didn't have kernel userspace access
> protection and had set_fs(), it was wise to use __get_user()
> and friends to read kernel memory.
> 
> Nowadays, get_user() and put_user() are granting userspace access and
> are exclusively for userspace access.
> 
> [...]

Applied to powerpc/next.

[1/1] powerpc/lib/sstep: Don't use __{get/put}_user() on kernel addresses
      https://git.kernel.org/powerpc/c/e28d0b675056d072f1f11fa644d0efbb016bb7ce

cheers