diff options
| author | Mark Brown <[email protected]> | 2021-10-08 13:31:57 +0000 |
|---|---|---|
| committer | Mark Brown <[email protected]> | 2021-10-14 11:47:29 +0000 |
| commit | 6098475d4cb48d821bdf453c61118c56e26294f0 (patch) | |
| tree | ddd30f9c1cc1ffc9e4f9e1fcb3fe4abc53d2b121 /scripts/gcc-plugins/randomize_layout_plugin.c | |
| parent | spi: bcm-qspi: clear MSPI spifie interrupt during probe (diff) | |
| download | kernel-6098475d4cb48d821bdf453c61118c56e26294f0.tar.gz kernel-6098475d4cb48d821bdf453c61118c56e26294f0.zip | |
spi: Fix deadlock when adding SPI controllers on SPI buses
Currently we have a global spi_add_lock which we take when adding new
devices so that we can check that we're not trying to reuse a chip
select that's already controlled. This means that if the SPI device is
itself a SPI controller and triggers the instantiation of further SPI
devices we trigger a deadlock as we try to register and instantiate
those devices while in the process of doing so for the parent controller
and hence already holding the global spi_add_lock. Since we only care
about concurrency within a single SPI bus move the lock to be per
controller, avoiding the deadlock.
This can be easily triggered in the case of spi-mux.
Reported-by: Uwe Kleine-König <[email protected]>
Signed-off-by: Mark Brown <[email protected]>
Diffstat (limited to 'scripts/gcc-plugins/randomize_layout_plugin.c')
0 files changed, 0 insertions, 0 deletions
