linux-kernel - Re: [PATCH] powerpc/lib/sstep: Don't use __{get/put}

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:   Tue, 02 Nov 2021 21:11:50 +1100
From:   Michael Ellerman <patch-notifications@...erman.id.au>
To:     Michael Ellerman <mpe@...erman.id.au>,
        Paul Mackerras <paulus@...ba.org>,
        Christophe Leroy <christophe.leroy@...roup.eu>,
        Benjamin Herrenschmidt <benh@...nel.crashing.org>
Cc:     Finn Thain <fthain@...ux-m68k.org>,
        Stan Johnson <userm57@...oo.com>, linux-kernel@...r.kernel.org,
        linuxppc-dev@...ts.ozlabs.org
Subject: Re: [PATCH] powerpc/lib/sstep: Don't use __{get/put}_user() on kernel addresses

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