aboutsummaryrefslogtreecommitdiff
path: root/lib/test_fortify/write_overflow-strlcpy-src.c
diff options
context:
space:
mode:
authorTomi Valkeinen <[email protected]>2023-12-07 08:57:48 +0100
committerMauro Carvalho Chehab <[email protected]>2023-12-09 07:45:33 +0100
commit870565f063a58576e8a4529f122cac4325c6b395 (patch)
tree65f88264883db8417294e9fa97ab9fbba543a7b2 /lib/test_fortify/write_overflow-strlcpy-src.c
parent0753874617de883c6d4da903142f334f76a75d70 (diff)
media: rkisp1: Fix IRQ disable race issue
In rkisp1_isp_stop() and rkisp1_csi_disable() the driver masks the interrupts and then apparently assumes that the interrupt handler won't be running, and proceeds in the stop procedure. This is not the case, as the interrupt handler can already be running, which would lead to the ISP being disabled while the interrupt handler handling a captured frame. This brings up two issues: 1) the ISP could be powered off while the interrupt handler is still running and accessing registers, leading to board lockup, and 2) the interrupt handler code and the code that disables the streaming might do things that conflict. It is not clear to me if 2) causes a real issue, but 1) can be seen with a suitable delay (or printk in my case) in the interrupt handler, leading to board lockup. Link: https://lore.kernel.org/r/[email protected] Tested-by: Adam Ford <[email protected]> #imx8mp-beacon Signed-off-by: Tomi Valkeinen <[email protected]> Signed-off-by: Laurent Pinchart <[email protected]> Signed-off-by: Mauro Carvalho Chehab <[email protected]>
Diffstat (limited to 'lib/test_fortify/write_overflow-strlcpy-src.c')
0 files changed, 0 insertions, 0 deletions