Always check for usage underflows in the storage API

changed milestone to %Tor: 0.3.1.x-final in legacy/trac

added actualpoints::0.2 in Legacy / Trac component::core tor/tor in Legacy / Trac integer-safety in Legacy / Trac milestone::Tor: 0.3.1.x-final in Legacy / Trac points::0.2 in Legacy / Trac priority::medium in Legacy / Trac race-condition in Legacy / Trac resolution::fixed in Legacy / Trac severity::normal in Legacy / Trac status::closed in Legacy / Trac type::defect in Legacy / Trac version::tor 0.3.1.1-alpha in Legacy / Trac labels

Please see my branch bug22424, which fixes two different ways the usage could underflow, and does something sensible when it does underflow. (For example, the usage can underflow when we cache the usage, then an external process makes a file bigger, then we delete that file.)

Trac:
Actualpoints: N/A to 0.2
Status: new to needs_review
Keywords: N/A deleted, race-condition, integer-safety added

wow, that's an elegantly structured patch series. Merged!

Trac:
Resolution: N/A to fixed
Status: needs_review to closed

closed

changed time estimate to 1h 36m

added 1h 36m of time spent

moved from legacy/trac#22424 (moved)

added Bug label and removed 1 deleted label

removed 1 deleted label