diff options
author | 2021-12-10 08:29:30 -0700 | |
---|---|---|
committer | 2021-12-10 13:56:28 -0700 | |
commit | 71a85387546e50b1a37b0fa45dadcae3bfb35cf6 (patch) | |
tree | 918a16d83d31a2ba20e5648a45611385f362b73e /tools/perf/util/scripting-engines/trace-event-python.c | |
parent | io_uring: ensure task_work gets run as part of cancelations (diff) | |
download | wireguard-linux-71a85387546e50b1a37b0fa45dadcae3bfb35cf6.tar.xz wireguard-linux-71a85387546e50b1a37b0fa45dadcae3bfb35cf6.zip |
io-wq: check for wq exit after adding new worker task_work
We check IO_WQ_BIT_EXIT before attempting to create a new worker, and
wq exit cancels pending work if we have any. But it's possible to have
a race between the two, where creation checks exit finding it not set,
but we're in the process of exiting. The exit side will cancel pending
creation task_work, but there's a gap where we add task_work after we've
canceled existing creations at exit time.
Fix this by checking the EXIT bit post adding the creation task_work.
If it's set, run the same cancelation that exit does.
Reported-and-tested-by: syzbot+b60c982cb0efc5e05a47@syzkaller.appspotmail.com
Reviewed-by: Hao Xu <haoxu@linux.alibaba.com>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions