This bug was fixed in the package linux - 3.19.0-14.14
---------------
linux (3.19.0-14.14) vivid; urgency=low
[ Upstream Kernel Changes ]
* powerpc: fix memory corruption by pnv_alloc_idle_core_states
- LP: #1442678
* nvme: Fix PRP list calculation for non-4k system page size
- LP: #1442186
* powerpc/perf: Cap 64bit userspace backtraces to PERF_MAX_STACK_DEPTH
- LP: #1442180
-- Leann Ogasawara <[email protected]> Fri, 10 Apr 2015 11:40:37
-0700
** Changed in: linux (Ubuntu Vivid)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1442180
Title:
powerpc/perf: Cap 64bit userspace backtraces to PERF_MAX_STACK_DEPTH
Status in linux package in Ubuntu:
Fix Released
Status in linux-lts-utopic package in Ubuntu:
Invalid
Status in linux source package in Trusty:
Fix Released
Status in linux-lts-utopic source package in Trusty:
Fix Released
Status in linux source package in Utopic:
Fix Released
Status in linux-lts-utopic source package in Utopic:
Invalid
Status in linux source package in Vivid:
Fix Released
Status in linux-lts-utopic source package in Vivid:
Invalid
Bug description:
Cap 64bit userspace backtraces to PERF_MAX_STACK_DEPTH
We cap 32bit userspace backtraces to PERF_MAX_STACK_DEPTH
(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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1442180/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
