diff options
author | Linus Torvalds <[email protected]> | 2018-08-01 09:57:50 -0700 |
---|---|---|
committer | Linus Torvalds <[email protected]> | 2018-08-01 09:57:50 -0700 |
commit | ebad825cdd4e6b327eaf0dd72439408957049cea (patch) | |
tree | 1968af65b9f31924d271db19ade63809fed105ec /tools/perf/scripts/python/flamegraph.py | |
parent | 37b71411b75c6a6c918e3102097417fdfed667b8 (diff) |
ia64: mark special ia64 memory areas anonymous
Commit bfd40eaff5ab ("mm: fix vma_is_anonymous() false-positives") made
newly allocated vma's have a dummy vm_ops field so that they wouldn't be
mistaken for anonymous mappings, and if you wanted an anonymous vma you
had to explicitly say so by calling "vma_set_anonymous()" on it.
However, it missed the two special vmas that ia64 processes have: the
register backing store and the NaT page. So they wouldn't actually act
like anonymous ranges, and page faults on them caused a SIGBUS rather
than the creation of a new anon page in them.
That obviously will make any ia64 binary very unhappy indeed, and the
boot fails early.
Fixes: bfd40eaff5ab ("mm: fix vma_is_anonymous() false-positives")
Reported-by: Tony Luck <[email protected]>
Cc: Kirill Shutemov <[email protected]>
Cc: Andrew Morton <[email protected]>
Cc: Dmitry Vyukov <[email protected]>
Cc: Oleg Nesterov <[email protected]>
Cc: Andrea Arcangeli <[email protected]>
Cc: John Stultz <[email protected]>
Signed-off-by: Linus Torvalds <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/flamegraph.py')
0 files changed, 0 insertions, 0 deletions