select in gilbc 2.33 does not always set select timeout in Hirsute
Bug #1930473 reported by
Balint Reczey
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| GLibC |
Fix Released
|
Critical
|
|||
| glibc (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
| Hirsute |
New
|
Undecided
|
Unassigned | ||
Bug Description
[Impact]
* Not updating select's timeout breaks topline's autopkgtest and possibly other software. https:/
[Test Plan]
* Run Groovy's topline's autopkgtest, it should pass:
$ autopkgtest -U topline_0.3-1.dsc --apt-pocket=
[Where problems could occur]
* The fix removes obsolete checks that prevented updating the returned timeout. There are no unexpected side effects from this.
Revision history for this message
|
|
#1 |
Revision history for this message
|
|
#2 |
Revision history for this message
|
|
#3 |
Revision history for this message
|
|
#4 |
Revision history for this message
|
|
#5 |
| description: | updated |
| Changed in glibc (Ubuntu): | |
| status: | New → Fix Released |
| summary: |
- select in gilbc 2.33 does not always set select timeout + select in gilbc 2.33 does not always set select timeout in Hirsute |
| Changed in glibc: | |
| importance: | Unknown → Critical |
| status: | Unknown → Fix Released |
To post a comment you must log in.
When the [p]select syscall returns with an error (eg. EINTR) the timeout argument is no longer updated.