Am Dienstag, 18. Juli 2017, 10:52:12 CEST schrieb Greg Kroah-Hartman: Hi Greg,
> > > I have stated the core concerns I have with random.c in [1]. To remedy > > these core concerns, major changes to random.c are needed. With the past > > experience, I would doubt that I get the changes into random.c. > > > > [1] https://www.spinics.net/lists/linux-crypto/msg26316.html > > Evolution is the correct way to do this, kernel development relies on > that. We don't do the "use this totally different and untested file > instead!" method. I am not sure I understand your reply. The offered patch set does not rip out existing code. It adds a replacement implementation which can be enabled during compile time. Yet it is even disabled per default (and thus the legacy code is compiled). I see such a development approach in numerous different kernel core areas: memory allocators (SLAB, SLOB, SLUB), process schedulers, IRQ schedulers. What is so different for the realm of RNGs? Ciao Stephan
