xfs: don't perform discard if the given range length is less than block size
authorJie Liu <jeff.liu@oracle.com>
Wed, 20 Nov 2013 08:08:53 +0000 (16:08 +0800)
committerBen Myers <bpm@sgi.com>
Tue, 10 Dec 2013 16:00:33 +0000 (10:00 -0600)
commit2f42d612e7d4c4fb1819ea7b2b6e18938714ae7a
tree4c09011b252a333c6fbaa17d00737a2605a53409
parent31978b5cc66b8ba8a7e8eef60b12395d41b7b890
xfs: don't perform discard if the given range length is less than block size

For discard operation, we should return EINVAL if the given range length
is less than a block size, otherwise it will go through the file system
to discard data blocks as the end range might be evaluated to -1, e.g,
# fstrim -v -o 0 -l 100 /xfs7
/xfs7: 9811378176 bytes were trimmed

This issue can be triggered via xfstests/generic/288.

Also, it seems to get the request queue pointer via bdev_get_queue()
instead of the hard code pointer dereference is not a bad thing.

Signed-off-by: Jie Liu <jeff.liu@oracle.com>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Ben Myers <bpm@sgi.com>
(cherry picked from commit f9fd0135610084abef6867d984e9951c3099950d)
fs/xfs/xfs_discard.c