path: root/MAINTAINERS
diff options
authorStefan Metzmacher <>2021-05-05 13:03:10 +0200
committerJens Axboe <>2021-05-05 17:47:41 -0600
commit50b7b6f29de3e18e9d6c09641256a0296361cfee (patch)
tree0f1f7e713aee5944cca46448a3da78e16aeca343 /MAINTAINERS
parenta5e7da1494e191c561ecce8829a6c19449585e3d (diff)
x86/process: setup io_threads more like normal user space threads
As io_threads are fully set up USER threads it's clearer to separate the code path from the KTHREAD logic. The only remaining difference to user space threads is that io_threads never return to user space again. Instead they loop within the given worker function. The fact that they never return to user space means they don't have an user space thread stack. In order to indicate that to tools like gdb we reset the stack and instruction pointers to 0. This allows gdb attach to user space processes using io-uring, which like means that they have io_threads, without printing worrying message like this: warning: Selected architecture i386:x86-64 is not compatible with reported target architecture i386 warning: Architecture rejected target-supplied description The output will be something like this: (gdb) info threads Id Target Id Frame * 1 LWP 4863 "io_uring-cp-for" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 2 LWP 4864 "iou-mgr-4863" 0x0000000000000000 in ?? () 3 LWP 4865 "iou-wrk-4863" 0x0000000000000000 in ?? () (gdb) thread 3 [Switching to thread 3 (LWP 4865)] #0 0x0000000000000000 in ?? () (gdb) bt #0 0x0000000000000000 in ?? () Backtrace stopped: Cannot access memory at address 0x0 Fixes: 4727dc20e042 ("arch: setup PF_IO_WORKER threads like PF_KTHREAD") Link: Signed-off-by: Stefan Metzmacher <> cc: Linus Torvalds <> cc: Jens Axboe <> cc: Andy Lutomirski <> cc: cc: cc: Link: Reviewed-by: Thomas Gleixner <> Signed-off-by: Jens Axboe <>
Diffstat (limited to 'MAINTAINERS')
0 files changed, 0 insertions, 0 deletions