On Tue, Nov 30, 2021 at 04:45:44PM +0100, Greg Kroah-Hartman wrote: > > And the main question here is, how can we get there, in any case, if > > the maintainer of the random device doesn't even participate in > > discussions, does not pick obvious bug fixes and is simply not engaging > > at all? > > What obvious bug fixes have been dropped? > The RNDRESEEDCRNG ioctl was totally broken, and I sent out a patch to fix it which was ignored for months: https://lore.kernel.org/linux-crypto/20200916041908.66649-1-ebiggers@xxxxxxxxxx/ Reminders didn't help: First ping: https://lore.kernel.org/linux-crypto/20201007035021.GB912@sol.localdomain/ Second ping: https://lore.kernel.org/linux-crypto/20201026163343.GA858@sol.localdomain/ Third ping: https://lore.kernel.org/linux-crypto/X7gQXgoXHHEr6HXC@sol.localdomain/ Fourth ping: https://lore.kernel.org/linux-crypto/X%2FNkrKpaIBTjQzbv@sol.localdomain/ Resent to Andrew Morton: https://lore.kernel.org/linux-crypto/20210112192818.69921-1-ebiggers@xxxxxxxxxx/ Pinged Andrew: https://lore.kernel.org/linux-crypto/YBiEJ9Md60HjAWJg@sol.localdomain/ Finally *you* took the patch: https://lore.kernel.org/linux-crypto/YBwZ1a0VIdpTDNuD@xxxxxxxxx/ Here's another random.c bug fix which was ignored, this one for 6 months before Herbert Xu finally took it through the crypto tree: https://lore.kernel.org/linux-crypto/20210322051347.266831-1-ebiggers@xxxxxxxxxx/ Here's a dead code cleanup which was ignored for 6 months before being taken by Herbert Xu through the crypto tree: https://lore.kernel.org/linux-crypto/20200916043652.96640-1-ebiggers@xxxxxxxxxx/ Here's a patch to random.c which was taken by the arm64 maintainers due to being ignored by the random.c maintainer: https://lore.kernel.org/lkml/20201105152944.16953-1-ardb@xxxxxxxxxx/ So unfortunately, as far as I can tell, Ted is not maintaining random.c anymore. - Eric
