On 2/15/24 1:47 PM, Bart Van Assche wrote: > If kiocb_set_cancel_fn() is called for I/O submitted via io_uring, the > following kernel warning appears: > > WARNING: CPU: 3 PID: 368 at fs/aio.c:598 kiocb_set_cancel_fn+0x9c/0xa8 > Call trace: > kiocb_set_cancel_fn+0x9c/0xa8 > ffs_epfile_read_iter+0x144/0x1d0 > io_read+0x19c/0x498 > io_issue_sqe+0x118/0x27c > io_submit_sqes+0x25c/0x5fc > __arm64_sys_io_uring_enter+0x104/0xab0 > invoke_syscall+0x58/0x11c > el0_svc_common+0xb4/0xf4 > do_el0_svc+0x2c/0xb0 > el0_svc+0x2c/0xa4 > el0t_64_sync_handler+0x68/0xb4 > el0t_64_sync+0x1a4/0x1a8 > > Fix this by setting the IOCB_AIO_RW flag for read and write I/O that is > submitted by libaio. Like I said weeks ago, let's please get this fix in NOW and we can debate what to do about cancelations in general for aio separately. This patch 1 is a real fix, and it'd be silly to keep this stalled while the other stuff is ongoing. This isn't a critique at at you Bart, really just wanted to reply to teh cover letter but there isn't one. Christian, can you queue this up for 6.8 and mark it for stable? -- Jens Axboe
