mbox series

[v8,0/2] hugetlb MADV_DONTNEED fix and zap_page_range cleanup

Message ID 20221108011910.350887-1-mike.kravetz@oracle.com (mailing list archive)
Headers show
Series hugetlb MADV_DONTNEED fix and zap_page_range cleanup | expand

Message

Mike Kravetz Nov. 8, 2022, 1:19 a.m. UTC 
Sending v8 as a two patch series.
Patch 1 addressed the huegtlb MADV_DONTNEED bug and should eventually go
to stable releases.
Patch 2 is cleanup which removes zap_page_range and changes as all callers
to use the new zap_vma_range routine as they only pass ranges within a
single vma.

These changes inspired by discussions with Nadav and Peter.

Andrew, I would suggest not replacing the patch currently in
mm-hotfixes-unstable branch until there is some feedback here.

Mike Kravetz (2):
  hugetlb: don't delete vma_lock in hugetlb MADV_DONTNEED processing
  mm: remove zap_page_range and change callers to use zap_vma_range

 arch/arm64/kernel/vdso.c                |  4 +--
 arch/powerpc/kernel/vdso.c              |  2 +-
 arch/powerpc/platforms/book3s/vas-api.c |  2 +-
 arch/powerpc/platforms/pseries/vas.c    |  2 +-
 arch/riscv/kernel/vdso.c                |  4 +--
 arch/s390/kernel/vdso.c                 |  2 +-
 arch/s390/mm/gmap.c                     |  2 +-
 arch/x86/entry/vdso/vma.c               |  2 +-
 drivers/android/binder_alloc.c          |  2 +-
 include/linux/mm.h                      |  5 ++-
 mm/hugetlb.c                            | 45 +++++++++++++----------
 mm/madvise.c                            |  4 +--
 mm/memory.c                             | 47 +++++++------------------
 mm/page-writeback.c                     |  2 +-
 net/ipv4/tcp.c                          |  6 ++--
 15 files changed, 61 insertions(+), 70 deletions(-)

Comments

Mike Kravetz Nov. 10, 2022, 7:46 p.m. UTC | #1 
On 11/07/22 17:19, Mike Kravetz wrote:
> Sending v8 as a two patch series.
> Patch 1 addressed the huegtlb MADV_DONTNEED bug and should eventually go
> to stable releases.
> Patch 2 is cleanup which removes zap_page_range and changes as all callers
> to use the new zap_vma_range routine as they only pass ranges within a
> single vma.
> 
> These changes inspired by discussions with Nadav and Peter.
> 
> Andrew, I would suggest not replacing the patch currently in
> mm-hotfixes-unstable branch until there is some feedback here.

Any comments?

Because of previous churn I asked Andrew not to add to his tree.  v7 with
zap_page_range fixup is sitting in mm-hotfixes-unstable.