Add [pre|post]suspend functions to the exception store API.
These will become important for future exception stores. Current
exception store implementations will not alter metadata after
a 'commit_exception' completes. However, future stores may do
journaling or other actions. They might return from 'commit_exception'
when the request hits the journal, but continue flushing after.
This could be bad, because we expect them to not do anything once
a 'suspend' is issued. Adding these functions to the API allows
them to finish what they are doing and conform to device-mapper
requirements. (The above was just one example... Cluster-aware
exception stores will also require the notification of when they
need to suspend their activity.)
Signed-off-by: Jonathan Brassow <jbrassow@redhat.com>
Add [pre|post]suspend functions to the exception store API.
These will become important for future exception stores. Current
exception store implementations will not alter metadata after
a 'commit_exception' completes. However, future stores may do
journaling or other actions. They might return from 'commit_exception'
when the request hits the journal, but continue flushing after.
This could be bad, because we expect them to not do anything once
a 'suspend' is issued. Adding these functions to the API allows
them to finish what they are doing and conform to device-mapper
requirements. (The above was just one example... Cluster-aware
exception stores will also require the notification of when they
need to suspend their activity.)
Signed-off-by: Jonathan Brassow <jbrassow@redhat.com>