Re: bootchooser: constant decrement of remaining_attempts

[Sascha Hauer <s.hauer@pengutronix.de>]

Hi Patrick,

+Cc Jan and Enrico

On Tue, Oct 09, 2018 at 06:37:25PM +0200, Patrick Huesmann wrote:
> Hi,
> 
> I'm building a RAUC- & bootchooser-based firmware update solution.
> The scenario is symmetric rootfs slots, manual update, userspace
> (RAUC) marks as good.
> It seems to work well, however I noticed that it's always decrementing
> and resetting the remaining_attempts of the booted system, not only
> when there's an update, but also during regular boot-ups.
> 
> I thought that the RAUC/bootchooser combo was mainly about providing a
> safeguard against accidentally "bricking" the system with corrupt or
> incomplete firmware updates.
> However, the logic of decrementing and later resetting the
> remaining_attempts is apparently not limited to the period between
> performing the update and the validation (mark as good) of that
> update, but also running all the other times the system is booted.
> 
> This can have some undesirable side effects:
> 
> 1) When the boot process is interrupted for any reason (power issues,
> brown-out resets, users unplugging the gadget while it boots, etc.)
> more than three times in a row (assuming a remaining_attempts reset
> value of 3), then bootchooser will happily switch to the fall-back
> target, even though there's nothing wrong with the actual target at
> all.

I think what you want here is the global.bootchooser.reset_attempts=power-on
option. With this option bootchooser will reset the remaining attempts
to the default value with each power on reset, meaning that the primary
target will only become invalid when the watchdog bites you three times
in a row, but not when the device is turned off in between.

> I guess this can be worked around by syncing the fall-back target to
> the last updated one, after the last update has been verified as good.
> However this brings additional cost & complexity, and feels more like
> a hack than a proper solution.
> 
> 2) In every complete boot cycle, there are two writes to the
> barebox-state partition (bootchooser decrementing the
> remaining_attempts, then userspace resetting the remaining_attempts
> when it marks the target as good). For systems that boot up & power
> down a lot, this will generate lots of unnecessary flash writes over
> time. Probably it won't be enough to actually wear out the flash, but
> still it doesn't "feel" quite right. (I jumped through hoops to have a
> proper read-only root and would like to limit the overall number of
> flash writes when possible).
> 
> I'm thinking of an option that limits the remaining_attempts logic to
> the phase when barebox attempts to boot a newly flashed update, until
> that update is marked as good later in userspace. There could be an
> extra (optional) variable in the barebox-state, that allows the
> userspace to deliberately enable/disable the remaining_attempts logic
> in barebox.

I don't think such an option is available at the moment. Maybe we could
declare remaining_attempts=INT_MAX as infinite attempts. Whenever that
value is found the remaining_attempts counter wouldn't be decreased.

After an update userspace could then set the remaining_attempts counter
of the new system to three and the new system would set it to INT_MAX
when successfully booted.

What do you think?

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox