| commit | 850f49de9b57511dcaf2cd7e45059f8f38fadf3b | |
| author | Daniel P. Berrange <berrange@redhat.com> | |
| Wed, 27 Sep 2017 12:53:36 +0000 (27 13:53 +0100) | ||
| committer | Max Reitz <mreitz@redhat.com> | |
| Fri, 6 Oct 2017 14:30:47 +0000 (6 16:30 +0200) | ||
| tree | 497e5c335910bdaa9a01d3fcc74eecdd344d986f | treesnapshot (tar.gz zip) |
| parent | 161253e2d0a83a1b33bca019c6e926013e1a03db | commitdiff |
crypto: expose encryption sector size in APIs
While current encryption schemes all have a fixed sector size of
512 bytes, this is not guaranteed to be the case in future. Expose
the sector size in the APIs so the block layer can remove assumptions
about fixed 512 byte sectors.
Reviewed-by: Max Reitz <mreitz@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
Message-id: 20170927125340.12360-3-berrange@redhat.com
Signed-off-by: Max Reitz <mreitz@redhat.com>
While current encryption schemes all have a fixed sector size of
512 bytes, this is not guaranteed to be the case in future. Expose
the sector size in the APIs so the block layer can remove assumptions
about fixed 512 byte sectors.
Reviewed-by: Max Reitz <mreitz@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
Message-id: 20170927125340.12360-3-berrange@redhat.com
Signed-off-by: Max Reitz <mreitz@redhat.com>