mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: Dominic Chen <d.c.ddcc@gmail.com>
Cc: fweimer@redhat.com, musl@lists.openwall.com
Subject: Re: [musl] Incorrect thread TID caching
Date: Wed, 17 Feb 2021 16:07:54 -0500	[thread overview]
Message-ID: <20210217210748.GL11590@brightrain.aerifal.cx> (raw)
In-Reply-To: <20210217201156.GK11590@brightrain.aerifal.cx>

[-- Attachment #1: Type: text/plain, Size: 1586 bytes --]

On Wed, Feb 17, 2021 at 03:11:57PM -0500, Rich Felker wrote:
> On Wed, Feb 17, 2021 at 02:49:45PM -0500, Dominic Chen wrote:
> > On 2/15/2021 11:56 AM, Rich Felker wrote:
> > >Following up on this now, the code in _Fork is something I really
> > >don't want to duplicate for clone() for risk of forgetting there's a
> > >copy in the latter and letting it bitrot there. I'd rather refactor
> > >things so the same logic can be shared...
> > 
> > Thanks for the update. Can you use something like
> > __attribute__((always_inline)) to just write the logic once but
> > force it to be inlined into both library functions?
> 
> Whether it's inlined isn't really a big deal; this is not a hot path.
> It's more just a matter of how it needs to be split up at the source
> level, and it seems to be messy whichever way we choose.
> 
> Trying to avoid calling __clone doesn't seem like such a good idea,
> since the child has to run on a new stack -- if we did avoid it we'd
> need a new way to switch stacks. The generic __unmapself has a hack
> to do this already that we could reuse without needing new
> arch-specific glue though.
> 
> I'll keep trying things and see if I come up with something not too
> unreasonable.

Attached is a draft of how clone() *could* work without refactoring
the pre/post logic from _Fork to use __clone. I don't particularly
like it, and CRTJMP abuse like this (which __unmapself also does, as
noted above) is not valid for FDPIC archs (it actually expects a code
address not a function pointer). I'll try a version the other way and
see how it looks.

Rich

[-- Attachment #2: clone_forklike.diff --]
[-- Type: text/plain, Size: 1357 bytes --]

diff --git a/src/linux/clone.c b/src/linux/clone.c
index 8c1af7d3..32d53a8f 100644
--- a/src/linux/clone.c
+++ b/src/linux/clone.c
@@ -4,6 +4,25 @@
 #include <sched.h>
 #include "pthread_impl.h"
 #include "syscall.h"
+#include "dynlink.h"
+
+extern int _Forklike(int (*)(void *), void *);
+
+struct clone_args {
+	int flags;
+	pid_t *ptid, *ctid;
+};
+
+static int do_clone(void *p)
+{
+	struct clone_args *args = p;
+	int mask = CLONE_PARENT_SETTID | CLONE_CHILD_SETTID | CLONE_CHILD_CLEARTID;
+	int r = __syscall(SYS_clone, args->flags & ~mask, 0);
+	if (r>0 && (args->flags & CLONE_PARENT_SETTID)) *args->ptid = r;
+	if (!r && (args->flags & CLONE_CHILD_SETTID)) *args->ctid = __syscall(SYS_gettid);
+	if (!r && (args->flags & CLONE_CHILD_CLEARTID)) __syscall(SYS_set_tid_address, args->ctid);
+	return r;
+}
 
 int clone(int (*func)(void *), void *stack, int flags, void *arg, ...)
 {
@@ -17,5 +36,13 @@ int clone(int (*func)(void *), void *stack, int flags, void *arg, ...)
 	ctid = va_arg(ap, pid_t *);
 	va_end(ap);
 
+	if (!(flags & CLONE_VM)) {
+		struct clone_args args = { .flags = flags, .ptid = ptid, .ctid = ctid };
+		if (flags & CLONE_THREAD) return __syscall_ret(-EINVAL);
+		int r = _Forklike(do_clone, &args);
+		if (r) return r;
+		CRTJMP(func, stack);
+	}
+
 	return __syscall_ret(__clone(func, stack, flags, arg, ptid, tls, ctid));
 }

  reply	other threads:[~2021-02-17 21:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-03  4:04 Dominic Chen
2021-02-03  7:16 ` Florian Weimer
2021-02-03 19:21 ` Rich Felker
2021-02-03 20:21   ` Dominic Chen
2021-02-03 21:01     ` Rich Felker
2021-02-03 22:30       ` Dominic Chen
2021-02-03 22:55         ` Rich Felker
2021-02-15 16:56           ` Rich Felker
2021-02-17 19:49             ` Dominic Chen
2021-02-17 20:11               ` Rich Felker
2021-02-17 21:07                 ` Rich Felker [this message]
2021-03-12 21:14                   ` Dominic Chen
2021-02-04  3:28     ` Carlos O'Donell
2021-02-04  4:22       ` Dominic Chen
2021-02-04 16:15         ` Rich Felker

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 \
    --in-reply-to=20210217210748.GL11590@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --cc=d.c.ddcc@gmail.com \
    --cc=fweimer@redhat.com \
    --cc=musl@lists.openwall.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).