diff options
| author | Milan Broz <gmazyland@gmail.com> | 2017-03-16 15:39:44 +0100 |
|---|---|---|
| committer | Mike Snitzer <snitzer@redhat.com> | 2017-03-24 15:54:21 -0400 |
| commit | 8f0009a225171cc1b76a6b443de5137b26e1374b (patch) | |
| tree | 4bb6cf315a9756411856c978eced0cc9a4fa1d2d /drivers/scsi/nsp32_debug.c | |
| parent | 33d2f09fcb357fd1861c4959d1d3505492bf91f8 (diff) | |
dm crypt: optionally support larger encryption sector size
Add optional "sector_size" parameter that specifies encryption sector
size (atomic unit of block device encryption).
Parameter can be in range 512 - 4096 bytes and must be power of two.
For compatibility reasons, the maximal IO must fit into the page limit,
so the limit is set to the minimal page size possible (4096 bytes).
NOTE: this device cannot yet be handled by cryptsetup if this parameter
is set.
IV for the sector is calculated from the 512 bytes sector offset unless
the iv_large_sectors option is used.
Test script using dmsetup:
DEV="/dev/sdb"
DEV_SIZE=$(blockdev --getsz $DEV)
KEY="9c1185a5c5e9fc54612808977ee8f548b2258d31ddadef707ba62c166051b9e3cd0294c27515f2bccee924e8823ca6e124b8fc3167ed478bca702babe4e130ac"
BLOCK_SIZE=4096
# dmsetup create test_crypt --table "0 $DEV_SIZE crypt aes-xts-plain64 $KEY 0 $DEV 0 1 sector_size:$BLOCK_SIZE"
# dmsetup table --showkeys test_crypt
Signed-off-by: Milan Broz <gmazyland@gmail.com>
Signed-off-by: Mike Snitzer <snitzer@redhat.com>
Diffstat (limited to 'drivers/scsi/nsp32_debug.c')
0 files changed, 0 insertions, 0 deletions