Den ons 14 juni 2023 kl 06:27 skrev Schech, C. W. ("Connor") <
sch...@gmail.com>:
> There's no check of the checksums for all the object files that the
> /rc task consumes
>
> This can be trivially fixed by generating them in, say
> In /sys/conf/newvars.sh, add the line:
> +sha512 -h /var/db/obj.${id}.sha512 *.o lorder
> above the segment starting with:
>
Wait, if I build a kernel it would still write the sha to my buildhosts
/var?
That sounds like a very bad idea. At the very least not completely thought
through.
> cat >vers.c <<eof
>
> Also consider moving the relinking to "only at shutdown", so no other
> jobs are running concurrently in case that causes a random kernel
> fault due to extreme load on faulty hardware, and to make the boot
>
Faulty hardware fails, that is not the problem of the relinking phase to
handle.
Have you timed how long this takes on slower arches, because now you get a
shutdown-time that becomes huge and it can not run async, for obvious
reasons.
> time as fast as possible, since the relinked kernel isn't used until
> the boot after AFAIK.
>
If you issue "reboot" it doesn't matter much if you spend this time going
down or same amount of time coming up, does it?
Also, as it currently stands, the machine can be used while relinking is
done in the background. If doing it during shutdown, not so much.
> Sorry I don't have an exact
> two or three line commit for the fence
> My solution takes care of the fact that the install media doesn't
Well, it is kind of hard to reason about these two-three lines if we don't
get to see "your solution".
--
May the most significant bit of your life be positive.
