| commit | bc9e9cf0401f18e33b78d4c8a518661b8346baf7 | |
| author | Mikulas Patocka <mpatocka@redhat.com> | |
| Fri, 10 Aug 2018 15:23:56 +0000 (10 11:23 -0400) | ||
| committer | Mike Snitzer <snitzer@redhat.com> | |
| Mon, 13 Aug 2018 19:28:41 +0000 (13 15:28 -0400) | ||
| tree | 963521449bca32037e0ac110e9faefc8f7a898c7 | treesnapshot (tar.gz zip) |
| parent | 5b1fe7bec8a8d0cc547a22e7ddc2bd59acd67de4 | commitdiff |
dm crypt: don't decrease device limits
dm-crypt should only increase device limits, it should not decrease them.
This fixes a bug where the user could creates a crypt device with 1024
sector size on the top of scsi device that had 4096 logical block size.
The limit 4096 would be lost and the user could incorrectly send
1024-I/Os to the crypt device.
Cc: stable@vger.kernel.org
Signed-off-by: Mikulas Patocka <mpatocka@redhat.com>
Signed-off-by: Mike Snitzer <snitzer@redhat.com>
dm-crypt should only increase device limits, it should not decrease them.
This fixes a bug where the user could creates a crypt device with 1024
sector size on the top of scsi device that had 4096 logical block size.
The limit 4096 would be lost and the user could incorrectly send
1024-I/Os to the crypt device.
Cc: stable@vger.kernel.org
Signed-off-by: Mikulas Patocka <mpatocka@redhat.com>
Signed-off-by: Mike Snitzer <snitzer@redhat.com>
| drivers/md/dm-crypt.c | diffblobblamehistory |