diff options
| author | Suren Baghdasaryan <surenb@google.com> | 2023-08-04 08:27:23 -0700 |
|---|---|---|
| committer | Andrew Morton <akpm@linux-foundation.org> | 2023-08-21 13:37:46 -0700 |
| commit | ad9f006351c3368171458ae7ab14d72f031b239f (patch) | |
| tree | 654bdfd191b866fcf7b1ec3335f9e8c69cf6d5ec /tools/perf/scripts/python/bin/stackcollapse-report | |
| parent | 60081bf19b0ec8fa40c589bd361fa2bc763f1050 (diff) | |
| download | linux-ad9f006351c3368171458ae7ab14d72f031b239f.tar.gz linux-ad9f006351c3368171458ae7ab14d72f031b239f.zip | |
mm: always lock new vma before inserting into vma tree
While it's not strictly necessary to lock a newly created vma before
adding it into the vma tree (as long as no further changes are performed
to it), it seems like a good policy to lock it and prevent accidental
changes after it becomes visible to the page faults. Lock the vma before
adding it into the vma tree.
[akpm@linux-foundation.org: fix reject fixing in vma_link(), per Jann]
Link: https://lkml.kernel.org/r/20230804152724.3090321-6-surenb@google.com
Suggested-by: Jann Horn <jannh@google.com>
Signed-off-by: Suren Baghdasaryan <surenb@google.com>
Reviewed-by: Liam R. Howlett <Liam.Howlett@oracle.com>
Cc: Linus Torvalds <torvalds@linuxfoundation.org>
Cc: Jann Horn <jannh@google.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-report')
0 files changed, 0 insertions, 0 deletions