diff options
| author | Zhan Xusheng <zhanxusheng1024@gmail.com> | 2026-08-04 10:25:00 +0800 |
|---|---|---|
| committer | Ulf Hansson <ulfh@kernel.org> | 2026-08-04 15:39:11 +0200 |
| commit | f64ea900e4bda3055ef24a2c906f8d049cf1c3bd (patch) | |
| tree | 253219ace7239910dab553c902deb5426ba9ec5e /tools/perf/scripts/python/bin/stackcollapse-report | |
| parent | c125ee35a49a0518521b52b27631eef061b8719a (diff) | |
mmc: omap_hsmmc: fix busy_timeout overflow in ns conversion on 32-bit
omap_hsmmc_prepare_data() converts the command busy timeout to nanoseconds
with:
timeout = req->cmd->busy_timeout * NSEC_PER_MSEC;
busy_timeout is an unsigned int (milliseconds) and timeout is a u64, but
NSEC_PER_MSEC is 1000000L. On 32-bit builds the multiplication is
performed in 32-bit arithmetic and wraps for busy_timeout values above
~4294 ms, before the result is assigned to the u64.
The driver does not set mmc->max_busy_timeout, so the core does not cap the
busy timeout, and commands such as erase or SANITIZE (MMC_SANITIZE_TIMEOUT_MS
is 240000 ms) can pass a busy_timeout far larger than 4294 ms. The wrapped,
much smaller ns value is then programmed via set_data_timeout(), so the data
timeout is set too short and the operation can time out prematurely.
Cast busy_timeout to u64 before the multiplication so the conversion is done
in 64-bit arithmetic.
Fixes: 8cc9a3e73de1 ("mmc: host: omap_hsmmc: use generic_cmd6_time to program timeout value for CMD6")
Cc: stable@vger.kernel.org
Signed-off-by: Zhan Xusheng <zhanxusheng@xiaomi.com>
Signed-off-by: Ulf Hansson <ulfh@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-report')
0 files changed, 0 insertions, 0 deletions
