Re: [PATCH] efivarfs: Expose RandomSeed variable but with limited permissions

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sunday, June 25th, 2023 at 22.21, Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx> wrote:
>
> Sami - can you try to revert the revert:
>
> git revert 69cbeb61ff9093a9155cb19a36d633033f71093a
>
> but then additionally in drivers/firmware/efi/efi.c, just change the
>
> static DECLARE_WORK(work, refresh_nv_rng_seed);
> schedule_work(&work);
>
> in refresh_nv_rng_seed_notification() to be something like
>
> static DECLARE_DELAYED_WORK(work, refresh_nv_rng_seed);
> schedule_delayed_work(&work, 120*HZ);
>
> to make the work fire two minutes after boot?
>
> The question then being:
>
> (a) does that fix the boot for you (maybe it's the schedule_work
> itself that confused things, however unlikely that sounds)
>
> (b) if it does boot, do you notice something happening two minutes
> after booting?

I did that and:
(a) It does boot fine with this change.
(b) I don't notice anything happening at two minutes after booting. I can see there is a random-seed file located in EFI partition, but it does not change two minutes after boot (but it is different each boot).

> I'm not entirely sure which laptop it is, with laptop manufacturers
> often re-using model names over several years, but "HP 6730b" seems to
> be basically from July 2008 (going by the service manual I found). So
> we're talking 15 years ago, and yes, EFI was likely much less
> reliable back then.

I got the laptop secondhand 7 years ago, but the 2008 has been my guess as well based on online resources. I have the _latest_ bios on it, 68PDD Ver. F.20 from 2011.




[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux