Searched hist:"983 c7db347db8ce2d8453fd1d89b7a4bb6920d56" (Results 1 – 4 of 4) sorted by relevance
/openbmc/linux/drivers/md/ |
H A D | dm-raid1.c | diff 7c8d3a42fe1c58a7e8fd3f6a013e7d7b474ff931 Fri Jul 20 08:25:07 CDT 2012 Mikulas Patocka <mpatocka@redhat.com> dm raid1: set discard_zeroes_data_unsupported
We can't guarantee that REQ_DISCARD on dm-mirror zeroes the data even if the underlying disks support zero on discard. So this patch sets ti->discard_zeroes_data_unsupported.
For example, if the mirror is in the process of resynchronizing, it may happen that kcopyd reads a piece of data, then discard is sent on the same area and then kcopyd writes the piece of data to another leg. Consequently, the data is not zeroed.
The flag was made available by commit 983c7db347db8ce2d8453fd1d89b7a4bb6920d56 (dm crypt: always disable discard_zeroes_data).
Signed-off-by: Mikulas Patocka <mpatocka@redhat.com> Cc: stable@kernel.org Signed-off-by: Alasdair G Kergon <agk@redhat.com>
|
H A D | dm-table.c | diff 983c7db347db8ce2d8453fd1d89b7a4bb6920d56 Sun Sep 25 17:26:21 CDT 2011 Milan Broz <mbroz@redhat.com> dm crypt: always disable discard_zeroes_data
If optional discard support in dm-crypt is enabled, discards requests bypass the crypt queue and blocks of the underlying device are discarded. For the read path, discarded blocks are handled the same as normal ciphertext blocks, thus decrypted.
So if the underlying device announces discarded regions return zeroes, dm-crypt must disable this flag because after decryption there is just random noise instead of zeroes.
Signed-off-by: Milan Broz <mbroz@redhat.com> Signed-off-by: Alasdair G Kergon <agk@redhat.com>
|
H A D | dm-crypt.c | diff 983c7db347db8ce2d8453fd1d89b7a4bb6920d56 Sun Sep 25 17:26:21 CDT 2011 Milan Broz <mbroz@redhat.com> dm crypt: always disable discard_zeroes_data
If optional discard support in dm-crypt is enabled, discards requests bypass the crypt queue and blocks of the underlying device are discarded. For the read path, discarded blocks are handled the same as normal ciphertext blocks, thus decrypted.
So if the underlying device announces discarded regions return zeroes, dm-crypt must disable this flag because after decryption there is just random noise instead of zeroes.
Signed-off-by: Milan Broz <mbroz@redhat.com> Signed-off-by: Alasdair G Kergon <agk@redhat.com>
|
/openbmc/linux/include/linux/ |
H A D | device-mapper.h | diff 983c7db347db8ce2d8453fd1d89b7a4bb6920d56 Sun Sep 25 17:26:21 CDT 2011 Milan Broz <mbroz@redhat.com> dm crypt: always disable discard_zeroes_data
If optional discard support in dm-crypt is enabled, discards requests bypass the crypt queue and blocks of the underlying device are discarded. For the read path, discarded blocks are handled the same as normal ciphertext blocks, thus decrypted.
So if the underlying device announces discarded regions return zeroes, dm-crypt must disable this flag because after decryption there is just random noise instead of zeroes.
Signed-off-by: Milan Broz <mbroz@redhat.com> Signed-off-by: Alasdair G Kergon <agk@redhat.com>
|