On 2017-11-20 13:25, Andreas Reichel wrote: > On Mon, Nov 20, 2017 at 12:28:18PM +0100, Jan Kiszka wrote: >> On 2017-11-17 17:32, Andreas J. Reichel wrote: >>> From: Andreas Reichel <[email protected]> >>> >>> Global variables are removed to avoid a regression regarding the >>> robustness of the update mechanism. >>> >>> Furthermore, an improvement to the 'setglobalstate' function of the API >>> is added to reduce unnecessary environment modifications and to add >>> further support to recover from usually non-occuring update states. >> >> Err, you need to help me: Why do we still have a setglobalstate API when >> global vars are removed? Shouldn't that one go as well? >> > That is okay :) The name 'globalstate' refers to ustate and was chosen > as such, because in case of failure, ALL environments are searched for > ustate == FAILED and revision == 0. That's why. > > The setter only modifies environments that are marked as FAILED if > setting the state to OK. If setting the state to another value, only the > current environment is accessed.
OK, that resolves my concerns. Merged, also to master. Thanks, Jan -- You received this message because you are subscribed to the Google Groups "EFI Boot Guard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/efibootguard-dev/9bdb1b3b-c309-48dc-8efc-a020c16bec16%40siemens.com. For more options, visit https://groups.google.com/d/optout.
