Re: [PATCH v5 0/5] random,x86,kvm: Rework arch RNG seeds and get some from kvm
From: Andy Lutomirski
Date: Wed Aug 13 2014 - 14:33:58 EST
On Wed, Aug 13, 2014 at 11:22 AM, Theodore Ts'o <tytso@xxxxxxx> wrote:
> On Wed, Aug 13, 2014 at 10:45:25AM -0700, H. Peter Anvin wrote:
>> On 08/13/2014 09:13 AM, Andy Lutomirski wrote:
>> > Sounds good to me.
>> > FWIW, I'd like to see a second use added in random.c: I think that we
>> > should do this, or even all of init_std_data, on resume from suspend
>> > and especially on resume from hibernate / kexec.
>> Yes, we should. We also need to make it possible to do this after
>> cloning a VM.
> Agreed. Can you send a patch?
> I can carry the commits to add arch_random_init() the generic version,
> and the patch to call it after suspend/resume. I'll do this at the
> very head of the random tree, and make sure it gets pushed to Linus
> early during the next merge window.
> Does that sound like a plan? Or does someone want to suggest
> something different? I'm flexible...
OK. Here's a proposal. I'll split the series into two parts. The
first part will be the arch_random_init generic change and code to
call it after suspend/resume (once I figure out the right callback).
I'll send that to you.
The second part will be the KVM and x86 code, which will look just
like this version (v5) except for the rename. If needed, hpa and I
can hash the details we need at KS.
As for doing arch_random_init after clone/migration, I think we'll
need another KVM extension for that, since, AFAIK, we don't actually
get notified that we were cloned or migrated. That will be
nontrivial. Maybe we can figure that out at KS, too.
> - Ted
AMA Capital Management, LLC
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/