Hidayath Khan c27e360545 dibs: initialise dibs->lock in dibs_dev_alloc() ... dibs->lock is initialised by dibs_dev_add(), but a dibs device can already take interrupts before that call: ism_probe() runs ism_dev_init(), and hence request_irq(), before it calls dibs_dev_add(). No client can have registered a dmb at that point, so no dmb interrupt can occur, but a GID event interrupt can, and ism_handle_irq() takes dibs->lock unconditionally on entry, before it inspects anything else. Initialise the lock in dibs_dev_alloc() instead, so that it is valid as soon as a driver can publish the device to its interrupt handler. Fixes: cc21191b58 ("dibs: Move data path to dibs layer") Cc: stable@vger.kernel.org Reviewed-by: Alexandra Winter <wintera@linux.ibm.com> Signed-off-by: Hidayath Khan <hidayath@linux.ibm.com> Link: https://patch.msgid.link/20260730124227.167829-1-hidayath@linux.ibm.com Signed-off-by: Jakub Kicinski <kuba@kernel.org>		2026-08-05 17:41:38 -07:00
..
dibs_loopback.c	dibs: fix use-after-free of dmb_node in loopback attach/detach/unregister	2026-07-29 16:46:51 -07:00
dibs_loopback.h
dibs_main.c	dibs: initialise dibs->lock in dibs_dev_alloc()	2026-08-05 17:41:38 -07:00
Kconfig	dibs: Improve DIBS prompts and help texts	2026-05-18 16:53:53 -07:00
Makefile