From: Mikulas Patocka <mpatocka@redhat.com>
To: Dmitry Safonov <dsafonov@virtuozzo.com>
Cc: 0x7f454c46@gmail.com, oleg@redhat.com, linux-mm@kvack.org,
gorcunov@openvz.org, xemul@virtuozzo.com,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org
Subject: x32 is broken in 4.9-rc1 due to "x86/signal: Add SA_{X32,IA32}_ABI sa_flags"
Date: Wed, 19 Oct 2016 13:19:01 -0400 (EDT) [thread overview]
Message-ID: <alpine.LRH.2.02.1610191311010.24555@file01.intranet.prod.int.rdu2.redhat.com> (raw)
[-- Attachment #1: Type: TEXT/PLAIN, Size: 995 bytes --]
Hi
In the kernel 4.9-rc1, the x32 support is seriously broken, a x32 process
is killed with SIGKILL after returning from any signal handler.
I use Debian sid x64-64 distribution with x32 architecture added from
debian-ports.
I bisected the bug and found out that it is caused by the patch
6846351052e685c2d1428e80ead2d7ca3d7ed913 ("x86/signal: Add
SA_{X32,IA32}_ABI sa_flags").
example (strace of a process after receiving the SIGWINCH signal):
epoll_wait(10, 0xef6890, 32, -1) = -1 EINTR (Interrupted system call)
--- SIGWINCH {si_signo=SIGWINCH, si_code=SI_USER, si_pid=1772, si_uid=0} ---
poll([{fd=4, events=POLLOUT}], 1, 0) = 1 ([{fd=4, revents=POLLOUT}])
write(4, "\0", 1) = 1
rt_sigreturn({mask=[INT QUIT ILL TRAP BUS KILL SEGV USR2 PIPE ALRM STKFLT TSTP TTOU URG XCPU XFSZ VTALRM IO PWR SYS RTMIN]}) = 0
--- SIGSEGV {si_signo=SIGSEGV, si_code=SI_KERNEL, si_addr=NULL} ---
+++ killed by SIGSEGV +++
Neopravniny poistup do pamiti (SIGSEGV)
Mikulas
next reply other threads:[~2016-10-19 17:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-19 17:19 Mikulas Patocka [this message]
2016-10-19 17:33 ` Mikulas Patocka
2016-10-19 17:45 ` Dmitry Safonov
2016-10-19 22:02 ` Dmitry Safonov
2016-10-20 3:13 ` Adam Borowski
2016-10-20 9:24 ` Thomas Gleixner
2016-10-20 11:00 ` Dmitry Safonov
2016-10-20 15:22 ` Mikulas Patocka
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=alpine.LRH.2.02.1610191311010.24555@file01.intranet.prod.int.rdu2.redhat.com \
--to=mpatocka@redhat.com \
--cc=0x7f454c46@gmail.com \
--cc=dsafonov@virtuozzo.com \
--cc=gorcunov@openvz.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=oleg@redhat.com \
--cc=tglx@linutronix.de \
--cc=xemul@virtuozzo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox