diff options
| author | Mike Snitzer <snitzer@redhat.com> | 2013-09-19 18:49:11 -0400 |
|---|---|---|
| committer | Mike Snitzer <snitzer@redhat.com> | 2013-09-23 10:42:06 -0400 |
| commit | b60ab990ccdf34b0159bf5ff52f4acee7c940d78 (patch) | |
| tree | 9a05149474e38190b0ed676ec98853ce5099da44 /drivers/md/dm.c | |
| parent | f84cb8a46a771f36a04a02c61ea635c968ed5f6a (diff) | |
| download | op-kernel-dev-b60ab990ccdf34b0159bf5ff52f4acee7c940d78.zip op-kernel-dev-b60ab990ccdf34b0159bf5ff52f4acee7c940d78.tar.gz | |
dm thin: do not expose non-zero discard limits if discards disabled
Fix issue where the block layer would stack the discard limits of the
pool's data device even if the "ignore_discard" pool feature was
specified.
The pool and thin device(s) still had discards disabled because the
QUEUE_FLAG_DISCARD request_queue flag wasn't set. But to avoid user
confusion when "ignore_discard" is used: both the pool device and the
thin device(s) have zeroes for all discard limits.
Also, always set discard_zeroes_data_unsupported in targets because they
should never advertise the 'discard_zeroes_data' capability (even if the
pool's data device supports it).
Signed-off-by: Mike Snitzer <snitzer@redhat.com>
Acked-by: Joe Thornber <ejt@redhat.com>
Diffstat (limited to 'drivers/md/dm.c')
0 files changed, 0 insertions, 0 deletions
