From: Stefan Metzmacher <[email protected]>
To: Linus Torvalds <[email protected]>
Cc: Stefan Metzmacher <[email protected]>, Jens Axboe <[email protected]>,
[email protected], [email protected]
Subject: [PATCH] io_thread/x86: don't reset 'cs', 'ss', 'ds' and 'es' registers for io_threads
Date: Sun, 11 Apr 2021 17:27:05 +0200 [thread overview]
Message-ID: <[email protected]> (raw)
This allows gdb attach to userspace processes using io-uring,
which means that they have io_threads (PF_IO_WORKER), which appear
just like normal as userspace threads.
See the code comment for more details.
Fixes: 4727dc20e04 ("arch: setup PF_IO_WORKER threads like PF_KTHREAD")
Signed-off-by: Stefan Metzmacher <[email protected]>
cc: Linus Torvalds <[email protected]>
cc: Jens Axboe <[email protected]>
cc: [email protected]
cc: [email protected]
---
arch/x86/kernel/process.c | 49 +++++++++++++++++++++++++++++++++++++++
1 file changed, 49 insertions(+)
diff --git a/arch/x86/kernel/process.c b/arch/x86/kernel/process.c
index 9c214d7085a4..72120c4b7618 100644
--- a/arch/x86/kernel/process.c
+++ b/arch/x86/kernel/process.c
@@ -163,6 +163,55 @@ int copy_thread(unsigned long clone_flags, unsigned long sp, unsigned long arg,
/* Kernel thread ? */
if (unlikely(p->flags & (PF_KTHREAD | PF_IO_WORKER))) {
memset(childregs, 0, sizeof(struct pt_regs));
+ /*
+ * gdb sees all userspace threads,
+ * including io threads (PF_IO_WORKER)!
+ *
+ * gdb uses:
+ * PTRACE_PEEKUSR, offsetof (struct user_regs_struct, cs)
+ * returning with 0x33 (51) to detect 64 bit
+ * and:
+ * PTRACE_PEEKUSR, offsetof (struct user_regs_struct, ds)
+ * returning 0x2b (43) to detect 32 bit.
+ *
+ * GDB relies on that the kernel returns the
+ * same values for all threads, which means
+ * we don't zero these out.
+ *
+ * Note that CONFIG_X86_64 handles 'es' and 'ds'
+ * differently, see the following above:
+ * savesegment(es, p->thread.es);
+ * savesegment(ds, p->thread.ds);
+ * and the CONFIG_X86_64 version of get_segment_reg().
+ *
+ * Linus proposed something like this:
+ * (https://lore.kernel.org/io-uring/CAHk-=whEObPkZBe4766DmR46-=5QTUiatWbSOaD468eTgYc1tg@mail.gmail.com/)
+ *
+ * childregs->cs = __USER_CS;
+ * childregs->ss = __USER_DS;
+ * childregs->ds = __USER_DS;
+ * childregs->es = __USER_DS;
+ *
+ * might make sense (just do it unconditionally, rather than making it
+ * special to PF_IO_WORKER).
+ *
+ * But that doesn't make gdb happy in all cases.
+ *
+ * While 32bit userspace on a 64bit kernel is legacy,
+ * it's still useful to allow 32bit libraries or nss modules
+ * use the same code as the 64bit version of that library, which
+ * can use io-uring just fine.
+ *
+ * So we better just inherit the values from
+ * the originating process instead of hardcoding
+ * values, which would imply 64bit userspace.
+ */
+ childregs->cs = current_pt_regs()->cs;
+ childregs->ss = current_pt_regs()->ss;
+#ifdef CONFIG_X86_32
+ childregs->ds = current_pt_regs()->ds;
+ childregs->es = current_pt_regs()->es;
+#endif
kthread_frame_init(frame, sp, arg);
return 0;
}
--
2.25.1
next reply other threads:[~2021-04-11 15:27 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-11 15:27 Stefan Metzmacher [this message]
2021-04-14 21:28 ` [PATCH] io_thread/x86: don't reset 'cs', 'ss', 'ds' and 'es' registers for io_threads Stefan Metzmacher
2021-05-05 11:03 ` [PATCH v2] io_thread/x86: setup io_threads more like normal user space threads Stefan Metzmacher
2021-05-05 21:24 ` Jens Axboe
2021-05-05 21:57 ` Thomas Gleixner
2021-05-05 22:07 ` Thomas Gleixner
2021-05-05 23:49 ` Jens Axboe
2021-05-06 9:17 ` Thomas Gleixner
2021-05-05 23:35 ` Jens Axboe
[not found] <[email protected]>
2021-05-03 16:05 ` [PATCH] io_thread/x86: don't reset 'cs', 'ss', 'ds' and 'es' registers for io_threads Andy Lutomirski
2021-05-03 19:14 ` Linus Torvalds
2021-05-03 20:15 ` Andy Lutomirski
2021-05-03 20:21 ` Andy Lutomirski
2021-05-03 20:37 ` Linus Torvalds
2021-05-03 21:26 ` Jens Axboe
2021-05-03 21:49 ` Andy Lutomirski
2021-05-03 22:08 ` Linus Torvalds
2021-05-03 22:56 ` Thomas Gleixner
2021-05-03 23:15 ` Andy Lutomirski
2021-05-03 23:16 ` Linus Torvalds
2021-05-03 23:19 ` Linus Torvalds
2021-05-03 23:27 ` Stefan Metzmacher
2021-05-03 23:48 ` Linus Torvalds
2021-05-04 2:50 ` Jens Axboe
2021-05-04 11:39 ` Stefan Metzmacher
2021-05-04 15:53 ` Linus Torvalds
2021-05-12 4:24 ` Olivier Langlois
2021-05-12 17:44 ` Linus Torvalds
2021-05-12 20:55 ` Jens Axboe
2021-05-20 4:13 ` Olivier Langlois
2021-05-21 7:31 ` Olivier Langlois
2021-05-25 19:39 ` Olivier Langlois
2021-05-25 19:45 ` Olivier Langlois
2021-05-25 19:52 ` Jens Axboe
2021-05-25 20:23 ` Linus Torvalds
2021-05-04 8:22 ` David Laight
2021-05-04 0:01 ` Andy Lutomirski
2021-05-04 8:39 ` Peter Zijlstra
2021-05-04 15:35 ` Borislav Petkov
2021-05-04 15:55 ` Simon Marchi
2021-05-05 11:29 ` Stefan Metzmacher
2021-05-05 21:59 ` Simon Marchi
2021-05-05 22:11 ` Andy Lutomirski
2021-05-05 23:12 ` Borislav Petkov
2021-05-05 23:22 ` Andy Lutomirski
2021-05-06 1:04 ` Simon Marchi
2021-05-06 15:11 ` Andy Lutomirski
2021-05-06 9:47 ` David Laight
2021-05-06 9:53 ` David Laight
2021-05-05 22:21 ` Stefan Metzmacher
2021-05-05 23:15 ` Simon Marchi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox