diff options
| author | Jann Horn <jannh@google.com> | 2023-08-16 00:22:16 +0300 |
|---|---|---|
| committer | Andrew Morton <akpm@linux-foundation.org> | 2023-08-25 02:20:27 +0300 |
| commit | 004a9a38e20da6eb88fbfb7eeff0f3dd8a01776a (patch) | |
| tree | 2346a5f6090ae5483c243080d7d0ae03de305503 /crypto/lz4hc.c | |
| parent | 00de2c9f26b15f1a6f2af516dd8ec5f8d28189b7 (diff) | |
| download | linux-004a9a38e20da6eb88fbfb7eeff0f3dd8a01776a.tar.xz | |
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 'crypto/lz4hc.c')
0 files changed, 0 insertions, 0 deletions