diff options
| author | Christian Marangi <[email protected]> | 2024-06-11 13:35:33 +0200 |
|---|---|---|
| committer | Thomas Bogendoerfer <[email protected]> | 2024-06-11 16:05:24 +0200 |
| commit | ce5cdd3b05216b704a704f466fb4c2dff3778caf (patch) | |
| tree | 525c451aa77f9522519f836df3ce9fefffc825d5 /lib/test_fortify/write_overflow-strncpy-src.c | |
| parent | 277a0363120276645ae598d8d5fea7265e076ae9 (diff) | |
mips: bmips: BCM6358: make sure CBR is correctly set
It was discovered that some device have CBR address set to 0 causing
kernel panic when arch_sync_dma_for_cpu_all is called.
This was notice in situation where the system is booted from TP1 and
BMIPS_GET_CBR() returns 0 instead of a valid address and
!!(read_c0_brcm_cmt_local() & (1 << 31)); not failing.
The current check whether RAC flush should be disabled or not are not
enough hence lets check if CBR is a valid address or not.
Fixes: ab327f8acdf8 ("mips: bmips: BCM6358: disable RAC flush for TP1")
Signed-off-by: Christian Marangi <[email protected]>
Acked-by: Florian Fainelli <[email protected]>
Signed-off-by: Thomas Bogendoerfer <[email protected]>
Diffstat (limited to 'lib/test_fortify/write_overflow-strncpy-src.c')
0 files changed, 0 insertions, 0 deletions