2:24 a.m.
https://bugzilla.redhat.com/show_bug.cgi?id=1087720
Bug ID: 1087720
Summary: signal 27 (SIGPROF) not passed to container using
--sig-proxy
Product: Fedora
Version: 20
Component: docker-io
Assignee: lsm5(a)redhat.com
Reporter: ldoktor(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org,
lsm5(a)redhat.com, mattdm(a)redhat.com,
mgoldman(a)redhat.com, skottler(a)redhat.com,
vbatts(a)redhat.com
Description of problem:
When I send signal 27 to the docker process, which is running with
--sig-proxy=true, it's not forwarded. Other signals are...
Version-Release number of selected component (if applicable):
docker-io-0.9.1-1.fc21.x86_64
How reproducible:
always
Steps to Reproduce:
1. /usr/bin/docker -D run --tty=false --rm -i --name test_eoly
localhost:5000/ldoktor/fedora:latest bash -c 'for NUM in `seq 1 64`; do trap
"echo Received $NUM, ignoring..." $NUM; done; while :; do sleep 1; done'
2. ps ax |grep docker
3. kill -27 $PID
Actual results:
nothing
Expected results:
Received 27, ignoring...
Additional info:
When you send any other signal (apart from 19 or 9) it works fine.
--
You are receiving this mail because:
You are on the CC list for the bug.
3:59 a.m.
New subject: [Bug 1087720] signal 27 (SIGPROF) not passed to container using --sig-proxy
https://bugzilla.redhat.com/show_bug.cgi?id=1087720
--- Comment #1 from Lukas Doktor <ldoktor(a)redhat.com> ---
The signal 17 is also ignored.
--
You are receiving this mail because:
You are on the CC list for the bug.
2:48 a.m.
New subject: [Bug 1087720] signal 27 (SIGPROF) not passed to container using --sig-proxy
https://bugzilla.redhat.com/show_bug.cgi?id=1087720
--- Comment #2 from Lukas Doktor <ldoktor(a)redhat.com> ---
The same bug is in upstream Docker version 0.10.0, build dc9c28f/0.10.0
--
You are receiving this mail because:
You are on the CC list for the bug.
9:55 a.m.
New subject: [Bug 1087720] signal 27 (SIGPROF) not passed to container using --sig-proxy
https://bugzilla.redhat.com/show_bug.cgi?id=1087720
Lukas Doktor <ldoktor(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Blocks| |1096276
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1096276
[Bug 1096276] signal 27 (SIGPROF) not passed to container using --sig-proxy
--
You are receiving this mail because:
You are on the CC list for the bug.
3:35 p.m.
New subject: [Bug 1087720] signal 27 (SIGPROF) not passed to container using --sig-proxy
https://bugzilla.redhat.com/show_bug.cgi?id=1087720
Daniel Walsh <dwalsh(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dwalsh(a)redhat.com
--- Comment #3 from Daniel Walsh <dwalsh(a)redhat.com> ---
We are keeping all of the versions of docker insync, please only report these
bugs once.
--
You are receiving this mail because:
You are on the CC list for the bug.
11:40 a.m.
New subject: [Bug 1087720] signal 27 (SIGPROF) not passed to container using --sig-proxy
https://bugzilla.redhat.com/show_bug.cgi?id=1087720
Daniel Walsh <dwalsh(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|lsm5(a)redhat.com |whenry(a)redhat.com
--
You are receiving this mail because:
You are on the CC list for the bug.
2:26 p.m.
New subject: [Bug 1087720] signal 27 (SIGPROF) not passed to container using --sig-proxy
https://bugzilla.redhat.com/show_bug.cgi?id=1087720
Daniel Walsh <dwalsh(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|whenry(a)redhat.com |mheon(a)redhat.com
--
You are receiving this mail because:
You are on the CC list for the bug.
3:27 p.m.
New subject: [Bug 1087720] signal 27 (SIGPROF) not passed to container using --sig-proxy
https://bugzilla.redhat.com/show_bug.cgi?id=1087720
--- Comment #4 from Matthew Heon <mheon(a)redhat.com> ---
With upstream Docker, signal 27 works. Signal 17, however, is still broken.
--
You are receiving this mail because:
You are on the CC list for the bug.
8:09 a.m.
New subject: [Bug 1087720] signal 27 (SIGPROF) not passed to container using --sig-proxy
https://bugzilla.redhat.com/show_bug.cgi?id=1087720
--- Comment #5 from Matthew Heon <mheon(a)redhat.com> ---
After further testing, I've determined that all signals are sent correctly
except 17 and 19. I'm looking into a fix for this.
--
You are receiving this mail because:
You are on the CC list for the bug.
2:23 p.m.
New subject: [Bug 1087720] signal 27 (SIGPROF) not passed to container using --sig-proxy
https://bugzilla.redhat.com/show_bug.cgi?id=1087720
--- Comment #6 from Matthew Heon <mheon(a)redhat.com> ---
Signal 17, SIGCHILD, is deliberately not forwarded - upstream commit
https://github.com/dotcloud/docker/commit/440422a96346072a0a9016c4db78ff7....
Signal 19 might actually be a Golang bug - I've constructed a small test
program in Go which also fails to catch this. Looking into this further.
--
You are receiving this mail because:
You are on the CC list for the bug.
3:23 p.m.
New subject: [Bug 1087720] signal 27 (SIGPROF) not passed to container using --sig-proxy
https://bugzilla.redhat.com/show_bug.cgi?id=1087720
Daniel Walsh <dwalsh(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
--- Comment #7 from Daniel Walsh <dwalsh(a)redhat.com> ---
I think we should just document, ignoring sigchld makes sense.
We should document in the man page that signal 17 should be ignored, and signal
19 is a bug in golang.
Just fix the man page.
--
You are receiving this mail because:
You are on the CC list for the bug.
9:45 a.m.
New subject: [Bug 1087720] signal 27 (SIGPROF) not passed to container using --sig-proxy
https://bugzilla.redhat.com/show_bug.cgi?id=1087720
--- Comment #8 from Matthew Heon <mheon(a)redhat.com> ---
PR out: https://github.com/dotcloud/docker/pull/6544
It appears that Signal 19 is actually forwarded, also. SIGSTOP cannot be
caught, so it was actually preventing my script from printing out that it was
received. So it's only Signal 17 that's not forwarded.
--
You are receiving this mail because:
You are on the CC list for the bug.
11:59 a.m.
New subject: [Bug 1087720] signal 27 (SIGPROF) not passed to container using --sig-proxy
https://bugzilla.redhat.com/show_bug.cgi?id=1087720
--- Comment #10 from Matthew Heon <mheon(a)redhat.com> ---
After further testing, I've managed to reproduce being unable to send signals
19, 18, and 27 to the container via --sig-proxy.
This seems to be a Golang issue. I implemented a trivial signal-catching test
program in Go and tested it with signals 1-31, and obtained identical results
to Docker aside from Signal 17 (discarded on Docker, caught by my test
program).
A brief summary of signals Docker does not play well with:
- Signal 17, SIGCHLD, deliberately caught and discarded. Makes no sense to pass
this into a container.
- Signal 18, SIGCONT, seems to be Golang issue
- Signal 19, SIGSTOP, unmaskable signal - cannot be caught
- Signal 27, SIGPROF, seems to be Golang issue
Worth noting that the "docker kill" command should be able to send any of these
without issue. If we have any general docs for Docker, we may want to recommend
avoiding proxying signals in favor of docker kill whenever possible.
--
You are receiving this mail because:
You are on the CC list for the bug.
9:09 a.m.
New subject: [Bug 1087720] signal 27 (SIGPROF) not passed to container using --sig-proxy
https://bugzilla.redhat.com/show_bug.cgi?id=1087720
--- Comment #11 from Matthew Heon <mheon(a)redhat.com> ---
Appears to be an issue with Golang proper
(https://code.google.com/p/go/issues/detail?id=4391&q=signal&colsp...)
Unknown when a fix will be released - there hasn't been any movement on the bug
since February.
--
You are receiving this mail because:
You are on the CC list for the bug.
3:53 p.m.
New subject: [Bug 1087720] signal 27 (SIGPROF) not passed to container using --sig-proxy
https://bugzilla.redhat.com/show_bug.cgi?id=1087720
John Skeoch <jskeoch(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|mheon(a)redhat.com |jrieden(a)redhat.com
--
You are receiving this mail because:
You are on the CC list for the bug.
7:20 a.m.
New subject: [Bug 1087720] signal 27 (SIGPROF) not passed to container using --sig-proxy
https://bugzilla.redhat.com/show_bug.cgi?id=1087720
Daniel Walsh <dwalsh(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|jrieden(a)redhat.com |dwalsh(a)redhat.com
--
You are receiving this mail because:
You are on the CC list for the bug.
8:38 a.m.
New subject: [Bug 1087720] signal 27 (SIGPROF) not passed to container using --sig-proxy
https://bugzilla.redhat.com/show_bug.cgi?id=1087720
Daniel Walsh <dwalsh(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|dwalsh(a)redhat.com |mheon(a)redhat.com
--
You are receiving this mail because:
You are on the CC list for the bug.
7:16 a.m.
New subject: [Bug 1087720] signal 27 (SIGPROF) not passed to container using --sig-proxy
https://bugzilla.redhat.com/show_bug.cgi?id=1087720
Daniel Walsh <dwalsh(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |CLOSED
Resolution|--- |CANTFIX
Last Closed| |2015-04-15 08:16:44
--- Comment #13 from Daniel Walsh <dwalsh(a)redhat.com> ---
Bug is in golang, have to wait until golang is fixed handling of signals.
--
You are receiving this mail because:
You are on the CC list for the bug.
3292
days inactive
3657
days old
golang@lists.fedoraproject.org
17 comments
1 participants
participants (1)
-
Red Hat Bugzilla