linux-kernel - Re: [PATCH v5 0/2] powerpc rng cleanups

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <87wnbz9pnk.fsf@mpe.ellerman.id.au>
Date:   Wed, 27 Jul 2022 13:54:07 +1000
From:   Michael Ellerman <mpe@...erman.id.au>
To:     "Jason A. Donenfeld" <Jason@...c4.com>,
        PowerPC <linuxppc-dev@...ts.ozlabs.org>,
        Sachin Sant <sachinp@...ux.ibm.com>,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v5 0/2] powerpc rng cleanups

"Jason A. Donenfeld" <Jason@...c4.com> writes:
> On Mon, Jul 18, 2022 at 3:09 PM Jason A. Donenfeld <Jason@...c4.com> wrote:
>> On Tue, Jul 12, 2022 at 01:24:46AM +0200, Jason A. Donenfeld wrote:
>> > These are two small cleanups for -next. This v5 rebases on the latest
>> > git master, as some whitespace was added that made v4 no longer apply.
>> >
>> > Jason A. Donenfeld (2):
>> >   powerpc/powernv: rename remaining rng powernv_ functions to pnv_
>> >   powerpc/kvm: don't crash on missing rng, and use darn
>> >
>> >  arch/powerpc/include/asm/archrandom.h |  7 +--
>> >  arch/powerpc/kvm/book3s_hv_builtin.c  |  7 +--
>> >  arch/powerpc/platforms/powernv/rng.c  | 66 ++++++++++-----------------
>> >  drivers/char/hw_random/powernv-rng.c  |  2 +-
>> >  4 files changed, 30 insertions(+), 52 deletions(-)
>>
>> I think v5 has reached a completion point. Could you queue these up in
>> some PPC tree for 5.20?
>
> Just paging again. Do you think you could queue these up for 5.20?
> This trivial series is over a month old now.

It can't claim to fix a guest-triggerable hypervisor crash and also be
"trivial" :)

But yes I plan to queue it for v5.20.

cheers