VT switching API is inherently racy
Bug #290197 reported by
Pete Graner
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Won't Fix
|
Medium
|
Canonical Kernel Team |
Bug Description
The requisite calling sequence for switching to a different VT is:
1. ioctl(VT_ACTIVATE, N) // request an asynchronous switch to VT #N
2. ioctl(VT_
If, between these two steps, another process calls VT_ACTIVATE, call #2 will block indefinitely waiting for the VT to become active.
Changed in linux: | |
assignee: | nobody → lieb |
importance: | Undecided → High |
milestone: | none → intrepid-updates |
status: | New → Triaged |
Changed in linux (Ubuntu): | |
importance: | High → Medium |
tags: | added: kj-omit |
Changed in linux (Ubuntu): | |
status: | Triaged → Won't Fix |
assignee: | Jim Lieb (lieb) → Canonical Kernel Team (canonical-kernel-team) |
To post a comment you must log in.
Some examples of problems related to this API include bug 243047 and bug 268644.
There was also a bug way back in Ubuntu 6.10 or so which was fixed in usplash 0.4-18, though I can't find the bug number at the moment.