Data corruption on-disk could cause the indexed ruleset to behave unpredictably, or even lead to crashes.
There have been previous discussions about storing the checksum directly in the flatbuffer, but it would be simplest to store it in subresource_filter::IndexedRulesetVersion, alongside the content / format version.
This way, our ruleset verification step can also ensure the contents did not change on disk by comparing the checksum to the one in prefs.
Comment 1 by ericrobinson@chromium.org
, May 30 2018