diff options
| author | Max Reitz <mreitz@redhat.com> | 2019-09-18 11:51:42 +0200 |
|---|---|---|
| committer | Max Reitz <mreitz@redhat.com> | 2019-10-28 12:05:30 +0100 |
| commit | e61a28a9b6b43da6a7a48f6d325fceadf9769388 (patch) | |
| tree | 4f4f9fa25e0c5486429dd082f60d119136b06c2f /capstone | |
| parent | 82325ae5f2f86ad696db3d66563a078daabc9769 (diff) | |
block: Let format drivers pass @exact
When truncating a format node, the @exact parameter is generally handled
simply by virtue of the format storing the new size in the image
metadata. Such formats do not need to pass on the parameter to their
file nodes.
There are exceptions, though:
- raw and crypto cannot store the image size, and thus must pass on
@exact.
- When using qcow2 with an external data file, it just makes sense to
keep its size in sync with the qcow2 virtual disk (because the
external data file is the virtual disk). Therefore, we should pass
@exact when truncating it.
Signed-off-by: Max Reitz <mreitz@redhat.com>
Message-id: 20190918095144.955-7-mreitz@redhat.com
Reviewed-by: Maxim Levitsky <mlevitsk@redhat.com>
Signed-off-by: Max Reitz <mreitz@redhat.com>
Diffstat (limited to 'capstone')
0 files changed, 0 insertions, 0 deletions