From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: [PATCH] Add gettid and tgkill syscall wrappers.
Date: Fri, 2 Aug 2019 16:25:16 -0400 [thread overview]
Message-ID: <20190802202516.GI9017@brightrain.aerifal.cx> (raw)
In-Reply-To: <CAA2zVHp2CiKHap0Fdg371YCXqC5ReEL3jcr3s5TwrtbiiUM8aA@mail.gmail.com>
On Thu, Aug 01, 2019 at 04:31:11PM -0400, James Y Knight wrote:
>
> From bdb4f28edece4b81e99becf4ffcdc69449211764 Mon Sep 17 00:00:00 2001
> From: James Y Knight <jyknight@google.com>
> Date: Thu, 1 Aug 2019 12:43:08 -0400
> Subject: [PATCH] Add gettid and tgkill syscall wrappers.
>
> ---
> include/signal.h | 1 +
> include/unistd.h | 1 +
> src/linux/gettid.c | 8 ++++++++
> src/linux/tgkill.c | 8 ++++++++
> 4 files changed, 18 insertions(+)
> create mode 100644 src/linux/gettid.c
> create mode 100644 src/linux/tgkill.c
>
> diff --git a/include/signal.h b/include/signal.h
> index 5c48cb83..6843323a 100644
> --- a/include/signal.h
> +++ b/include/signal.h
> @@ -257,6 +257,7 @@ void (*bsd_signal(int, void (*)(int)))(int);
> int sigisemptyset(const sigset_t *);
> int sigorset (sigset_t *, const sigset_t *, const sigset_t *);
> int sigandset(sigset_t *, const sigset_t *, const sigset_t *);
> +int tgkill(pid_t, pid_t, int);
>
> #define SA_NOMASK SA_NODEFER
> #define SA_ONESHOT SA_RESETHAND
> diff --git a/include/unistd.h b/include/unistd.h
> index 9485da7a..4764f157 100644
> --- a/include/unistd.h
> +++ b/include/unistd.h
> @@ -188,6 +188,7 @@ char *get_current_dir_name(void);
> int syncfs(int);
> int euidaccess(const char *, int);
> int eaccess(const char *, int);
> +pid_t gettid(void);
> #endif
>
> #if defined(_LARGEFILE64_SOURCE) || defined(_GNU_SOURCE)
> diff --git a/src/linux/gettid.c b/src/linux/gettid.c
> new file mode 100644
> index 00000000..6490101d
> --- /dev/null
> +++ b/src/linux/gettid.c
> @@ -0,0 +1,8 @@
> +#define _GNU_SOURCE
> +#include <unistd.h>
> +#include "syscall.h"
> +
> +pid_t gettid(void)
> +{
> + return __syscall(SYS_gettid);
> +}
> diff --git a/src/linux/tgkill.c b/src/linux/tgkill.c
> new file mode 100644
> index 00000000..97365d58
> --- /dev/null
> +++ b/src/linux/tgkill.c
> @@ -0,0 +1,8 @@
> +#define _GNU_SOURCE
> +#include <signal.h>
> +#include "syscall.h"
> +
> +int tgkill(pid_t pid, pid_t tid, int sig)
> +{
> + return syscall(SYS_tgkill, pid, tid, sig);
> +}
> --
> 2.22.0.770.g0f2c4a37fd-goog
Is pid_t the right type for this? Fundamentally the futex interface
imposes a requirement that tids fit in 29 bits of int. pid_t *is* int
anyway, but it's more a matter of figuring out what the right semantic
type for this is.
I also question whether tgkill should be a supported API. The idea of
being able to address threads of other processes is dubious. Before we
start adding these, I think we should think about which ones make
sense as APIs that applications can safely use.
Also, pthread_gettid_np or something like that is probably important
to being able to use any interfaces involving tids; otherwise you can
only address yourself without explicit communication with a thread to
query its tid.
Is there a list of which interfaces glibc will be adding and their
rationale?
Rich
next prev parent reply other threads:[~2019-08-02 20:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-01 20:31 James Y Knight
2019-08-02 20:25 ` Rich Felker [this message]
2019-08-02 21:46 ` Szabolcs Nagy
2019-08-07 16:16 ` Florian Weimer
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=20190802202516.GI9017@brightrain.aerifal.cx \
--to=dalias@libc.org \
--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).