On Thu, Jul 16, 2015 at 3:28 PM, K. Macy <km...@freebsd.org> wrote: > I discovered this when I MFC'd and my kernel wouldn't link because of > unresolved symbols. I thought I had put the issue aside when I added > RANDOM_DUMMY to my kernel config. > > However, I just hit this: > > while (!random_alg_context.ra_seeded()) { > if (nonblock) { > error = EWOULDBLOCK; > break; > } > tsleep(&random_alg_context, 0, "randseed", hz/10); > /* keep tapping away at the pre-read until we seed/unblock. */ > random_alg_context.ra_pre_read(); > printf("random: %s unblock wait\n", __func__); > } > > My system wouldn't boot because this was endlessly spamming the > console. I don't know what the right default here is. But I can say > that this is not it.
I've also realized that a process blocked here is uninterruptible. Hence any process reading an insufficiently seeded /dev/random is unkillable. For example my boot can't proceed past dd doing a read and I can't ^C it. Did you test RANDOM_DUMMY? -K _______________________________________________ svn-src-head@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-src-head To unsubscribe, send any mail to "svn-src-head-unsubscr...@freebsd.org"