Commit 0c0eb4ca authored by Zi Yan's avatar Zi Yan Committed by Vinod Koul

dmaengine: avoid map_cnt overflow with CONFIG_DMA_ENGINE_RAID

When CONFIG_DMA_ENGINE_RAID is enabled, unmap pool size can reach to
256. But in struct dmaengine_unmap_data, map_cnt is only u8, wrapping
to 0, if the unmap pool is maximally used. This triggers BUG() when
struct dmaengine_unmap_data is freed. Use u16 to fix the problem.
Signed-off-by: default avatarZi Yan <zi.yan@cs.rutgers.edu>
Signed-off-by: default avatarVinod Koul <vinod.koul@intel.com>
parent 7928b2cb
...@@ -470,7 +470,11 @@ typedef void (*dma_async_tx_callback_result)(void *dma_async_param, ...@@ -470,7 +470,11 @@ typedef void (*dma_async_tx_callback_result)(void *dma_async_param,
const struct dmaengine_result *result); const struct dmaengine_result *result);
struct dmaengine_unmap_data { struct dmaengine_unmap_data {
#if IS_ENABLED(CONFIG_DMA_ENGINE_RAID)
u16 map_cnt;
#else
u8 map_cnt; u8 map_cnt;
#endif
u8 to_cnt; u8 to_cnt;
u8 from_cnt; u8 from_cnt;
u8 bidi_cnt; u8 bidi_cnt;
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment