[Bug 1096269] New: lost signals when sending lots of signals using --sig-proxy to docker

[Red Hat Bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1096269

            Bug ID: 1096269
           Summary: lost signals when sending lots of signals using
                    --sig-proxy to docker
           Product: Red Hat Enterprise Linux 7
           Version: 7.1
         Component: docker
          Assignee: lsm5(a)redhat.com
          Reporter: ldoktor(a)redhat.com
        QA Contact: virt-bugs(a)redhat.com
                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
        Depends On: 1087700



+++ This bug was initially created as a clone of Bug #1087700 +++

Description of problem:
When I send lots of signals to the running docker with --sig-proxy (actual kill
signals, not `docker kill`), most of them got lost.

Version-Release number of selected component (if applicable):
docker-0.10.0-8.el7.x86_64
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. for AAA in `seq 1 32`; do [ $AAA -ne 9 ] && [ $AAA -ne 20 ] && [ $AAA
-ne 19
] && kill -s $AAA $PID; done

Actual results:
Output of the docker is:
Received 1, ignoring...
Received 2, ignoring...


Expected results:
Messages for all of the `Received $NUM, ignoring...` printed (order doesn't
matter)

Additional info:
Skipping 9, 19, 20 as they are a bit too special..

--- Additional comment from Lukas Doktor on 2014-05-05 04:10:09 EDT ---

The same results with upstream docker dc9c28f/0.10.0:

Output:
Received 1, ignoring...
[debug] stdcopy.go:111 framesize: 24
Received 2, ignoring...

Daemon output:
2014/05/05 10:08:45 POST
/v1.10/containers/b01a849cb45ebe94c3a61fa021a5464186345d5b159faee4ea9d5da39fb36de5/kill?signal=HUP
[/home/medic/Work/Projekty/Docker/root|fa3816b6] +job
kill(b01a849cb45ebe94c3a61fa021a5464186345d5b159faee4ea9d5da39fb36de5, HUP)
[/home/medic/Work/Projekty/Docker/root|fa3816b6] -job
kill(b01a849cb45ebe94c3a61fa021a5464186345d5b159faee4ea9d5da39fb36de5, HUP) =
OK (0)
2014/05/05 10:08:45 POST
/v1.10/containers/b01a849cb45ebe94c3a61fa021a5464186345d5b159faee4ea9d5da39fb36de5/kill?signal=INT
[/home/medic/Work/Projekty/Docker/root|fa3816b6] +job
kill(b01a849cb45ebe94c3a61fa021a5464186345d5b159faee4ea9d5da39fb36de5, INT)
[/home/medic/Work/Projekty/Docker/root|fa3816b6] -job
kill(b01a849cb45ebe94c3a61fa021a5464186345d5b159faee4ea9d5da39fb36de5, INT) =
OK (0)


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1087700
[Bug 1087700] lost signals when sending lots of signals using --sig-proxy
to docker
-- 
You are receiving this mail because:
You are on the CC list for the bug.