Always check for usage underflows in the storage API

changed milestone to %Tor: 0.3.1.x-final

added actualpoints::0.2 component::core tor/tor integer-safety milestone::Tor: 0.3.1.x-final points::0.2 priority::medium race-condition resolution::fixed severity::normal status::closed type::defect version::tor 0.3.1.1-alpha 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 to tpo/core/tor#22424 (closed)