test_dma_loop: Fix fail with dma_mcux_lpc #94114
Open
+14
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Modify the
dma_mcux_lpc
driver to include a sanity check when allocating channels. Release channels upon concluding thetest_dma_loop
test.Fixes #91670.
The condition was instigated with the DMA driver context being added to the
dma_mcux_lpc
driver (with eeaf860, yes, I acknowledge that I broke this), which enables channels to be requested (allocated). Thetest_dma_loop
test requested multiple channels (only a single one was used at a time, but they didn't get released) and as the driver was configured to hold internal state only for a limited number of channels (CONFIG_DMA_MCUX_LPC_NUMBER_OF_CHANNELS_ALLOCATED
) without a sanity check when allocating it for each channel, the array holding that state structs was overrun, resulting in memory corruption and system crash.