[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug 1907969] Re: linux-user/i386: Segfault when mixing threads and sign
From: |
Thomas Huth |
Subject: |
[Bug 1907969] Re: linux-user/i386: Segfault when mixing threads and signals |
Date: |
Wed, 12 May 2021 15:16:52 -0000 |
The QEMU project is currently moving its bug tracking to another system.
For this we need to know which bugs are still valid and which could be
closed already. Thus we are setting the bug state to "Incomplete" now.
If the bug has already been fixed in the latest upstream version of QEMU,
then please close this ticket as "Fix released".
If it is not fixed yet and you think that this bug report here is still
valid, then you have two options:
1) If you already have an account on gitlab.com, please open a new ticket
for this problem in our new tracker here:
https://gitlab.com/qemu-project/qemu/-/issues
and then close this ticket here on Launchpad (or let it expire auto-
matically after 60 days). Please mention the URL of this bug ticket on
Launchpad in the new ticket on GitLab.
2) If you don't have an account on gitlab.com and don't intend to get
one, but still would like to keep this ticket opened, then please switch
the state back to "New" or "Confirmed" within the next 60 days (other-
wise it will get closed as "Expired"). We will then eventually migrate
the ticket automatically to the new system (but you won't be the reporter
of the bug in the new system and thus you won't get notified on changes
anymore).
Thank you and sorry for the inconvenience.
** Tags added: i386 linux-user
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1907969
Title:
linux-user/i386: Segfault when mixing threads and signals
Status in QEMU:
Incomplete
Bug description:
Given the following C program, qemu-i386 will surely and certainly segfault
when executing it.
The problem is only noticeable if the program is statically linked to musl's
libc and, as written
in the title, it only manifests when targeting i386.
Removing the pthread calls or the second raise() makes it not
segfault.
The crash is in some part of the TCG-generated code, right when it tries to
perform a
%gs-relative access.
If you want a quick way of cross-compiling this binary:
* Download a copy of the Zig compiler from https://ziglang.org/download/
* Compile it with
`zig cc -target i386-linux-musl <C-FILE> -o <OUT>`
```
#include <pthread.h>
#include <signal.h>
#include <stdio.h>
#include <string.h>
#include <sys/types.h>
#include <unistd.h>
#include <asm/prctl.h>
#include <sys/syscall.h>
void sig_func(int sig)
{
write(1, "hi!\n", strlen("hi!\n"));
}
void func(void *p) { }
typedef void *(*F)(void *);
int main()
{
pthread_t tid;
struct sigaction action;
action.sa_flags = 0;
action.sa_handler = sig_func;
if (sigaction(SIGUSR1, &action, NULL) == -1) {
return 1;
}
// This works.
raise(SIGUSR1);
pthread_create(&tid, NULL, (F)func, NULL);
pthread_join(tid, NULL);
// This makes qemu segfault.
raise(SIGUSR1);
}
```
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1907969/+subscriptions
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Bug 1907969] Re: linux-user/i386: Segfault when mixing threads and signals,
Thomas Huth <=