On Tue, Jun 07, 2022 at 11:51:23AM +0200, Jason A. Donenfeld wrote: > On Tue, Jun 7, 2022 at 11:49 AM Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx> wrote: > > > > On Tue, Jun 07, 2022 at 10:56:21AM +0200, Jason A. Donenfeld wrote: > > > You can actually drop this in favor of > > > https://lore.kernel.org/stable/20220607084005.666059-1-Jason@xxxxxxxxx/ > > > rather than playing whack-a-mole by architectures that may have been > > > broken by it. > > > > So I need to drop this as well? Or is it ok to keep for now now that I > > have queued up the other commit? > > The other commit ("Revert "random: use static branch for > crng_ready()"") fixes this problem on all architectures. This commit > fixes the problem on arm64. There's probably no harm in keeping this > commit, if you want it, but it's also no longer necessary, because > "Revert "random: use static branch for crng_ready()"" addresses the > issue more comprehensively. I'll just leave this as-is for now, that's simpler. thanks, greg k-h
