diff options
author | David S. Miller <davem@davemloft.net> | 2015-06-25 06:01:10 -0700 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2015-06-25 06:01:10 -0700 |
commit | f01cae4e1a9bc845ee125cdb763ccf18298d3fdc (patch) | |
tree | 93d8f24e2555c4ffc0b559286d13a37b19020272 /fs/ext4/crypto_key.c | |
parent | aefbef10e3ae6e2c6e3c54f906f10b34c73a2c66 (diff) | |
parent | 2d89cd8625c4af01a2683b18c3c8194cc3b3067c (diff) |
Merge branch 'sparc-perf-stack'
David Ahern says:
====================
sparc64: perf fixes for userspace stacks
Coming back to the perf userspace callchain problem. As a reminder there are
a series of problems trying to use perf to collect callchains with scheduling
tracepoints, e.g., perf sched record -g -- <cmd>.
The first patch disables pagefaults while walking the user stack. As discussed
a couple of months ago this is the right fix, but I was puzzled as to why
processes were terminating with sigbus (and sometimes sigsegv). I believe the
root of this problem is bad addresses trying to walk the frames using frame
pointers. The bad addresses lead to faults that get handled by do_sparc64_fault
and it aborts the task though I am still puzzled as to why it gets past this
check in do_sparc64_fault:
if (in_atomic() || !mm)
goto intr_or_no_mm;
pagefault_disable bumps the preempt_count which should make in_atomic return != 0
(building kernels with preemption set to voluntar, CONFIG_PREEMPT_VOLUNTARY=y).
While this set does not fully solve the problem it does prevent a number of
pain points with the current code, most notably able to lock up the system.
====================
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'fs/ext4/crypto_key.c')
0 files changed, 0 insertions, 0 deletions