diff options
author | Jiong Wu <lohengrin1024@gmail.com> | 2019-03-01 00:18:33 +0800 |
---|---|---|
committer | Ulf Hansson <ulf.hansson@linaro.org> | 2019-03-01 09:50:10 +0100 |
commit | d4721339dcca7def04909a8e60da43c19a24d8bf (patch) | |
tree | 1b8470579a6f38604ee40fc3e25f37480a737255 /include | |
parent | 4d3d534e9fd596e6f70ee19c75f0cd9aa5be2588 (diff) | |
download | linux-d4721339dcca7def04909a8e60da43c19a24d8bf.tar.bz2 |
mmc:fix a bug when max_discard is 0
The original purpose of the code I fix is to replace max_discard with
max_trim if max_trim is less than max_discard. When max_discard is 0
we should replace max_discard with max_trim as well, because
max_discard equals 0 happens only when the max_do_calc_max_discard
process is overflowed, so if mmc_can_trim(card) is true, max_discard
should be replaced by an available max_trim.
However, in the original code, there are two lines of code interfere
the right process.
1) if (max_discard && mmc_can_trim(card))
when max_discard is 0, it skips the process checking if max_discard
needs to be replaced with max_trim.
2) if (max_trim < max_discard)
the condition is false when max_discard is 0. it also skips the process
that replaces max_discard with max_trim, in fact, we should replace the
0-valued max_discard with max_trim.
Signed-off-by: Jiong Wu <Lohengrin1024@gmail.com>
Fixes: b305882fbc87 (mmc: core: optimize mmc_calc_max_discard)
Cc: stable@vger.kernel.org # v4.17+
Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions