RE: efi: be more paranoid about available space when creating variables

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

 



>    We should be able to calculate that by simply
>     summing the size of each available variable and subtracting that from
>     the total storage space. With luck this will fix the problem described in
>     https://bugzilla.kernel.org/show_bug.cgi?id=55471 without permitting
>     damage to occur to the machines 68d9298 was attempting to fix.

I like the idea of this patch. It could be a long term solution.

If we can calculate the size of available variables by ourselves,
 we don't need to call QueryVariableInfo().
It makes efivars robust against buggy firmwares.
Also, this patch actually fixes a serious bug, failing boot up.

In theory, QueryVariableInfo() should return accurate values to kernel.
But, it doesn't in practice.

I think creating blacklist will be like playing whac-a-mole, because
we can't anticipate how many buggy firmwares will appear in the future.

Seiji
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Kernel]     [Kernel Development Newbies]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Hiking]     [Linux Kernel]     [Linux SCSI]