github.com/cloudflare/tableflip
View on Github
Activity
- Latest release
- 4y ago
- Total releases
- 6
- Cadence
- ~9 months
- Last 12 months
- 0
Reach
- Stars
- —
Details
- First release
- Jul 16, 2019
| Version | Released | |
|---|---|---|
v1.2.3
patch
|
v1.2.3
patch
Dependencies (1)
|
|
v1.2.2
patch
|
v1.2.2
patch
Dependencies (1)
|
|
v1.2.1
patch
1 CVE
GHSA-gmq2-39ff-f5qg
May 21, 2021
A failed upgrade may lead to hung goroutines
Low
ImpactProcesses using tableflip may encounter hung goroutines in the parent process, after a failed upgrade. The Go runtime has annoying behaviour around setting and clearing O_NONBLOCK: exec.Cmd.Start() ends up calling os.File.Fd() for any file in exec.Cmd.ExtraFiles. os.File.Fd() disables both the use of the runtime poller for the file and clears O_NONBLOCK from the underlying open file descriptor. This can lead to goroutines hanging in a parent process, after at least one failed upgrade. The bug manifests in goroutines which rely on either a deadline or interruption via Close() to be unblocked being stuck in read or accept like syscalls. As far as I can tell we've not experienced this problem in production, so it's most likely quite rare. PatchesThe problem has been fixed in v1.2.2. WorkaroundsNone. References
Fixed in
1.2.2
References Updated May 21, 2021 · Source: OSV.dev |
v1.2.1
patch
Dependencies (1)
|
|
v1.2.0
minor
1 CVE
GHSA-gmq2-39ff-f5qg
May 21, 2021
A failed upgrade may lead to hung goroutines
Low
ImpactProcesses using tableflip may encounter hung goroutines in the parent process, after a failed upgrade. The Go runtime has annoying behaviour around setting and clearing O_NONBLOCK: exec.Cmd.Start() ends up calling os.File.Fd() for any file in exec.Cmd.ExtraFiles. os.File.Fd() disables both the use of the runtime poller for the file and clears O_NONBLOCK from the underlying open file descriptor. This can lead to goroutines hanging in a parent process, after at least one failed upgrade. The bug manifests in goroutines which rely on either a deadline or interruption via Close() to be unblocked being stuck in read or accept like syscalls. As far as I can tell we've not experienced this problem in production, so it's most likely quite rare. PatchesThe problem has been fixed in v1.2.2. WorkaroundsNone. References
Fixed in
1.2.2
References Updated May 21, 2021 · Source: OSV.dev |
v1.2.0
minor
|
|
v1.1.0
minor
1 CVE
GHSA-gmq2-39ff-f5qg
May 21, 2021
A failed upgrade may lead to hung goroutines
Low
ImpactProcesses using tableflip may encounter hung goroutines in the parent process, after a failed upgrade. The Go runtime has annoying behaviour around setting and clearing O_NONBLOCK: exec.Cmd.Start() ends up calling os.File.Fd() for any file in exec.Cmd.ExtraFiles. os.File.Fd() disables both the use of the runtime poller for the file and clears O_NONBLOCK from the underlying open file descriptor. This can lead to goroutines hanging in a parent process, after at least one failed upgrade. The bug manifests in goroutines which rely on either a deadline or interruption via Close() to be unblocked being stuck in read or accept like syscalls. As far as I can tell we've not experienced this problem in production, so it's most likely quite rare. PatchesThe problem has been fixed in v1.2.2. WorkaroundsNone. References
Fixed in
1.2.2
References Updated May 21, 2021 · Source: OSV.dev |
v1.1.0
minor
|
|
v1.0.0
initial
1 CVE
GHSA-gmq2-39ff-f5qg
May 21, 2021
A failed upgrade may lead to hung goroutines
Low
ImpactProcesses using tableflip may encounter hung goroutines in the parent process, after a failed upgrade. The Go runtime has annoying behaviour around setting and clearing O_NONBLOCK: exec.Cmd.Start() ends up calling os.File.Fd() for any file in exec.Cmd.ExtraFiles. os.File.Fd() disables both the use of the runtime poller for the file and clears O_NONBLOCK from the underlying open file descriptor. This can lead to goroutines hanging in a parent process, after at least one failed upgrade. The bug manifests in goroutines which rely on either a deadline or interruption via Close() to be unblocked being stuck in read or accept like syscalls. As far as I can tell we've not experienced this problem in production, so it's most likely quite rare. PatchesThe problem has been fixed in v1.2.2. WorkaroundsNone. References
Fixed in
1.2.2
References Updated May 21, 2021 · Source: OSV.dev |
v1.0.0
initial
|