golang April 2016

golang@lists.fedoraproject.org

7 participants
217 discussions

Broken dependencies: golang-github-kraman-libcontainer
by Fedora Koji Build System 06 Apr '16

06 Apr '16

golang-github-kraman-libcontainer has broken dependencies in the rawhide tree: On x86_64: golang-github-kraman-libcontainer-devel-0-0.7.gitd700e5b.fc24.noarch requires golang(github.com/docker/docker/pkg/netlink) On i386: golang-github-kraman-libcontainer-devel-0-0.7.gitd700e5b.fc24.noarch requires golang(github.com/docker/docker/pkg/netlink) On armhfp: golang-github-kraman-libcontainer-devel-0-0.7.gitd700e5b.fc24.noarch requires golang(github.com/docker/docker/pkg/netlink) Please resolve this as soon as possible.

1 0

Broken dependencies: golang-github-samalba-dockerclient
by Fedora Koji Build System 06 Apr '16

06 Apr '16

golang-github-samalba-dockerclient has broken dependencies in the rawhide tree: On x86_64: golang-github-samalba-dockerclient-devel-0-0.3.gitc37a52f.fc24.noarch requires golang(github.com/docker/docker/pkg/timeutils) On i386: golang-github-samalba-dockerclient-devel-0-0.3.gitc37a52f.fc24.noarch requires golang(github.com/docker/docker/pkg/timeutils) On armhfp: golang-github-samalba-dockerclient-devel-0-0.3.gitc37a52f.fc24.noarch requires golang(github.com/docker/docker/pkg/timeutils) Please resolve this as soon as possible.

1 0

Broken dependencies: cadvisor
by Fedora Koji Build System 06 Apr '16

06 Apr '16

cadvisor has broken dependencies in the rawhide tree: On x86_64: cadvisor-devel-0.16.0.2-1.fc24.noarch requires golang(github.com/docker/docker/pkg/units) Please resolve this as soon as possible.

1 0

[Bug 1324343] CVE-2016-3959 golang: infinite loop in several big integer routines
by Red Hat Bugzilla 06 Apr '16

06 Apr '16

1 0

[Bug 1324343] CVE-2016-3959 golang: infinite loop in several big integer routines
by Red Hat Bugzilla 06 Apr '16

06 Apr '16

https://bugzilla.redhat.com/show_bug.cgi?id=1324343 Andrej Nemec <anemec(a)redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends On| |1324344 Depends On| |1324345 --- Comment #1 from Andrej Nemec <anemec(a)redhat.com> --- Created golang tracking bugs for this issue: Affects: fedora-all [bug 1324344] Affects: epel-6 [bug 1324345] Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1324344 [Bug 1324344] CVE-2016-3959 golang: infinite loop in several big integer routines [fedora-all] https://bugzilla.redhat.com/show_bug.cgi?id=1324345 [Bug 1324345] CVE-2016-3959 golang: infinite loop in several big integer routines [epel-6] -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1324345] New: CVE-2016-3959 golang: infinite loop in several big integer routines [epel-6]
by Red Hat Bugzilla 06 Apr '16

06 Apr '16

https://bugzilla.redhat.com/show_bug.cgi?id=1324345 Bug ID: 1324345 Summary: CVE-2016-3959 golang: infinite loop in several big integer routines [epel-6] Product: Fedora EPEL Version: el6 Component: golang Keywords: Security, SecurityTracking Severity: medium Priority: medium Assignee: admiller(a)redhat.com Reporter: anemec(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: admiller(a)redhat.com, amurdaca(a)redhat.com, golang(a)lists.fedoraproject.org, jcajka(a)redhat.com, s(a)shk.io Blocks: 1324343 (CVE-2016-3959) This is an automatically created tracking bug! It was created to ensure that one or more security vulnerabilities are fixed in affected versions of Fedora EPEL. For comments that are specific to the vulnerability please use bugs filed against the "Security Response" product referenced in the "Blocks" field. For more information see: http://fedoraproject.org/wiki/Security/TrackingBugs When submitting as an update, use the fedpkg template provided in the next comment(s). This will include the bug IDs of this tracking bug as well as the relevant top-level CVE bugs. Please also mention the CVE IDs being fixed in the RPM changelog and the fedpkg commit message. [bug automatically created by: add-tracking-bugs] Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1324343 [Bug 1324343] CVE-2016-3959 golang: infinite loop in several big integer routines -- You are receiving this mail because: You are on the CC list for the bug.

1 1

Broken dependencies: golang-github-kraman-libcontainer
by Fedora Koji Build System 05 Apr '16

05 Apr '16

1 0

Broken dependencies: golang-github-samalba-dockerclient
by Fedora Koji Build System 05 Apr '16

05 Apr '16

1 0

Broken dependencies: cadvisor
by Fedora Koji Build System 05 Apr '16

05 Apr '16

cadvisor has broken dependencies in the rawhide tree: On x86_64: cadvisor-devel-0.16.0.2-1.fc24.noarch requires golang(github.com/docker/docker/pkg/units) Please resolve this as soon as possible.

1 0

[Bug 1096273] New: repetition of signal 21 with --sig-proxy and SIGSTOP of docker
by Red Hat Bugzilla 05 Apr '16

05 Apr '16

https://bugzilla.redhat.com/show_bug.cgi?id=1096273 Bug ID: 1096273 Summary: repetition of signal 21 with --sig-proxy and SIGSTOP of docker Product: Red Hat Enterprise Linux 7 Version: 7.1 Component: docker Severity: low 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: 1087704 +++ This bug was initially created as a clone of Bug #1087704 +++ Description of problem: I noticed weird reaction to SIGSTOP signal. When you start container with --sig-proxy, ignore all signals in container and from OS use kill -SIGSTOP to the `docker run` process, it's put into background. (so far correct behavior) Than when you use kill -SIGCONT, it's resumed (still in background) and it's continuing to send signal 21 to the container (100% CPU utilization). This disappears once you attach the process with fg. 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. kill -SIGSTOP $PID 4. kill -SIGCONT $PID Actual results: [1]+ Pozastavena /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' [root@t530 ~]# Received 21, ignoring... Received 21, ignoring... Received 21, ignoring... Received 21, ignoring... Received 21, ignoring... Received 21, ignoring... ... (100% CPU utilization, when you use fg it stops and you can use the container again...) Expected results: [1]+ Pozastavena /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' [root@t530 ~]# Received 21, ignoring... Additional info: I'm not definitely sure if this is really required as it's not a common usage. But as there is no way to detach the process apart from kill -SIGSTOP people might use it and get to this problem... --- Additional comment from Lukas Doktor on 2014-05-05 03:59:30 EDT --- I retested this with the upstream dc9c28f/0.10.0 with the same results. The daemon output is: ... [/home/medic/Work/Projekty/Docker/root|fa3816b6] -job kill(b01a849cb45ebe94c3a61fa021a5464186345d5b159faee4ea9d5da39fb36de5, TTIN) = OK (0) 2014/05/05 09:58:13 POST /v1.10/containers/b01a849cb45ebe94c3a61fa021a5464186345d5b159faee4ea9d5da39fb36de5/kill?signal=TTIN [/home/medic/Work/Projekty/Docker/root|fa3816b6] +job kill(b01a849cb45ebe94c3a61fa021a5464186345d5b159faee4ea9d5da39fb36de5, TTIN) [/home/medic/Work/Projekty/Docker/root|fa3816b6] -job kill(b01a849cb45ebe94c3a61fa021a5464186345d5b159faee4ea9d5da39fb36de5, TTIN) = OK (0) 2014/05/05 09:58:13 POST /v1.10/containers/b01a849cb45ebe94c3a61fa021a5464186345d5b159faee4ea9d5da39fb36de5/kill?signal=TTIN [/home/medic/Work/Projekty/Docker/root|fa3816b6] +job kill(b01a849cb45ebe94c3a61fa021a5464186345d5b159faee4ea9d5da39fb36de5, TTIN) [/home/medic/Work/Projekty/Docker/root|fa3816b6] -job kill(b01a849cb45ebe94c3a61fa021a5464186345d5b159faee4ea9d5da39fb36de5, TTIN) = OK (0) 2014/05/05 09:58:13 POST /v1.10/containers/b01a849cb45ebe94c3a61fa021a5464186345d5b159faee4ea9d5da39fb36de5/kill?signal=TTIN [/home/medic/Work/Projekty/Docker/root|fa3816b6] +job kill(b01a849cb45ebe94c3a61fa021a5464186345d5b159faee4ea9d5da39fb36de5, TTIN) ... Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1087704 [Bug 1087704] repetition of signal 21 with --sig-proxy and SIGSTOP of docker -- You are receiving this mail because: You are on the CC list for the bug.

1 25

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

golang April 2016