aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/tools/perf/scripts/python/exported-sql-viewer.py
diff options
context:
space:
mode:
authorJann Horn <jannh@google.com>2023-08-15 23:22:16 +0200
committerAndrew Morton <akpm@linux-foundation.org>2023-08-24 16:20:27 -0700
commit004a9a38e20da6eb88fbfb7eeff0f3dd8a01776a (patch)
tree2346a5f6090ae5483c243080d7d0ae03de305503 /tools/perf/scripts/python/exported-sql-viewer.py
parentarm64: mm: use ptep_clear() instead of pte_clear() in clear_flush() (diff)
downloadwireguard-linux-004a9a38e20da6eb88fbfb7eeff0f3dd8a01776a.tar.xz
wireguard-linux-004a9a38e20da6eb88fbfb7eeff0f3dd8a01776a.zip
mm: userfaultfd: remove stale comment about core dump locking
Since commit 7f3bfab52cab ("mm/gup: take mmap_lock in get_dump_page()"), which landed in v5.10, core dumping doesn't enter fault handling without holding the mmap_lock anymore. Remove the stale parts of the comments, but leave the behavior as-is - letting core dumping block on userfault handling would be a bad idea and could lead to deadlocks if the dumping process was handling its own userfaults. Link: https://lkml.kernel.org/r/20230815212216.264445-1-jannh@google.com Signed-off-by: Jann Horn <jannh@google.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Diffstat (limited to 'tools/perf/scripts/python/exported-sql-viewer.py')
0 files changed, 0 insertions, 0 deletions