summaryrefslogtreecommitdiffstats
path: root/mm/mprotect.c
diff options
context:
space:
mode:
authorChristian Löhle <CLoehle@hyperstone.com>2022-02-04 15:11:37 +0000
committerUlf Hansson <ulf.hansson@linaro.org>2022-02-08 16:04:49 +0100
commit54309fde1a352ad2674ebba004a79f7d20b9f037 (patch)
tree81ddbb9fa104e7401bdffd1f498e38e64239aef6 /mm/mprotect.c
parentbd2db32e7c3e35bd4d9b8bbff689434a50893546 (diff)
downloadlinux-54309fde1a352ad2674ebba004a79f7d20b9f037.tar.bz2
mmc: block: fix read single on recovery logic
On reads with MMC_READ_MULTIPLE_BLOCK that fail, the recovery handler will use MMC_READ_SINGLE_BLOCK for each of the blocks, up to MMC_READ_SINGLE_RETRIES times each. The logic for this is fixed to never report unsuccessful reads as success to the block layer. On command error with retries remaining, blk_update_request was called with whatever value error was set last to. In case it was last set to BLK_STS_OK (default), the read will be reported as success, even though there was no data read from the device. This could happen on a CRC mismatch for the response, a card rejecting the command (e.g. again due to a CRC mismatch). In case it was last set to BLK_STS_IOERR, the error is reported correctly, but no retries will be attempted. Fixes: 81196976ed946c ("mmc: block: Add blk-mq support") Cc: stable@vger.kernel.org Signed-off-by: Christian Loehle <cloehle@hyperstone.com> Reviewed-by: Adrian Hunter <adrian.hunter@intel.com> Link: https://lore.kernel.org/r/bc706a6ab08c4fe2834ba0c05a804672@hyperstone.com Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org>
Diffstat (limited to 'mm/mprotect.c')
0 files changed, 0 insertions, 0 deletions