diff options
author | Linus Torvalds <torvalds@linux-foundation.org> | 2023-07-03 19:29:48 -0700 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2023-07-04 07:22:59 -0700 |
commit | b5641a5d8b8b14643bfe3d017d64da90a5c55479 (patch) | |
tree | 9e5bd4006f597e073a4faa653b83185dcfa58534 /kernel | |
parent | 24be4d0b46bb0c3c1dc7bacd30957d6144a70dfc (diff) | |
download | linux-stable-b5641a5d8b8b14643bfe3d017d64da90a5c55479.tar.gz linux-stable-b5641a5d8b8b14643bfe3d017d64da90a5c55479.tar.bz2 linux-stable-b5641a5d8b8b14643bfe3d017d64da90a5c55479.zip |
mm: don't do validate_mm() unnecessarily and without mmap locking
This is an addition to commit ae80b4041984 ("mm: validate the mm before
dropping the mmap lock"), because it turns out there were two problems,
but lockdep just stopped complaining after finding the first one.
The do_vmi_align_munmap() function now drops the mmap lock after doing
the validate_mm() call, but it turns out that one of the callers then
immediately calls validate_mm() again.
That's both a bit silly, and now (again) happens without the mmap lock
held.
So just remove that validate_mm() call from the caller, but make sure to
not lose any coverage by doing that mm sanity checking in the error path
of do_vmi_align_munmap() too.
Reported-and-tested-by: kernel test robot <oliver.sang@intel.com>
Link: https://lore.kernel.org/lkml/ZKN6CdkKyxBShPHi@xsang-OptiPlex-9020/
Fixes: 408579cd627a ("mm: Update do_vmi_align_munmap() return semantics")
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'kernel')
0 files changed, 0 insertions, 0 deletions