Jens Axboe 810e401b34 io_uring: ensure IOPOLL locks around deferred work ... No direct upstream commit exists for this issue. It was fixed in 5.18 as part of a larger rework of the completion side. io_commit_cqring() writes the CQ ring tail to make it visible, but it also kicks off any deferred work we have. A ring setup with IOPOLL does not need any locking around the CQ ring updates, as we're always under the ctx uring_lock. But if we have deferred work that needs processing, then io_queue_deferred() assumes that the completion_lock is held, as it is for !IOPOLL. Add a lockdep assertion to check and document this fact, and have io_iopoll_complete() check if we have deferred work and run that separately with the appropriate lock grabbed. Cc: stable@vger.kernel.org # 5.10, 5.15 Reported-by: dghost david <daviduniverse18@gmail.com> Signed-off-by: Jens Axboe <axboe@kernel.dk> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>		2023-07-27 08:44:01 +02:00
..
io_uring.c	io_uring: ensure IOPOLL locks around deferred work	2023-07-27 08:44:01 +02:00
io-wq.c	io_uring: don't gate task_work run on TIF_NOTIFY_SIGNAL	2023-01-24 07:19:56 +01:00
io-wq.h	io_uring: import 5.15-stable io_uring	2023-01-04 11:39:23 +01:00
Makefile	io_uring: import 5.15-stable io_uring	2023-01-04 11:39:23 +01:00