Re: [PATCH v4 13/15] cryptodisk: Properly handle non-512 byte sized sectors.

2020-11-22 Thread Patrick Steinhardt
On Fri, Nov 20, 2020 at 02:42:35AM -0600, Glenn Washburn wrote: > On Sun, 15 Nov 2020 11:07:27 +0100 > Patrick Steinhardt wrote: > > > On Fri, Nov 06, 2020 at 10:44:33PM -0600, Glenn Washburn wrote: > > > By default, dm-crypt internally uses an IV that corresponds to > > > 512-byte sectors, even

Re: [PATCH v4 13/15] cryptodisk: Properly handle non-512 byte sized sectors.

2020-11-20 Thread Glenn Washburn
On Sun, 15 Nov 2020 11:07:27 +0100 Patrick Steinhardt wrote: > On Fri, Nov 06, 2020 at 10:44:33PM -0600, Glenn Washburn wrote: > > By default, dm-crypt internally uses an IV that corresponds to > > 512-byte sectors, even when a larger sector size is specified. What > > this means is that when usi

Re: [PATCH v4 13/15] cryptodisk: Properly handle non-512 byte sized sectors.

2020-11-15 Thread Patrick Steinhardt
On Fri, Nov 06, 2020 at 10:44:33PM -0600, Glenn Washburn wrote: > By default, dm-crypt internally uses an IV that corresponds to 512-byte > sectors, even when a larger sector size is specified. What this means is > that when using a larger sector size, the IV is incremented every sector. > However,

[PATCH v4 13/15] cryptodisk: Properly handle non-512 byte sized sectors.

2020-11-06 Thread Glenn Washburn
By default, dm-crypt internally uses an IV that corresponds to 512-byte sectors, even when a larger sector size is specified. What this means is that when using a larger sector size, the IV is incremented every sector. However, the amount the IV is incremented is the number of 512 byte blocks in a