io_uring: don't issue reqs in iopoll mode when ctx is dying
PATCH 1/1 io_uring: don't issue reqs in iopoll mode when ctx is dying
Abaci Robot reported following panic:
------------[ cut here ]------------ refcount_t: underflow; use-after-free. WARNING: CPU: 1 PID: 195 at lib/refcount.c:28 refcount_warn_saturate+0x137/0x140 Modules linked in: CPU: 1 PID: 195 Comm: kworker/u4:2 Not tainted 5.11.0-rc3+ #70 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.11.1-0-g0551a4be2c-prebuilt.qemu-project.or4 Workqueue: events_unbound io_ring_exit_work RIP: 0010:refcount_warn_saturate+0x137/0x140 Code: 05 ad 63 49 08 01 e8 45 0f 6f 00 0f 0b e9 16 ff ff ff e8 4c ba ae ff 48 c7 c7 28 2e 7c 82 c6 05 90 63 40 RSP: 0018:ffffc900002e3cc8 EFLAGS: 00010282 RAX: 0000000000000000 RBX: 0000000000000003 RCX: 0000000000000000 RDX: ffff888102918000 RSI: ffffffff81150a34 RDI: ffff88813bd28570 RBP: ffff8881075cd348 R08: 0000000000000001 R09: 0000000000000001 R10: 0000000000000001 R11: 0000000000080000 R12: ffff8881075cd308 R13: ffff8881075cd348 R14: ffff888122d33ab8 R15: ffff888104780300 FS: 0000000000000000(0000) GS:ffff88813bd00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000108 CR3: 0000000107636005 CR4: 0000000000060ee0 Call Trace: io_dismantle_req+0x3f3/0x5b0 __io_free_req+0x2c/0x270 io_put_req+0x4c/0x70 io_wq_cancel_cb+0x171/0x470 ? io_match_task.part.0+0x80/0x80 __io_uring_cancel_task_requests+0xa0/0x190 io_ring_exit_work+0x32/0x3e0 process_one_work+0x2f3/0x720 worker_thread+0x5a/0x4b0 ? process_one_work+0x720/0x720 kthread+0x138/0x180 ? kthread_park+0xd0/0xd0 ret_from_fork+0x1f/0x30
Later system will panic for some memory corruption.
The io_identity's count is underflowed. It's because in io_put_identity, first argument tctx comes from req->task->io_uring, the second argument comes from the task context that calls io_req_init_async, so the compare in io_put_identity maybe meaningless. See below case:
task context A issue one polled req, then req->task = A.
task context B do iopoll, above req returns with EAGAIN error. task context B re-issue req, call io_queue_async_work for req. req->task->io_uring will set to task context B's identity, or cow new one.
then for above case, in io_put_identity(), the compare is meaningless.
IIUC, req->task should indicates the initial task context that issues req, then if it gets EAGAIN error, we'll call io_prep_async_work() in req->task context, but iopoll reqs seems special, they maybe issued successfully and got re-issued in other task context because of EAGAIN error.
Currently for this panic, we can disable issuing reqs that are returned with EAGAIN error in iopoll mode when ctx is dying, but we may need to re-consider the io identity codes more.
--- fs/io_uring.c | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-)
fs/io_uring.c +6 -1
@@ -2467,7 +2467,12 @@ static void io_iopoll_complete(struct io_ring_ctx *ctx, unsigned int *nr_events,int cflags =0 ; req = list_first_entry(done, struct io_kiocb, inflight_entry); -if (READ_ONCE (req->result) == -EAGAIN ) { +/* +* If ctx is dying, don't need to issue reqs that are returned +* with EAGAIN error, since there maybe no users to reap them. +*/ +if ((READ_ONCE (req->result) == -EAGAIN ) && + !percpu_ref_is_dying (&ctx->refs)) { req->result =0 ; req->iopoll_completed =0 ;list_move_tail (&req->inflight_entry, &again);
Signature · 1 line
2.17.2
Quoted 46 lines · Xiaoguang Wang
Abaci Robot reported following panic:
------------[ cut here ]------------ refcount_t: underflow; use-after-free. WARNING: CPU: 1 PID: 195 at lib/refcount.c:28 refcount_warn_saturate+0x137/0x140 Modules linked in: CPU: 1 PID: 195 Comm: kworker/u4:2 Not tainted 5.11.0-rc3+ #70 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.11.1-0-g0551a4be2c-prebuilt.qemu-project.or4 Workqueue: events_unbound io_ring_exit_work RIP: 0010:refcount_warn_saturate+0x137/0x140 Code: 05 ad 63 49 08 01 e8 45 0f 6f 00 0f 0b e9 16 ff ff ff e8 4c ba ae ff 48 c7 c7 28 2e 7c 82 c6 05 90 63 40 RSP: 0018:ffffc900002e3cc8 EFLAGS: 00010282 RAX: 0000000000000000 RBX: 0000000000000003 RCX: 0000000000000000 RDX: ffff888102918000 RSI: ffffffff81150a34 RDI: ffff88813bd28570 RBP: ffff8881075cd348 R08: 0000000000000001 R09: 0000000000000001 R10: 0000000000000001 R11: 0000000000080000 R12: ffff8881075cd308 R13: ffff8881075cd348 R14: ffff888122d33ab8 R15: ffff888104780300 FS: 0000000000000000(0000) GS:ffff88813bd00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000108 CR3: 0000000107636005 CR4: 0000000000060ee0 Call Trace: io_dismantle_req+0x3f3/0x5b0 __io_free_req+0x2c/0x270 io_put_req+0x4c/0x70 io_wq_cancel_cb+0x171/0x470 ? io_match_task.part.0+0x80/0x80 __io_uring_cancel_task_requests+0xa0/0x190 io_ring_exit_work+0x32/0x3e0 process_one_work+0x2f3/0x720 worker_thread+0x5a/0x4b0 ? process_one_work+0x720/0x720 kthread+0x138/0x180 ? kthread_park+0xd0/0xd0 ret_from_fork+0x1f/0x30Later system will panic for some memory corruption.
The io_identity's count is underflowed. It's because in
io_put_identity, first argument tctx comes fromreq->task->io_uring, the second argument comes from the task context that callsio_req_init_async, so the compare inio_put_identitymaybe meaningless. See below case:
task context A issue one polled req, thenreq->task= A.
task context B do iopoll, above req returns with EAGAIN error. task context B re-issue req, callio_queue_async_workfor req.req->task->io_uringwill set to task context B's identity, or cow new one.
then for above case, inio_put_identity(), the compare is meaningless.
Quoted 4 lines
IIUC,
req->taskshould indicates the initial task context that issues req, then if it gets EAGAIN error, we'll callio_prep_async_work()inreq->taskcontext, but iopoll reqs seems special, they maybe issued successfully and got re-issued in other task context because of EAGAIN error.
Looks as you say, but the patch doesn't solve the issue completely.
1. We must not do io_queue_async_work() under a different task context, because of it potentially uses a different set of resources. So, I just thought that it would be better to punt it to the right task context via task_work. But...
2. ...iovec import from io_resubmit_prep() might happen after submit ends, i.e. when iovec was freed in userspace. And that's not great at all.
Quoted 29 lines
Currently for this panic, we can disable issuing reqs that are returned with EAGAIN error in iopoll mode when ctx is dying, but we may need to re-consider the io identity codes more.
Reported-by Abaci Robot <[email protected]>Signed-off-by Xiaoguang Wang <[email protected]>--- fs/io_uring.c | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-)fs/io_uring.c +6
-1@@ -2467,7 +2467,12 @@ static void io_iopoll_complete(struct io_ring_ctx *ctx, unsigned int *nr_events,int cflags =0 ; req = list_first_entry(done, struct io_kiocb, inflight_entry); -if (READ_ONCE (req->result) == -EAGAIN ) { +/* +* If ctx is dying, don't need to issue reqs that are returned +* with EAGAIN error, since there maybe no users to reap them. +*/ +if ((READ_ONCE (req->result) == -EAGAIN ) && + !percpu_ref_is_dying (&ctx->refs)) { req->result =0 ; req->iopoll_completed =0 ;list_move_tail (&req->inflight_entry, &again);
Signature · 1 line
Pavel Begunkov
hi,
Quoted 52 lines · Xiaoguang Wang
Quoted 46 lines
Abaci Robot reported following panic:
------------[ cut here ]------------ refcount_t: underflow; use-after-free. WARNING: CPU: 1 PID: 195 at lib/refcount.c:28 refcount_warn_saturate+0x137/0x140 Modules linked in: CPU: 1 PID: 195 Comm: kworker/u4:2 Not tainted 5.11.0-rc3+ #70 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.11.1-0-g0551a4be2c-prebuilt.qemu-project.or4 Workqueue: events_unbound io_ring_exit_work RIP: 0010:refcount_warn_saturate+0x137/0x140 Code: 05 ad 63 49 08 01 e8 45 0f 6f 00 0f 0b e9 16 ff ff ff e8 4c ba ae ff 48 c7 c7 28 2e 7c 82 c6 05 90 63 40 RSP: 0018:ffffc900002e3cc8 EFLAGS: 00010282 RAX: 0000000000000000 RBX: 0000000000000003 RCX: 0000000000000000 RDX: ffff888102918000 RSI: ffffffff81150a34 RDI: ffff88813bd28570 RBP: ffff8881075cd348 R08: 0000000000000001 R09: 0000000000000001 R10: 0000000000000001 R11: 0000000000080000 R12: ffff8881075cd308 R13: ffff8881075cd348 R14: ffff888122d33ab8 R15: ffff888104780300 FS: 0000000000000000(0000) GS:ffff88813bd00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000108 CR3: 0000000107636005 CR4: 0000000000060ee0 Call Trace: io_dismantle_req+0x3f3/0x5b0 __io_free_req+0x2c/0x270 io_put_req+0x4c/0x70 io_wq_cancel_cb+0x171/0x470 ? io_match_task.part.0+0x80/0x80 __io_uring_cancel_task_requests+0xa0/0x190 io_ring_exit_work+0x32/0x3e0 process_one_work+0x2f3/0x720 worker_thread+0x5a/0x4b0 ? process_one_work+0x720/0x720 kthread+0x138/0x180 ? kthread_park+0xd0/0xd0 ret_from_fork+0x1f/0x30Later system will panic for some memory corruption.
The io_identity's count is underflowed. It's because in
io_put_identity, first argument tctx comes fromreq->task->io_uring, the second argument comes from the task context that callsio_req_init_async, so the compare inio_put_identitymaybe meaningless. See below case:
task context A issue one polled req, thenreq->task= A.
task context B do iopoll, above req returns with EAGAIN error. task context B re-issue req, callio_queue_async_workfor req.req->task->io_uringwill set to task context B's identity, or cow new one.
then for above case, inio_put_identity(), the compare is meaningless.Quoted 4 lines
IIUC,
req->taskshould indicates the initial task context that issues req, then if it gets EAGAIN error, we'll callio_prep_async_work()inreq->taskcontext, but iopoll reqs seems special, they maybe issued successfully and got re-issued in other task context because of EAGAIN error.
Quoted 8 lines
Looks as you say, but the patch doesn't solve the issue completely.
1. We must not doio_queue_async_work()under a different task context, because of it potentially uses a different set of resources. So, I just thought that it would be better to punt it to the right task context viatask_work. But...2. ...iovec import from
io_resubmit_prep()might happen after submit ends, i.e. when iovec was freed in userspace. And that's not great at all.
Yes, agree, that's why I say we neeed to re-consider the io identity codes more in commit message :) I'll have a try to prepare a better one.
Regards,
Xiaoguang Wang
Quoted 31 lines
Quoted 30 lines
Currently for this panic, we can disable issuing reqs that are returned with EAGAIN error in iopoll mode when ctx is dying, but we may need to re-consider the io identity codes more.
Reported-by Abaci Robot <[email protected]>Signed-off-by Xiaoguang Wang <[email protected]>--- fs/io_uring.c | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-)fs/io_uring.c +6
-1@@ -2467,7 +2467,12 @@ static void io_iopoll_complete(struct io_ring_ctx *ctx, unsigned int *nr_events,int cflags =0 ; req = list_first_entry(done, struct io_kiocb, inflight_entry); -if (READ_ONCE (req->result) == -EAGAIN ) { +/* +* If ctx is dying, don't need to issue reqs that are returned +* with EAGAIN error, since there maybe no users to reap them. +*/ +if ((READ_ONCE (req->result) == -EAGAIN ) && + !percpu_ref_is_dying (&ctx->refs)) { req->result =0 ; req->iopoll_completed =0 ;list_move_tail (&req->inflight_entry, &again);
Quoted 21 lines · Xiaoguang Wang
Quoted 21 lines
Quoted 10 lines
The io_identity's count is underflowed. It's because in
io_put_identity, first argument tctx comes fromreq->task->io_uring, the second argument comes from the task context that callsio_req_init_async, so the compare inio_put_identitymaybe meaningless. See below case:
task context A issue one polled req, thenreq->task= A.
task context B do iopoll, above req returns with EAGAIN error. task context B re-issue req, callio_queue_async_workfor req.req->task->io_uringwill set to task context B's identity, or cow new one. then for above case, inio_put_identity(), the compare is meaningless.Quoted 4 lines
IIUC,
req->taskshould indicates the initial task context that issues req, then if it gets EAGAIN error, we'll callio_prep_async_work()inreq->taskcontext, but iopoll reqs seems special, they maybe issued successfully and got re-issued in other task context because of EAGAIN error.Looks as you say, but the patch doesn't solve the issue completely.
1. We must not doio_queue_async_work()under a different task context, because of it potentially uses a different set of resources. So, I just thought that it would be better to punt it to the right task context viatask_work. But...
Quoted 4 lines
Quoted 2 lines
2. ...iovec import from
io_resubmit_prep()might happen after submit ends, i.e. when iovec was freed in userspace. And that's not great at all.Yes, agree, that's why I say we neeed to re-consider the io identity codes more in commit message :) I'll have a try to prepare a better one.
I'd vote for dragging -AGAIN'ed reqs that don't need io_import_iovec() through task_work for resubmission, and fail everything else. Not great, but imho better than always setting async_data.
Signature · 1 line
Pavel Begunkov
Quoted 22 lines · Pavel Begunkov
Quoted 21 lines · Xiaoguang Wang
Quoted 21 lines
Quoted 10 lines
The io_identity's count is underflowed. It's because in
io_put_identity, first argument tctx comes fromreq->task->io_uring, the second argument comes from the task context that callsio_req_init_async, so the compare inio_put_identitymaybe meaningless. See below case:
task context A issue one polled req, thenreq->task= A.
task context B do iopoll, above req returns with EAGAIN error. task context B re-issue req, callio_queue_async_workfor req.req->task->io_uringwill set to task context B's identity, or cow new one. then for above case, inio_put_identity(), the compare is meaningless.Quoted 4 lines
IIUC,
req->taskshould indicates the initial task context that issues req, then if it gets EAGAIN error, we'll callio_prep_async_work()inreq->taskcontext, but iopoll reqs seems special, they maybe issued successfully and got re-issued in other task context because of EAGAIN error.Looks as you say, but the patch doesn't solve the issue completely.
1. We must not doio_queue_async_work()under a different task context, because of it potentially uses a different set of resources. So, I just thought that it would be better to punt it to the right task context viatask_work. But...
Quoted 8 lines
Quoted 4 lines
Quoted 2 lines
2. ...iovec import from
io_resubmit_prep()might happen after submit ends, i.e. when iovec was freed in userspace. And that's not great at all.Yes, agree, that's why I say we neeed to re-consider the io identity codes more in commit message :) I'll have a try to prepare a better one.
I'd vote for dragging -AGAIN'ed reqs that don't need
io_import_iovec()throughtask_workfor resubmission, and fail everything else. Not great, but imho better than always settingasync_data.
Hey Xiaoguang, are you working on this? I would like to leave it to you, If you do.
Signature · 1 line
Pavel Begunkov
hi Pavel,
Quoted 28 lines · Pavel Begunkov
Quoted 27 lines · Xiaoguang Wang
Quoted 25 lines
Quoted 15 lines
Quoted 10 lines
The io_identity's count is underflowed. It's because in
io_put_identity, first argument tctx comes fromreq->task->io_uring, the second argument comes from the task context that callsio_req_init_async, so the compare inio_put_identitymaybe meaningless. See below case:
task context A issue one polled req, thenreq->task= A.
task context B do iopoll, above req returns with EAGAIN error. task context B re-issue req, callio_queue_async_workfor req.req->task->io_uringwill set to task context B's identity, or cow new one.
then for above case, inio_put_identity(), the compare is meaningless.Quoted 4 lines
IIUC,
req->taskshould indicates the initial task context that issues req, then if it gets EAGAIN error, we'll callio_prep_async_work()inreq->taskcontext, but iopoll reqs seems special, they maybe issued successfully and got re-issued in other task context because of EAGAIN error.Quoted 8 lines
Looks as you say, but the patch doesn't solve the issue completely.
1. We must not doio_queue_async_work()under a different task context, because of it potentially uses a different set of resources. So, I just thought that it would be better to punt it to the right task context viatask_work. But...2. ...iovec import from
io_resubmit_prep()might happen after submit ends, i.e. when iovec was freed in userspace. And that's not great at all.Yes, agree, that's why I say we neeed to re-consider the io identity codes more in commit message :) I'll have a try to prepare a better one.
Quoted 6 lines
Quoted 3 lines
I'd vote for dragging -AGAIN'ed reqs that don't need
io_import_iovec()throughtask_workfor resubmission, and fail everything else. Not great, but imho better than always settingasync_data.Hey Xiaoguang, are you working on this? I would like to leave it to you, If you do.
Sorry, currently I'm busy with other project and don't have much time to work on it yet. Hao Xu will help to continue work on the new version patch.
Regards,
Xiaoguang Wang
Quoted 1 line
Jens Axboe
maintainerQuoted 30 lines · Xiaoguang Wang
hi Pavel,
Quoted 28 lines · Pavel Begunkov
Quoted 27 lines · Xiaoguang Wang
Quoted 25 lines
Quoted 15 lines
Quoted 10 lines
The io_identity's count is underflowed. It's because in
io_put_identity, first argument tctx comes fromreq->task->io_uring, the second argument comes from the task context that callsio_req_init_async, so the compare inio_put_identitymaybe meaningless. See below case:
task context A issue one polled req, thenreq->task= A.
task context B do iopoll, above req returns with EAGAIN error. task context B re-issue req, callio_queue_async_workfor req.req->task->io_uringwill set to task context B's identity, or cow new one.
then for above case, inio_put_identity(), the compare is meaningless.Quoted 4 lines
IIUC,
req->taskshould indicates the initial task context that issues req, then if it gets EAGAIN error, we'll callio_prep_async_work()inreq->taskcontext, but iopoll reqs seems special, they maybe issued successfully and got re-issued in other task context because of EAGAIN error.Quoted 8 lines
Looks as you say, but the patch doesn't solve the issue completely.
1. We must not doio_queue_async_work()under a different task context, because of it potentially uses a different set of resources. So, I just thought that it would be better to punt it to the right task context viatask_work. But...2. ...iovec import from
io_resubmit_prep()might happen after submit ends, i.e. when iovec was freed in userspace. And that's not great at all.Yes, agree, that's why I say we neeed to re-consider the io identity codes more in commit message :) I'll have a try to prepare a better one.
Quoted 8 lines
Quoted 6 lines
Quoted 3 lines
I'd vote for dragging -AGAIN'ed reqs that don't need
io_import_iovec()throughtask_workfor resubmission, and fail everything else. Not great, but imho better than always settingasync_data.Hey Xiaoguang, are you working on this? I would like to leave it to you, If you do.
Sorry, currently I'm busy with other project and don't have much time to work on it yet. Hao Xu will help to continue work on the new version patch.
Is it issue or reissue? I found this one today:
https://lore.kernel.org/io-uring/[email protected]/
Signature · 1 line
Jens Axboe
hi,
Quoted 35 lines · Xiaoguang Wang
Quoted 34 lines
hi Pavel,
Quoted 32 lines · Pavel Begunkov
Quoted 30 lines · Xiaoguang Wang
Quoted 21 lines
Quoted 21 lines
Quoted 10 lines
The io_identity's count is underflowed. It's because in
io_put_identity, first argument tctx comes fromreq->task->io_uring, the second argument comes from the task context that callsio_req_init_async, so the compare inio_put_identitymaybe meaningless. See below case:
task context A issue one polled req, thenreq->task= A.
task context B do iopoll, above req returns with EAGAIN error. task context B re-issue req, callio_queue_async_workfor req.req->task->io_uringwill set to task context B's identity, or cow new one.
then for above case, inio_put_identity(), the compare is meaningless.Quoted 4 lines
IIUC,
req->taskshould indicates the initial task context that issues req, then if it gets EAGAIN error, we'll callio_prep_async_work()inreq->taskcontext, but iopoll reqs seems special, they maybe issued successfully and got re-issued in other task context because of EAGAIN error.Looks as you say, but the patch doesn't solve the issue completely.
1. We must not doio_queue_async_work()under a different task context, because of it potentially uses a different set of resources. So, I just thought that it would be better to punt it to the right task context viatask_work. But...Quoted 4 lines
Quoted 2 lines
2. ...iovec import from
io_resubmit_prep()might happen after submit ends, i.e. when iovec was freed in userspace. And that's not great at all.Yes, agree, that's why I say we neeed to re-consider the io identity codes more in commit message :) I'll have a try to prepare a better one.
I'd vote for dragging -AGAIN'ed reqs that don't need
io_import_iovec()throughtask_workfor resubmission, and fail everything else. Not great, but imho better than always settingasync_data.
Quoted 8 lines
Quoted 4 lines
Quoted 2 lines
Hey Xiaoguang, are you working on this? I would like to leave it to you, If you do.
Sorry, currently I'm busy with other project and don't have much time to work on it yet. Hao Xu will help to continue work on the new version patch.
Is it issue or reissue? I found this one today:
Yeah, my initial patch is similar to yours, but it only solves the bug described in my commit message partially(ctx is dying), you can have a look at my commit message for the bug bug scene, thanks.
Regards,
Xiaoguang Wang
Quoted 1 line
Jens Axboe
maintainerQuoted 42 lines · Xiaoguang Wang
hi,
Quoted 40 lines · Xiaoguang Wang
Quoted 38 lines
hi Pavel,
Quoted 28 lines · Pavel Begunkov
Quoted 27 lines · Xiaoguang Wang
Quoted 25 lines
Quoted 15 lines
Quoted 10 lines
The io_identity's count is underflowed. It's because in
io_put_identity, first argument tctx comes fromreq->task->io_uring, the second argument comes from the task context that callsio_req_init_async, so the compare inio_put_identitymaybe meaningless. See below case:
task context A issue one polled req, thenreq->task= A.
task context B do iopoll, above req returns with EAGAIN error. task context B re-issue req, callio_queue_async_workfor req.req->task->io_uringwill set to task context B's identity, or cow new one.
then for above case, inio_put_identity(), the compare is meaningless.Quoted 4 lines
IIUC,
req->taskshould indicates the initial task context that issues req, then if it gets EAGAIN error, we'll callio_prep_async_work()inreq->taskcontext, but iopoll reqs seems special, they maybe issued successfully and got re-issued in other task context because of EAGAIN error.Quoted 8 lines
Looks as you say, but the patch doesn't solve the issue completely.
1. We must not doio_queue_async_work()under a different task context, because of it potentially uses a different set of resources. So, I just thought that it would be better to punt it to the right task context viatask_work. But...2. ...iovec import from
io_resubmit_prep()might happen after submit ends, i.e. when iovec was freed in userspace. And that's not great at all.Yes, agree, that's why I say we neeed to re-consider the io identity codes more in commit message :) I'll have a try to prepare a better one.
Quoted 6 lines
Quoted 3 lines
I'd vote for dragging -AGAIN'ed reqs that don't need
io_import_iovec()throughtask_workfor resubmission, and fail everything else. Not great, but imho better than always settingasync_data.Hey Xiaoguang, are you working on this? I would like to leave it to you, If you do.
Sorry, currently I'm busy with other project and don't have much time to work on it yet. Hao Xu will help to continue work on the new version patch.
Quoted 6 lines
Quoted 3 lines
Is it issue or reissue? I found this one today:
Yeah, my initial patch is similar to yours, but it only solves the bug described in my commit message partially(ctx is dying), you can have a look at my commit message for the bug bug scene, thanks.
Are you sure? We just don't want to reissue it, we need to fail it. Hence if we catch it at reissue time, that should be enough. But I'm open to clue batting :-)
Signature · 1 line
Jens Axboe
Quoted 39 lines · Jens Axboe
Quoted 39 lines
Quoted 39 lines
Quoted 28 lines
Quoted 28 lines · Pavel Begunkov
Quoted 27 lines · Xiaoguang Wang
Quoted 25 lines
Quoted 15 lines
Quoted 10 lines
The io_identity's count is underflowed. It's because in
io_put_identity, first argument tctx comes fromreq->task->io_uring, the second argument comes from the task context that callsio_req_init_async, so the compare inio_put_identitymaybe meaningless. See below case:
task context A issue one polled req, thenreq->task= A.
task context B do iopoll, above req returns with EAGAIN error. task context B re-issue req, callio_queue_async_workfor req.req->task->io_uringwill set to task context B's identity, or cow new one.
then for above case, inio_put_identity(), the compare is meaningless.Quoted 4 lines
IIUC,
req->taskshould indicates the initial task context that issues req, then if it gets EAGAIN error, we'll callio_prep_async_work()inreq->taskcontext, but iopoll reqs seems special, they maybe issued successfully and got re-issued in other task context because of EAGAIN error.Quoted 8 lines
Looks as you say, but the patch doesn't solve the issue completely.
1. We must not doio_queue_async_work()under a different task context, because of it potentially uses a different set of resources. So, I just thought that it would be better to punt it to the right task context viatask_work. But...2. ...iovec import from
io_resubmit_prep()might happen after submit ends, i.e. when iovec was freed in userspace. And that's not great at all.Yes, agree, that's why I say we neeed to re-consider the io identity codes more in commit message :) I'll have a try to prepare a better one.
Quoted 8 lines
Quoted 6 lines
Quoted 3 lines
I'd vote for dragging -AGAIN'ed reqs that don't need
io_import_iovec()throughtask_workfor resubmission, and fail everything else. Not great, but imho better than always settingasync_data.Hey Xiaoguang, are you working on this? I would like to leave it to you, If you do.
Sorry, currently I'm busy with other project and don't have much time to work on it yet. Hao Xu will help to continue work on the new version patch.
Is it issue or reissue? I found this one today:
Quoted 8 lines
Quoted 4 lines
Quoted 1 line
Yeah, my initial patch is similar to yours, but it only solves the bug described in my commit message partially(ctx is dying), you can have a look at my commit message for the bug bug scene, thanks.
Are you sure? We just don't want to reissue it, we need to fail it. Hence if we catch it at reissue time, that should be enough. But I'm open to clue batting :-)
Jens, IOPOLL can happen from a different task, so
1) we don't want to grab io_wq_work context from it. As always we can pass it through task_work, or should be solved with your io-wq patches.
2) it happens who knows when in time, so iovec may be gone already -- same reasoning why io_[read,write]() copy it before going to io-wq.
Signature · 1 line
Pavel Begunkov
Quoted 10 lines · Pavel Begunkov
Quoted 3 lines
Are you sure? We just don't want to reissue it, we need to fail it. Hence if we catch it at reissue time, that should be enough. But I'm open to clue batting :-)
Jens, IOPOLL can happen from a different task, so
1) we don't want to grabio_wq_workcontext from it. As always we can pass it throughtask_work, or should be solved with your io-wq patches.2) it happens who knows when in time, so iovec may be gone already -- same reasoning why io_[read,write]() copy it before going to io-wq.
The diff below should solve the second problem by failing them (not tested).
1) can be left to the io-wq patches.
fs/io_uring.c +4 -1
@@ -2610,8 +2610,11 @@ static void io_iopoll_complete(struct io_ring_ctx *ctx, unsigned int *nr_events,list_del (&req->inflight_entry);if (READ_ONCE (req->result) == -EAGAIN ) { +bool reissue = req->async_data || + !io_op_defs[req->opcode].needs_async_data; + req->iopoll_completed =0 ; -if (io_rw_reissue (req)) +if (reissue &&io_rw_reissue (req))continue ; }
Signature · 1 line
Pavel Begunkov
Quoted 9 lines · Pavel Begunkov
Quoted 8 lines · Pavel Begunkov
Quoted 3 lines
Are you sure? We just don't want to reissue it, we need to fail it. Hence if we catch it at reissue time, that should be enough. But I'm open to clue batting :-)
Jens, IOPOLL can happen from a different task, so
1) we don't want to grabio_wq_workcontext from it. As always we can pass it throughtask_work, or should be solved with your io-wq patches.
Quoted 5 lines
Quoted 2 lines
2) it happens who knows when in time, so iovec may be gone already -- same reasoning why io_[read,write]() copy it before going to io-wq.
The diff below should solve the second problem by failing them (not tested).
1) can be left to the io-wq patches.
We can even try to init it in io_complete_rw_iopoll() similarly to __io_complete_rw(). The tricky part for me is that "!inline exec" comment, i.e. to distinct io_complete_rw_iopoll() -EAGAIN'ed inline and from IRQ/etc. Jens?
fs/io_uring.c +21 -6
@@ -2610,8 +2610,11 @@ static void io_iopoll_complete(struct io_ring_ctx *ctx, unsigned int *nr_events,list_del (&req->inflight_entry);if (READ_ONCE (req->result) == -EAGAIN ) { +bool reissue = req->async_data || + !io_op_defs[req->opcode].needs_async_data; + req->iopoll_completed =0 ; -if (io_rw_reissue (req)) +if (reissue &&io_rw_reissue (req))continue ; }
@@ -2829,7 +2832,7 @@ static bool io_resubmit_prep(struct io_kiocb *req) }#endif -static bool io_rw_reissue (struct io_kiocb *req) +static bool io_rw_reissue_prep (struct io_kiocb *req) {#ifdef CONFIG_BLOCK umode_t mode =file_inode (req->file)->i_mode;
@@ -2844,13 +2847,21 @@ static bool io_rw_reissue(struct io_kiocb *req) ret =io_sq_thread_acquire_mm_files (req->ctx, req); -if (!ret &&io_resubmit_prep (req)) { +if (!ret &&io_resubmit_prep (req)) +return true; +req_set_fail_links (req); +#endif +return false; + +} + +static bool io_rw_reissue (struct io_kiocb *req) +{ +if (io_rw_reissue_prep (req)) {refcount_inc (&req->refs);io_queue_async_work (req);return true; } -req_set_fail_links (req); -#endif return false; }
@@ -2885,8 +2896,12 @@ static void io_complete_rw_iopoll(struct kiocb *kiocb, long res, long res2)if (kiocb->ki_flags &IOCB_WRITE )kiocb_end_write (req); -if (res != -EAGAIN && res != req->result) +if (req == -EAGAIN ) { +if (/* !inline exec || */ !io_rw_reissue_prep (req)) +req_set_fail_links (req); + }else if (res != req->result) {req_set_fail_links (req); + }WRITE_ONCE (req->result, res);/* order with io_poll_complete() checking ->result */
Signature · 1 line
Pavel Begunkov
Quoted 30 lines · Xiaoguang Wang
hi Pavel,
Quoted 28 lines · Pavel Begunkov
Quoted 27 lines · Xiaoguang Wang
Quoted 25 lines
Quoted 15 lines
Quoted 10 lines
The io_identity's count is underflowed. It's because in
io_put_identity, first argument tctx comes fromreq->task->io_uring, the second argument comes from the task context that callsio_req_init_async, so the compare inio_put_identitymaybe meaningless. See below case:
task context A issue one polled req, thenreq->task= A.
task context B do iopoll, above req returns with EAGAIN error. task context B re-issue req, callio_queue_async_workfor req.req->task->io_uringwill set to task context B's identity, or cow new one. then for above case, inio_put_identity(), the compare is meaningless.Quoted 4 lines
IIUC,
req->taskshould indicates the initial task context that issues req, then if it gets EAGAIN error, we'll callio_prep_async_work()inreq->taskcontext, but iopoll reqs seems special, they maybe issued successfully and got re-issued in other task context because of EAGAIN error.Quoted 8 lines
Looks as you say, but the patch doesn't solve the issue completely.
1. We must not doio_queue_async_work()under a different task context, because of it potentially uses a different set of resources. So, I just thought that it would be better to punt it to the right task context viatask_work. But...2. ...iovec import from
io_resubmit_prep()might happen after submit ends, i.e. when iovec was freed in userspace. And that's not great at all.Yes, agree, that's why I say we neeed to re-consider the io identity codes more in commit message :) I'll have a try to prepare a better one.
Quoted 8 lines
Quoted 6 lines
Quoted 3 lines
I'd vote for dragging -AGAIN'ed reqs that don't need
io_import_iovec()throughtask_workfor resubmission, and fail everything else. Not great, but imho better than always settingasync_data.Hey Xiaoguang, are you working on this? I would like to leave it to you, If you do.
Sorry, currently I'm busy with other project and don't have much time to work on it yet. Hao Xu will help to continue work on the new version patch.
Thanks for letting know! It's really not a big deal, just was leaving it if someones wants to take a shot, but we'll get it fixed ourselves otherwise.
Signature · 1 line
Pavel Begunkov
Quoted 47 lines · Pavel Begunkov
Quoted 46 lines · Xiaoguang Wang
Abaci Robot reported following panic:
------------[ cut here ]------------ refcount_t: underflow; use-after-free. WARNING: CPU: 1 PID: 195 at lib/refcount.c:28 refcount_warn_saturate+0x137/0x140 Modules linked in: CPU: 1 PID: 195 Comm: kworker/u4:2 Not tainted 5.11.0-rc3+ #70 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.11.1-0-g0551a4be2c-prebuilt.qemu-project.or4 Workqueue: events_unbound io_ring_exit_work RIP: 0010:refcount_warn_saturate+0x137/0x140 Code: 05 ad 63 49 08 01 e8 45 0f 6f 00 0f 0b e9 16 ff ff ff e8 4c ba ae ff 48 c7 c7 28 2e 7c 82 c6 05 90 63 40 RSP: 0018:ffffc900002e3cc8 EFLAGS: 00010282 RAX: 0000000000000000 RBX: 0000000000000003 RCX: 0000000000000000 RDX: ffff888102918000 RSI: ffffffff81150a34 RDI: ffff88813bd28570 RBP: ffff8881075cd348 R08: 0000000000000001 R09: 0000000000000001 R10: 0000000000000001 R11: 0000000000080000 R12: ffff8881075cd308 R13: ffff8881075cd348 R14: ffff888122d33ab8 R15: ffff888104780300 FS: 0000000000000000(0000) GS:ffff88813bd00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000108 CR3: 0000000107636005 CR4: 0000000000060ee0 Call Trace: io_dismantle_req+0x3f3/0x5b0 __io_free_req+0x2c/0x270 io_put_req+0x4c/0x70 io_wq_cancel_cb+0x171/0x470 ? io_match_task.part.0+0x80/0x80 __io_uring_cancel_task_requests+0xa0/0x190 io_ring_exit_work+0x32/0x3e0 process_one_work+0x2f3/0x720 worker_thread+0x5a/0x4b0 ? process_one_work+0x720/0x720 kthread+0x138/0x180 ? kthread_park+0xd0/0xd0 ret_from_fork+0x1f/0x30Later system will panic for some memory corruption.
The io_identity's count is underflowed. It's because in
io_put_identity, first argument tctx comes fromreq->task->io_uring, the second argument comes from the task context that callsio_req_init_async, so the compare inio_put_identitymaybe meaningless. See below case:
task context A issue one polled req, thenreq->task= A.
task context B do iopoll, above req returns with EAGAIN error. task context B re-issue req, callio_queue_async_workfor req.req->task->io_uringwill set to task context B's identity, or cow new one.
then for above case, inio_put_identity(), the compare is meaningless.
Quoted 8 lines
Quoted 4 lines
IIUC,
req->taskshould indicates the initial task context that issues req, then if it gets EAGAIN error, we'll callio_prep_async_work()inreq->taskcontext, but iopoll reqs seems special, they maybe issued successfully and got re-issued in other task context because of EAGAIN error.Looks as you say, but the patch doesn't solve the issue completely.
1. We must not doio_queue_async_work()under a different task context, because of it potentially uses a different set of resources. So, I just
Hi Pavel,
I've some questions.
- Why would the resources be potentially different? My understanding
is the tasks which can share a uring instance must be in the same process, so they have same context(files, mm etc.)
- Assume 1 is true, why don't we just do something like this:
req->work.identity = req->task->io_uring->identity;
since req->task points to the original context
Quoted 5 lines
thought that it would be better to punt it to the right task context via
task_work. But...2. ...iovec import from
io_resubmit_prep()might happen after submit ends, i.e. when iovec was freed in userspace. And that's not great at all.
I didn't get it why here we need to import iovec. My understanding is OPs(such as readv writev) which need imoport iovec already did that in the first inline IO, what do I omit? And if it is neccessary, how do we ensure the iovec wasn't freed in userspace at the reissuing time?
Quoted 31 lines
Quoted 30 lines
Currently for this panic, we can disable issuing reqs that are returned with EAGAIN error in iopoll mode when ctx is dying, but we may need to re-consider the io identity codes more.
Reported-by Abaci Robot <[email protected]>Signed-off-by Xiaoguang Wang <[email protected]>--- fs/io_uring.c | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-)fs/io_uring.c +6
-1@@ -2467,7 +2467,12 @@ static void io_iopoll_complete(struct io_ring_ctx *ctx, unsigned int *nr_events,int cflags =0 ; req = list_first_entry(done, struct io_kiocb, inflight_entry); -if (READ_ONCE (req->result) == -EAGAIN ) { +/* +* If ctx is dying, don't need to issue reqs that are returned +* with EAGAIN error, since there maybe no users to reap them. +*/ +if ((READ_ONCE (req->result) == -EAGAIN ) && + !percpu_ref_is_dying (&ctx->refs)) { req->result =0 ; req->iopoll_completed =0 ;list_move_tail (&req->inflight_entry, &again);
Quoted 8 lines · Hao Xu
Quoted 4 lines · Pavel Begunkov
On 06/02/2021 15:00, Xiaoguang Wang wrote:
Looks as you say, but the patch doesn't solve the issue completely.
1. We must not doio_queue_async_work()under a different task context, because of it potentially uses a different set of resources. So, I justHi Pavel,
I've some questions.
- Why would the resources be potentially different? My understanding is the tasks which can share a uring instance must be in the same process, so they have samecontext(files, mm etc.)
"task" and "process" are pretty synonyms in this context, as well as struct task. And they can have different files/mm, e.g. io_uring works across fork.
Quoted 3 lines
- Assume 1 is true, why don't we just do something like this:
req->work.identity=req->task->io_uring->identity; sincereq->taskpoints to the original context
Because there is more to be done to that, see grab_identity or something, and it may be racy to do. As mentioned, identity will cease to exist with Jens' patches, and in any case we can punt to task_work.
Quoted 7 lines
Quoted 6 lines
thought that it would be better to punt it to the right task context via
task_work. But...2. ...iovec import from
io_resubmit_prep()might happen after submit ends, i.e. when iovec was freed in userspace. And that's not great at all.I didn't get it why here we need to import iovec. My understanding is OPs(such as readv writev) which need imoport iovec already did that in the first inline IO, what do I omit?
Nope, it may skip copying them. e.g. see -EIOCBQUEUED path of io_read().
Quoted 1 line
And if it is neccessary, how do we ensure the iovec wasn't freed in userspace at the reissuing time?
We should not import_iovec() for reissue after we left submit, and that's exactly the problem happening with IOPOLL.
For __io_complete_rw(), Jens tells that it returns -EAGAIN IFF it called the callback from the submission, correct me if I'm wrong. I have never checked it myself, though
Signature · 1 line
Pavel Begunkov
hi,
Quoted 36 lines
Abaci Robot reported following panic:
------------[ cut here ]------------ refcount_t: underflow; use-after-free. WARNING: CPU: 1 PID: 195 at lib/refcount.c:28 refcount_warn_saturate+0x137/0x140 Modules linked in: CPU: 1 PID: 195 Comm: kworker/u4:2 Not tainted 5.11.0-rc3+ #70 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.11.1-0-g0551a4be2c-prebuilt.qemu-project.or4 Workqueue: events_unbound io_ring_exit_work RIP: 0010:refcount_warn_saturate+0x137/0x140 Code: 05 ad 63 49 08 01 e8 45 0f 6f 00 0f 0b e9 16 ff ff ff e8 4c ba ae ff 48 c7 c7 28 2e 7c 82 c6 05 90 63 40 RSP: 0018:ffffc900002e3cc8 EFLAGS: 00010282 RAX: 0000000000000000 RBX: 0000000000000003 RCX: 0000000000000000 RDX: ffff888102918000 RSI: ffffffff81150a34 RDI: ffff88813bd28570 RBP: ffff8881075cd348 R08: 0000000000000001 R09: 0000000000000001 R10: 0000000000000001 R11: 0000000000080000 R12: ffff8881075cd308 R13: ffff8881075cd348 R14: ffff888122d33ab8 R15: ffff888104780300 FS: 0000000000000000(0000) GS:ffff88813bd00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000108 CR3: 0000000107636005 CR4: 0000000000060ee0 Call Trace: io_dismantle_req+0x3f3/0x5b0 __io_free_req+0x2c/0x270 io_put_req+0x4c/0x70 io_wq_cancel_cb+0x171/0x470 ? io_match_task.part.0+0x80/0x80 __io_uring_cancel_task_requests+0xa0/0x190 io_ring_exit_work+0x32/0x3e0 process_one_work+0x2f3/0x720 worker_thread+0x5a/0x4b0 ? process_one_work+0x720/0x720 kthread+0x138/0x180 ? kthread_park+0xd0/0xd0 ret_from_fork+0x1f/0x30Later system will panic for some memory corruption.
Quoted 9 lines
The io_identity's count is underflowed. It's because in
io_put_identity, first argument tctx comes fromreq->task->io_uring, the second argument comes from the task context that callsio_req_init_async, so the compare inio_put_identitymaybe meaningless. See below case:
task context A issue one polled req, thenreq->task= A.
task context B do iopoll, above req returns with EAGAIN error. task context B re-issue req, callio_queue_async_workfor req.req->task->io_uringwill set to task context B's identity, or cow new one.
then for above case, inio_put_identity(), the compare is meaningless.
Jens, can your patch solve this issue when ctx is not dying.
Regards,
Xiaoguang Wang
Quoted 35 lines
IIUC,
req->taskshould indicates the initial task context that issues req, then if it gets EAGAIN error, we'll callio_prep_async_work()inreq->taskcontext, but iopoll reqs seems special, they maybe issued successfully and got re-issued in other task context because of EAGAIN error.Currently for this panic, we can disable issuing reqs that are returned with EAGAIN error in iopoll mode when ctx is dying, but we may need to re-consider the io identity codes more.
Reported-by Abaci Robot <[email protected]>Signed-off-by Xiaoguang Wang <[email protected]>--- fs/io_uring.c | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-)fs/io_uring.c +6
-1@@ -2467,7 +2467,12 @@ static void io_iopoll_complete(struct io_ring_ctx *ctx, unsigned int *nr_events,int cflags =0 ; req = list_first_entry(done, struct io_kiocb, inflight_entry); -if (READ_ONCE (req->result) == -EAGAIN ) { +/* +* If ctx is dying, don't need to issue reqs that are returned +* with EAGAIN error, since there maybe no users to reap them. +*/ +if ((READ_ONCE (req->result) == -EAGAIN ) && + !percpu_ref_is_dying (&ctx->refs)) { req->result =0 ; req->iopoll_completed =0 ;list_move_tail (&req->inflight_entry, &again);