powerpc/perf: Cap 64bit userspace backtraces to PERF_MAX_STACK_DEPTH
Bug #1442180 reported by
bugproxy
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| linux (Ubuntu) |
Fix Released
|
Critical
|
Leann Ogasawara | ||
| Trusty |
Fix Released
|
Critical
|
Luis Henriques | ||
| Utopic |
Fix Released
|
Critical
|
Luis Henriques | ||
| Vivid |
Fix Released
|
Critical
|
Leann Ogasawara | ||
| linux-lts-utopic (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
| Trusty |
Fix Released
|
Critical
|
Luis Henriques | ||
| Utopic |
Invalid
|
Undecided
|
Unassigned | ||
| Vivid |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
Cap 64bit userspace backtraces to PERF_MAX_
We cap 32bit userspace backtraces to PERF_MAX_
(currently 127), but we forgot to do the same for 64bit backtraces.
If userspace creates a stack frame that points to itself we will
loop forever in the backtrace code with interrupts off.
| tags: | added: architecture-ppc64le bugnameltc-123761 severity-critical targetmilestone-inin1504 |
| affects: | ubuntu → linux (Ubuntu) |
| Changed in linux (Ubuntu): | |
| assignee: | nobody → Taco Screen team (taco-screen-team) |
| status: | New → Confirmed |
| information type: | Public → Private Security |
| Changed in linux (Ubuntu): | |
| assignee: | Taco Screen team (taco-screen-team) → Leann Ogasawara (leannogasawara) |
| importance: | Undecided → Critical |
| status: | Confirmed → In Progress |
| Changed in linux (Ubuntu Utopic): | |
| assignee: | nobody → Luis Henriques (henrix) |
| status: | New → In Progress |
| importance: | Undecided → Critical |
| Changed in linux-lts-utopic (Ubuntu Utopic): | |
| status: | New → Invalid |
| Changed in linux-lts-utopic (Ubuntu Vivid): | |
| status: | New → Invalid |
| Changed in linux (Ubuntu Trusty): | |
| status: | New → In Progress |
| Changed in linux-lts-utopic (Ubuntu Trusty): | |
| status: | New → In Progress |
| assignee: | nobody → Luís Henriques (henrix) |
| Changed in linux (Ubuntu Trusty): | |
| assignee: | nobody → Luís Henriques (henrix) |
| importance: | Undecided → Critical |
| Changed in linux-lts-utopic (Ubuntu Trusty): | |
| importance: | Undecided → Critical |
| information type: | Private Security → Public Security |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #1 |
| Changed in linux (Ubuntu Trusty): | |
| status: | In Progress → Fix Released |
| status: | In Progress → Fix Released |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #3 |
| Changed in linux (Ubuntu Utopic): | |
| status: | In Progress → Fix Released |
| status: | In Progress → Fix Released |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #5 |
| Changed in linux-lts-utopic (Ubuntu Trusty): | |
| status: | In Progress → Fix Released |
| status: | In Progress → Fix Released |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #7 |
| Changed in linux (Ubuntu Vivid): | |
| status: | In Progress → Fix Released |
To post a comment you must log in.
This bug was fixed in the package linux - 3.13.0-49.83
---------------
linux (3.13.0-49.83) trusty; urgency=low
[ Upstream Kernel Changes ]
* powerpc/perf: Cap 64bit userspace backtraces to PERF_MAX_
- LP: #1442180
-- Luis Henriques <email address hidden> Fri, 10 Apr 2015 18:46:02 +0100