linux-kernel - Re: [PATCH v3] random: handle archrandom with multiple longs

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: <CAHmME9rk27DA0DmTY7hhedFT0ftkMKhZn30NCvjkkzkKD0hNfQ@mail.gmail.com>
Date:   Mon, 1 Aug 2022 16:50:00 +0200
From:   "Jason A. Donenfeld" <Jason@...c4.com>
To:     freude@...ux.ibm.com
Cc:     linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
        linuxppc-dev@...ts.ozlabs.org, linux-s390@...r.kernel.org,
        x86@...nel.org, Will Deacon <will@...nel.org>,
        Alexander Gordeev <agordeev@...ux.ibm.com>,
        Thomas Gleixner <tglx@...utronix.de>,
        "H . Peter Anvin" <hpa@...or.com>,
        Catalin Marinas <catalin.marinas@....com>,
        Borislav Petkov <bp@...e.de>,
        Heiko Carstens <hca@...ux.ibm.com>,
        Johannes Berg <johannes@...solutions.net>,
        Mark Rutland <mark.rutland@....com>,
        Michael Ellerman <mpe@...erman.id.au>,
        Stephen Rothwell <sfr@...b.auug.org.au>
Subject: Re: [PATCH v3] random: handle archrandom with multiple longs

Hi Harald,

On Mon, Aug 1, 2022 at 4:47 PM Harald Freudenberger
<freude@...ux.ibm.com> wrote:
>
> Nice interface :-)
> Here is my
> Acked-by: Harald Freudenberger <freude@...ux.ibm.com>

You're too late; I already sent in my pull request. But that's okay; I
received Heiko's ack on this for s390.

> but please keep in mind that your patch does not apply cleanly as there
> is my other patch
> 918e75f77af7 ("s390/archrandom: prevent CPACF trng invocations in
> interrupt context")
> in between.

Yea, this was a late addition to 5.19, and my random tree was based on
an earlier rc of 5.19. That kind of thing happens and is fine; Stephen
caught it when doing the next merge and carries the merge conflict
resolution there. I mentioned it to Linus in my pull, so he'll be able
to work it out.

Jason