Linux Kernel Memory Management

• Date Index

• [PATCH v5 12/20] floppy: use __bio_add_page for adding single page to bio, (continued)
  • [PATCH v5 12/20] floppy: use __bio_add_page for adding single page to bio, Johannes Thumshirn
  • [PATCH v5 17/20] block: mark bio_add_page as __must_check, Johannes Thumshirn
  • [PATCH v5 10/20] zonefs: use __bio_add_page for adding single page to bio, Johannes Thumshirn
  • [PATCH v5 14/20] md: raid1: use __bio_add_page for adding single page to bio, Johannes Thumshirn
  • [PATCH v5 13/20] md: check for failure when adding pages in alloc_behind_master_bio, Johannes Thumshirn
  • [PATCH v5 16/20] dm-crypt: check if adding pages to clone bio fails, Johannes Thumshirn
    • Re: [dm-devel] [PATCH v5 16/20] dm-crypt: check if adding pages to clone bio fails, Mikulas Patocka
      • Re: [PATCH v5 16/20] dm-crypt: check if adding pages to clone bio fails, Mike Snitzer
        • Re: [PATCH v5 16/20] dm-crypt: check if adding pages to clone bio fails, Mikulas Patocka
          • Re: [PATCH v5 16/20] dm-crypt: check if adding pages to clone bio fails, Mike Snitzer
  • [PATCH v5 15/20] md: raid1: check if adding pages to resync bio fails, Johannes Thumshirn
  • [PATCH v5 08/20] jfs: logmgr: use __bio_add_page to add single page to bio, Johannes Thumshirn
  • Re: [PATCH v5 00/20] bio: check return values of bio_add_page, Johannes Thumshirn
    • Re: [PATCH v5 00/20] bio: check return values of bio_add_page, Jens Axboe
      • Re: [PATCH v5 00/20] bio: check return values of bio_add_page, Johannes Thumshirn
  • Re: [PATCH v5 00/20] bio: check return values of bio_add_page, Jens Axboe
    • Re: [PATCH v5 00/20] bio: check return values of bio_add_page, Johannes Thumshirn
      • Re: [PATCH v5 00/20] bio: check return values of bio_add_page, Jens Axboe
• Payment of your receipt -$499.99 USD, Zackary Olmos
• Let Your Presentation Speak, In Your Language, AI Powered., DeckBird.ai
• Re: [PATCH v3 1/3] kasan: switch kunit tests to console tracepoints, Peter Collingbourne
  • Re: [PATCH v3 1/3] kasan: switch kunit tests to console tracepoints, Nick Desaulniers
  • Re: [PATCH v3 1/3] kasan: switch kunit tests to console tracepoints, Steven Rostedt
    • Re: [PATCH v3 1/3] kasan: switch kunit tests to console tracepoints, Paul Heidekrüger
      • Re: [PATCH v3 1/3] kasan: switch kunit tests to console tracepoints, Andrey Konovalov
        • Re: [PATCH v3 1/3] kasan: switch kunit tests to console tracepoints, Paul Heidekrüger
          • Re: [PATCH v3 1/3] kasan: switch kunit tests to console tracepoints, Andrey Konovalov
            • Re: [PATCH v3 1/3] kasan: switch kunit tests to console tracepoints, Paul Heidekrüger
              • Re: [PATCH v3 1/3] kasan: switch kunit tests to console tracepoints, Marco Elver
                • Re: [PATCH v3 1/3] kasan: switch kunit tests to console tracepoints, Paul Heidekrüger
                  • Re: [PATCH v3 1/3] kasan: switch kunit tests to console tracepoints, Andrey Konovalov
                    • Re: [PATCH v3 1/3] kasan: switch kunit tests to console tracepoints, Paul Heidekrüger
                      • Re: [PATCH v3 1/3] kasan: switch kunit tests to console tracepoints, Marco Elver
                        • Re: Re: [PATCH v3 1/3] kasan: switch kunit tests to console tracepoints, Paul Heidekrüger
                          • Re: [PATCH v3 1/3] kasan: switch kunit tests to console tracepoints, Paul Heidekrüger
• [PATCH v2 00/34] Split ptdesc from struct page, Vishal Moola (Oracle)
  • [PATCH v2 01/34] mm: Add PAGE_TYPE_OP folio functions, Vishal Moola (Oracle)
    • Re: [PATCH v2 01/34] mm: Add PAGE_TYPE_OP folio functions, Mike Rapoport
      • Re: [PATCH v2 01/34] mm: Add PAGE_TYPE_OP folio functions, Vishal Moola
        • Re: [PATCH v2 01/34] mm: Add PAGE_TYPE_OP folio functions, Mike Rapoport
          • Re: [PATCH v2 01/34] mm: Add PAGE_TYPE_OP folio functions, Vishal Moola
            • Re: [PATCH v2 01/34] mm: Add PAGE_TYPE_OP folio functions, Matthew Wilcox
  • [PATCH v2 02/34] s390: Use _pt_s390_gaddr for gmap address tracking, Vishal Moola (Oracle)
    • Re: [PATCH v2 02/34] s390: Use _pt_s390_gaddr for gmap address tracking, Mike Rapoport
      • Re: [PATCH v2 02/34] s390: Use _pt_s390_gaddr for gmap address tracking, Vishal Moola
  • [PATCH v2 03/34] s390: Use pt_frag_refcount for pagetables, Vishal Moola (Oracle)
  • [PATCH v2 04/34] pgtable: Create struct ptdesc, Vishal Moola (Oracle)
  • [PATCH v2 05/34] mm: add utility functions for ptdesc, Vishal Moola (Oracle)
    • Re: [PATCH v2 05/34] mm: add utility functions for ptdesc, Mike Rapoport
      • Re: [PATCH v2 05/34] mm: add utility functions for ptdesc, Vishal Moola
        • Re: [PATCH v2 05/34] mm: add utility functions for ptdesc, Mike Rapoport
          • Re: [PATCH v2 05/34] mm: add utility functions for ptdesc, Vishal Moola
            • Re: [PATCH v2 05/34] mm: add utility functions for ptdesc, Mike Rapoport
              • Re: [PATCH v2 05/34] mm: add utility functions for ptdesc, Matthew Wilcox
                • Re: [PATCH v2 05/34] mm: add utility functions for ptdesc, Mike Rapoport
  • [PATCH v2 06/34] mm: Convert pmd_pgtable_page() to pmd_ptdesc(), Vishal Moola (Oracle)
  • [PATCH v2 07/34] mm: Convert ptlock_alloc() to use ptdescs, Vishal Moola (Oracle)
  • [PATCH v2 08/34] mm: Convert ptlock_ptr() to use ptdescs, Vishal Moola (Oracle)
  • [PATCH v2 09/34] mm: Convert pmd_ptlock_init() to use ptdescs, Vishal Moola (Oracle)
  • [PATCH v2 10/34] mm: Convert ptlock_init() to use ptdescs, Vishal Moola (Oracle)
  • [PATCH v2 11/34] mm: Convert pmd_ptlock_free() to use ptdescs, Vishal Moola (Oracle)
  • [PATCH v2 12/34] mm: Convert ptlock_free() to use ptdescs, Vishal Moola (Oracle)
  • [PATCH v2 13/34] mm: Create ptdesc equivalents for pgtable_{pte,pmd}_page_{ctor,dtor}, Vishal Moola (Oracle)
    • Re: [PATCH v2 13/34] mm: Create ptdesc equivalents for pgtable_{pte,pmd}_page_{ctor,dtor}, Mike Rapoport
      • Re: [PATCH v2 13/34] mm: Create ptdesc equivalents for pgtable_{pte,pmd}_page_{ctor,dtor}, Vishal Moola
  • [PATCH v2 14/34] powerpc: Convert various functions to use ptdescs, Vishal Moola (Oracle)
  • [PATCH v2 15/34] x86: Convert various functions to use ptdescs, Vishal Moola (Oracle)
  • [PATCH v2 16/34] s390: Convert various gmap functions to use ptdescs, Vishal Moola (Oracle)
  • [PATCH v2 17/34] s390: Convert various pgalloc functions to use ptdescs, Vishal Moola (Oracle)
  • [PATCH v2 18/34] mm: Remove page table members from struct page, Vishal Moola (Oracle)
  • [PATCH v2 19/34] pgalloc: Convert various functions to use ptdescs, Vishal Moola (Oracle)
  • [PATCH v2 20/34] arm: Convert various functions to use ptdescs, Vishal Moola (Oracle)
  • [PATCH v2 21/34] arm64: Convert various functions to use ptdescs, Vishal Moola (Oracle)
    • Re: [PATCH v2 21/34] arm64: Convert various functions to use ptdescs, kernel test robot
    • Re: [PATCH v2 21/34] arm64: Convert various functions to use ptdescs, kernel test robot
  • [PATCH v2 22/34] csky: Convert __pte_free_tlb() to use ptdescs, Vishal Moola (Oracle)
  • [PATCH v2 23/34] hexagon: Convert __pte_free_tlb() to use ptdescs, Vishal Moola (Oracle)
  • [PATCH v2 24/34] loongarch: Convert various functions to use ptdescs, Vishal Moola (Oracle)
  • [PATCH v2 25/34] m68k: Convert various functions to use ptdescs, Vishal Moola (Oracle)
  • [PATCH v2 26/34] mips: Convert various functions to use ptdescs, Vishal Moola (Oracle)
  • [PATCH v2 27/34] nios2: Convert __pte_free_tlb() to use ptdescs, Vishal Moola (Oracle)
  • [PATCH v2 28/34] openrisc: Convert __pte_free_tlb() to use ptdescs, Vishal Moola (Oracle)
  • [PATCH v2 29/34] riscv: Convert alloc_{pmd, pte}_late() to use ptdescs, Vishal Moola (Oracle)
    • Re: [PATCH v2 29/34] riscv: Convert alloc_{pmd, pte}_late() to use ptdescs, Palmer Dabbelt
  • [PATCH v2 30/34] sh: Convert pte_free_tlb() to use ptdescs, Vishal Moola (Oracle)
    • Re: [PATCH v2 30/34] sh: Convert pte_free_tlb() to use ptdescs, John Paul Adrian Glaubitz
      • Re: [PATCH v2 30/34] sh: Convert pte_free_tlb() to use ptdescs, Vishal Moola
  • [PATCH v2 31/34] sparc64: Convert various functions to use ptdescs, Vishal Moola (Oracle)
  • [PATCH v2 32/34] sparc: Convert pgtable_pte_page_{ctor, dtor}() to ptdesc equivalents, Vishal Moola (Oracle)
  • [PATCH v2 33/34] um: Convert {pmd, pte}_free_tlb() to use ptdescs, Vishal Moola (Oracle)
  • [PATCH v2 34/34] mm: Remove pgtable_{pmd, pte}_page_{ctor, dtor}() wrappers, Vishal Moola (Oracle)
  • Re: [PATCH v2 00/34] Split ptdesc from struct page, Jason Gunthorpe
• mbind MPOL_INTERLEAVE existing pages, Mike Kravetz
  • Re: mbind MPOL_INTERLEAVE existing pages, Vlastimil Babka
    • Re: mbind MPOL_INTERLEAVE existing pages, Michal Hocko
      • Re: mbind MPOL_INTERLEAVE existing pages, Mike Kravetz
• [PATCH 1/3] mm: handle swap page faults under VMA lock if page is uncontended, Suren Baghdasaryan
  • [PATCH 2/3] mm: drop VMA lock before waiting for migration, Suren Baghdasaryan
    • Re: [PATCH 2/3] mm: drop VMA lock before waiting for migration, Matthew Wilcox
      • Re: [PATCH 2/3] mm: drop VMA lock before waiting for migration, Suren Baghdasaryan
    • Re: [PATCH 2/3] mm: drop VMA lock before waiting for migration, Alistair Popple
      • Re: [PATCH 2/3] mm: drop VMA lock before waiting for migration, Suren Baghdasaryan
        • Re: [PATCH 2/3] mm: drop VMA lock before waiting for migration, Alistair Popple
          • Re: [PATCH 2/3] mm: drop VMA lock before waiting for migration, Suren Baghdasaryan
  • [PATCH 3/3] mm: implement folio wait under VMA lock, Suren Baghdasaryan
  • Re: [PATCH 1/3] mm: handle swap page faults under VMA lock if page is uncontended, Matthew Wilcox
    • Message not available
      • Re: [PATCH 1/3] mm: handle swap page faults under VMA lock if page is uncontended, Matthew Wilcox
        • Re: [PATCH 1/3] mm: handle swap page faults under VMA lock if page is uncontended, Suren Baghdasaryan
          • Re: [PATCH 1/3] mm: handle swap page faults under VMA lock if page is uncontended, Matthew Wilcox
            • Re: [PATCH 1/3] mm: handle swap page faults under VMA lock if page is uncontended, Suren Baghdasaryan
              • Re: [PATCH 1/3] mm: handle swap page faults under VMA lock if page is uncontended, Matthew Wilcox
                • Re: [PATCH 1/3] mm: handle swap page faults under VMA lock if page is uncontended, Suren Baghdasaryan
                  • Re: [PATCH 1/3] mm: handle swap page faults under VMA lock if page is uncontended, Matthew Wilcox
                    • Re: [PATCH 1/3] mm: handle swap page faults under VMA lock if page is uncontended, Suren Baghdasaryan
                  • Re: [PATCH 1/3] mm: handle swap page faults under VMA lock if page is uncontended, Yosry Ahmed
                    • Re: [PATCH 1/3] mm: handle swap page faults under VMA lock if page is uncontended, Suren Baghdasaryan
                      • Re: [PATCH 1/3] mm: handle swap page faults under VMA lock if page is uncontended, Yosry Ahmed
                        • Re: [PATCH 1/3] mm: handle swap page faults under VMA lock if page is uncontended, Huang, Ying
                          • Re: [PATCH 1/3] mm: handle swap page faults under VMA lock if page is uncontended, Suren Baghdasaryan
• [PATCH 00/40] Memory allocation profiling, Suren Baghdasaryan
  • [PATCH 01/40] lib/string_helpers: Drop space in string_get_size's output, Suren Baghdasaryan
    • Re: [PATCH 01/40] lib/string_helpers: Drop space in string_get_size's output, Davidlohr Bueso
      • Re: [PATCH 01/40] lib/string_helpers: Drop space in string_get_size's output, Kent Overstreet
        • Re: [PATCH 01/40] lib/string_helpers: Drop space in string_get_size's output, Andy Shevchenko
          • Re: [PATCH 01/40] lib/string_helpers: Drop space in string_get_size's output, Kent Overstreet
          • Re: [PATCH 01/40] lib/string_helpers: Drop space in string_get_size's output, Liam R. Howlett
            • Re: [PATCH 01/40] lib/string_helpers: Drop space in string_get_size's output, Kent Overstreet
          • Re: [PATCH 01/40] lib/string_helpers: Drop space in string_get_size's output, Kent Overstreet
        • Re: [PATCH 01/40] lib/string_helpers: Drop space in string_get_size's output, James Bottomley
          • Re: [PATCH 01/40] lib/string_helpers: Drop space in string_get_size's output, Kent Overstreet
            • Re: [PATCH 01/40] lib/string_helpers: Drop space in string_get_size's output, James Bottomley
              • Re: [PATCH 01/40] lib/string_helpers: Drop space in string_get_size's output, Dave Chinner
                • Re: [PATCH 01/40] lib/string_helpers: Drop space in string_get_size's output, Vlastimil Babka
                  • Re: [PATCH 01/40] lib/string_helpers: Drop space in string_get_size's output, Andy Shevchenko
                • Re: [PATCH 01/40] lib/string_helpers: Drop space in string_get_size's output, James Bottomley
            • Re: [PATCH 01/40] lib/string_helpers: Drop space in string_get_size's output, Andy Shevchenko
              • Re: [PATCH 01/40] lib/string_helpers: Drop space in string_get_size's output, Kent Overstreet
                • Re: [PATCH 01/40] lib/string_helpers: Drop space in string_get_size's output, Andy Shevchenko
                  • Re: [PATCH 01/40] lib/string_helpers: Drop space in string_get_size's output, Kent Overstreet
                    • Re: [PATCH 01/40] lib/string_helpers: Drop space in string_get_size's output, Andy Shevchenko
                      • Re: [PATCH 01/40] lib/string_helpers: Drop space in string_get_size's output, Kent Overstreet
                        • Re: [PATCH 01/40] lib/string_helpers: Drop space in string_get_size's output, Andy Shevchenko
                          • Re: [PATCH 01/40] lib/string_helpers: Drop space in string_get_size's output, Kent Overstreet
    • Re: [PATCH 01/40] lib/string_helpers: Drop space in string_get_size's output, Jani Nikula
  • [PATCH 02/40] scripts/kallysms: Always include __start and __stop symbols, Suren Baghdasaryan
  • [PATCH 03/40] fs: Convert alloc_inode_sb() to a macro, Suren Baghdasaryan
    • Re: [PATCH 03/40] fs: Convert alloc_inode_sb() to a macro, Petr Tesařík
      • Re: [PATCH 03/40] fs: Convert alloc_inode_sb() to a macro, Kent Overstreet
        • Re: [PATCH 03/40] fs: Convert alloc_inode_sb() to a macro, Petr Tesařík
  • [PATCH 04/40] nodemask: Split out include/linux/nodemask_types.h, Suren Baghdasaryan
  • [PATCH 05/40] prandom: Remove unused include, Suren Baghdasaryan
  • [PATCH 06/40] lib/string.c: strsep_no_empty(), Suren Baghdasaryan
    • Re: [PATCH 06/40] lib/string.c: strsep_no_empty(), Petr Tesařík
  • [PATCH 07/40] Lazy percpu counters, Suren Baghdasaryan
    • Re: [PATCH 07/40] Lazy percpu counters, Randy Dunlap
  • [PATCH 08/40] mm: introduce slabobj_ext to support slab object extensions, Suren Baghdasaryan
  • [PATCH 09/40] mm: introduce __GFP_NO_OBJ_EXT flag to selectively prevent slabobj_ext creation, Suren Baghdasaryan
    • Re: [PATCH 09/40] mm: introduce __GFP_NO_OBJ_EXT flag to selectively prevent slabobj_ext creation, Petr Tesařík
      • Re: [PATCH 09/40] mm: introduce __GFP_NO_OBJ_EXT flag to selectively prevent slabobj_ext creation, Suren Baghdasaryan
  • [PATCH 10/40] mm/slab: introduce SLAB_NO_OBJ_EXT to avoid obj_ext creation, Suren Baghdasaryan
  • [PATCH 11/40] mm: prevent slabobj_ext allocations for slabobj_ext and kmem_cache objects, Suren Baghdasaryan
  • [PATCH 12/40] slab: objext: introduce objext_flags as extension to page_memcg_data_flags, Suren Baghdasaryan
  • [PATCH 13/40] lib: code tagging framework, Suren Baghdasaryan
  • [PATCH 15/40] lib: prevent module unloading if memory is not freed, Suren Baghdasaryan
  • [PATCH 16/40] lib: code tagging query helper functions, Suren Baghdasaryan
  • [PATCH 17/40] lib: add allocation tagging support for memory allocation profiling, Suren Baghdasaryan
  • [PATCH 18/40] lib: introduce support for page allocation tagging, Suren Baghdasaryan
  • [PATCH 19/40] change alloc_pages name in dma_map_ops to avoid name conflicts, Suren Baghdasaryan
    • Re: [PATCH 19/40] change alloc_pages name in dma_map_ops to avoid name conflicts, Petr Tesařík
      • Re: [PATCH 19/40] change alloc_pages name in dma_map_ops to avoid name conflicts, Suren Baghdasaryan
        • Re: [PATCH 19/40] change alloc_pages name in dma_map_ops to avoid name conflicts, Petr Tesařík
          • Re: [PATCH 19/40] change alloc_pages name in dma_map_ops to avoid name conflicts, Kent Overstreet
          • Re: [PATCH 19/40] change alloc_pages name in dma_map_ops to avoid name conflicts, Suren Baghdasaryan
            • Re: [PATCH 19/40] change alloc_pages name in dma_map_ops to avoid name conflicts, Petr Tesařík
              • Re: [PATCH 19/40] change alloc_pages name in dma_map_ops to avoid name conflicts, Suren Baghdasaryan
    • Re: [PATCH 19/40] change alloc_pages name in dma_map_ops to avoid name conflicts, Steven Rostedt
      • Re: [PATCH 19/40] change alloc_pages name in dma_map_ops to avoid name conflicts, Suren Baghdasaryan
  • [PATCH 20/40] mm: enable page allocation tagging, Suren Baghdasaryan
  • [PATCH 21/40] mm/page_ext: enable early_page_ext when CONFIG_MEM_ALLOC_PROFILING_DEBUG=y, Suren Baghdasaryan
  • [PATCH 22/40] mm: create new codetag references during page splitting, Suren Baghdasaryan
  • [PATCH 23/40] lib: add codetag reference into slabobj_ext, Suren Baghdasaryan
  • [PATCH 24/40] mm/slab: add allocation accounting into slab allocation and free paths, Suren Baghdasaryan
  • [PATCH 25/40] mm/slab: enable slab allocation tagging for kmalloc and friends, Suren Baghdasaryan
  • [PATCH 26/40] mm/slub: Mark slab_free_freelist_hook() __always_inline, Suren Baghdasaryan
  • [PATCH 27/40] mempool: Hook up to memory allocation profiling, Suren Baghdasaryan
  • [PATCH 28/40] timekeeping: Fix a circular include dependency, Suren Baghdasaryan
    • Re: [PATCH 28/40] timekeeping: Fix a circular include dependency, Thomas Gleixner
  • [PATCH 29/40] mm: percpu: Introduce pcpuobj_ext, Suren Baghdasaryan
  • [PATCH 30/40] mm: percpu: Add codetag reference into pcpuobj_ext, Suren Baghdasaryan
  • [PATCH 31/40] mm: percpu: enable per-cpu allocation tagging, Suren Baghdasaryan
  • [PATCH 33/40] move stack capture functionality into a separate function for reuse, Suren Baghdasaryan
  • [PATCH 34/40] lib: code tagging context capture support, Suren Baghdasaryan
    • Re: [PATCH 34/40] lib: code tagging context capture support, Michal Hocko
      • Re: [PATCH 34/40] lib: code tagging context capture support, Suren Baghdasaryan
        • Re: [PATCH 34/40] lib: code tagging context capture support, Dave Hansen
          • Re: [PATCH 34/40] lib: code tagging context capture support, Suren Baghdasaryan
        • Re: [PATCH 34/40] lib: code tagging context capture support, Michal Hocko
          • Re: [PATCH 34/40] lib: code tagging context capture support, Suren Baghdasaryan
  • [PATCH 35/40] lib: implement context capture support for tagged allocations, Suren Baghdasaryan
    • Re: [PATCH 35/40] lib: implement context capture support for tagged allocations, Michal Hocko
      • Re: [PATCH 35/40] lib: implement context capture support for tagged allocations, Suren Baghdasaryan
        • Re: [PATCH 35/40] lib: implement context capture support for tagged allocations, Michal Hocko
          • Re: [PATCH 35/40] lib: implement context capture support for tagged allocations, Suren Baghdasaryan
            • Re: [PATCH 35/40] lib: implement context capture support for tagged allocations, Michal Hocko
              • Re: [PATCH 35/40] lib: implement context capture support for tagged allocations, Suren Baghdasaryan
  • [PATCH 36/40] lib: add memory allocations report in show_mem(), Suren Baghdasaryan
  • [PATCH 37/40] codetag: debug: skip objext checking when it's for objext itself, Suren Baghdasaryan
  • [PATCH 38/40] codetag: debug: mark codetags for reserved pages as empty, Suren Baghdasaryan
  • [PATCH 39/40] codetag: debug: introduce OBJEXTS_ALLOC_FAIL to mark failed slab_ext allocations, Suren Baghdasaryan
  • [PATCH 40/40] MAINTAINERS: Add entries for code tagging and memory allocation profiling, Suren Baghdasaryan
  • [PATCH 14/40] lib: code tagging module support, Suren Baghdasaryan
  • [PATCH 32/40] arm64: Fix circular header dependency, Suren Baghdasaryan
  • Re: [PATCH 00/40] Memory allocation profiling, Roman Gushchin
    • Re: [PATCH 00/40] Memory allocation profiling, Suren Baghdasaryan
      • Re: [PATCH 00/40] Memory allocation profiling, Roman Gushchin
        • Re: [PATCH 00/40] Memory allocation profiling, Kent Overstreet
          • Re: [PATCH 00/40] Memory allocation profiling, Roman Gushchin
  • Re: [PATCH 00/40] Memory allocation profiling, Michal Hocko
    • Re: [PATCH 00/40] Memory allocation profiling, Kent Overstreet
      • Re: [PATCH 00/40] Memory allocation profiling, Michal Hocko
        • Re: [PATCH 00/40] Memory allocation profiling, Kent Overstreet
          • Re: [PATCH 00/40] Memory allocation profiling, Steven Rostedt
          • Re: [PATCH 00/40] Memory allocation profiling, Tejun Heo
            • Re: [PATCH 00/40] Memory allocation profiling, Suren Baghdasaryan
              • Re: [PATCH 00/40] Memory allocation profiling, Tejun Heo
            • Re: [PATCH 00/40] Memory allocation profiling, Kent Overstreet
            • Re: [PATCH 00/40] Memory allocation profiling, Kent Overstreet
              • Re: [PATCH 00/40] Memory allocation profiling, Tejun Heo
            • Re: [PATCH 00/40] Memory allocation profiling, Johannes Weiner
              • Re: [PATCH 00/40] Memory allocation profiling, Tejun Heo
                • Re: [PATCH 00/40] Memory allocation profiling, Tejun Heo
                  • Re: [PATCH 00/40] Memory allocation profiling, Kent Overstreet
                    • Re: [PATCH 00/40] Memory allocation profiling, Tejun Heo
                      • Re: [PATCH 00/40] Memory allocation profiling, Tejun Heo
                        • Re: [PATCH 00/40] Memory allocation profiling, Suren Baghdasaryan
                          • Re: [PATCH 00/40] Memory allocation profiling, Tejun Heo
                            • Re: [PATCH 00/40] Memory allocation profiling, Tejun Heo
                              • Re: [PATCH 00/40] Memory allocation profiling, Suren Baghdasaryan
                                • Re: [PATCH 00/40] Memory allocation profiling, Tejun Heo
                                  • Re: [PATCH 00/40] Memory allocation profiling, Kent Overstreet
                                  • Re: [PATCH 00/40] Memory allocation profiling, Suren Baghdasaryan
                                • Re: [PATCH 00/40] Memory allocation profiling, Petr Tesařík
                            • Re: [PATCH 00/40] Memory allocation profiling, Suren Baghdasaryan
                              • Re: [PATCH 00/40] Memory allocation profiling, Johannes Weiner
                              • Re: [PATCH 00/40] Memory allocation profiling, Tejun Heo
            • Re: [PATCH 00/40] Memory allocation profiling, Andrey Ryabinin
        • Re: [PATCH 00/40] Memory allocation profiling, Petr Tesařík
          • Re: [PATCH 00/40] Memory allocation profiling, Kent Overstreet
            • Re: [PATCH 00/40] Memory allocation profiling, Petr Tesařík
          • Re: [PATCH 00/40] Memory allocation profiling, Kent Overstreet
            • Re: [PATCH 00/40] Memory allocation profiling, Petr Tesařík
              • Re: [PATCH 00/40] Memory allocation profiling, Kent Overstreet
            • Re: [PATCH 00/40] Memory allocation profiling, James Bottomley
              • Re: [PATCH 00/40] Memory allocation profiling, Suren Baghdasaryan
              • Re: [PATCH 00/40] Memory allocation profiling, Kent Overstreet
                • Re: [PATCH 00/40] Memory allocation profiling, Lorenzo Stoakes
                  • Re: [PATCH 00/40] Memory allocation profiling, Kent Overstreet
                • Re: [PATCH 00/40] Memory allocation profiling, James Bottomley
    • Re: [PATCH 00/40] Memory allocation profiling, Suren Baghdasaryan
      • Re: [PATCH 00/40] Memory allocation profiling, Steven Rostedt
        • Re: [PATCH 00/40] Memory allocation profiling, Suren Baghdasaryan
          • Re: [PATCH 00/40] Memory allocation profiling, Steven Rostedt
            • Re: [PATCH 00/40] Memory allocation profiling, Suren Baghdasaryan
            • Re: [PATCH 00/40] Memory allocation profiling, Kent Overstreet
      • Re: [PATCH 00/40] Memory allocation profiling, Michal Hocko
        • Re: [PATCH 00/40] Memory allocation profiling, Suren Baghdasaryan
          • Re: [PATCH 00/40] Memory allocation profiling, Michal Hocko
            • Re: [PATCH 00/40] Memory allocation profiling, Kent Overstreet
        • Re: [PATCH 00/40] Memory allocation profiling, Kent Overstreet
          • Re: [PATCH 00/40] Memory allocation profiling, Steven Rostedt
            • Re: [PATCH 00/40] Memory allocation profiling, Kent Overstreet
              • Re: [PATCH 00/40] Memory allocation profiling, Steven Rostedt
                • Re: [PATCH 00/40] Memory allocation profiling, Kent Overstreet
          • Re: [PATCH 00/40] Memory allocation profiling, Petr Tesařík
            • Re: [PATCH 00/40] Memory allocation profiling, Kent Overstreet
              • Re: [PATCH 00/40] Memory allocation profiling, Petr Tesařík
                • Re: [PATCH 00/40] Memory allocation profiling, Kent Overstreet
                  • Re: [PATCH 00/40] Memory allocation profiling, Petr Tesařík
                    • Re: [PATCH 00/40] Memory allocation profiling, Kent Overstreet
• Re: [PATCH v6 1/3] mm: vmscan: ignore non-LRU-based reclaim in memcg reclaim, Yosry Ahmed
• [PATCH v2 0/3] permit write-sealed memfd read-only shared mappings, Lorenzo Stoakes
  • [PATCH v2 1/3] mm: drop the assumption that VM_SHARED always implies writable, Lorenzo Stoakes
  • [PATCH v2 2/3] mm: update seal_check_[future_]write() to include F_SEAL_WRITE as well, Lorenzo Stoakes
  • [PATCH v2 3/3] mm: perform the mapping_map_writable() check after call_mmap(), Lorenzo Stoakes
    • Re: [PATCH v2 3/3] mm: perform the mapping_map_writable() check after call_mmap(), Andy Lutomirski
      • Re: [PATCH v2 3/3] mm: perform the mapping_map_writable() check after call_mmap(), Lorenzo Stoakes
    • Re: [PATCH v2 3/3] mm: perform the mapping_map_writable() check after call_mmap(), kernel test robot
      • Re: [PATCH v2 3/3] mm: perform the mapping_map_writable() check after call_mmap(), Lorenzo Stoakes
• [PATCH] mm/mmap/vma_merge: always check invariants, Lorenzo Stoakes
  • Re: [PATCH] mm/mmap/vma_merge: always check invariants, Liam R. Howlett
  • Re: [PATCH] mm/mmap/vma_merge: always check invariants, Vlastimil Babka
  • Re: [PATCH] mm/mmap/vma_merge: always check invariants, David Hildenbrand
  • Re: [PATCH] mm/mmap/vma_merge: always check invariants, Andrew Morton
  • Re: [PATCH] mm/mmap/vma_merge: always check invariants, Mark Rutland
    • Re: [PATCH] mm/mmap/vma_merge: always check invariants, Lorenzo Stoakes
      • Re: [PATCH] mm/mmap/vma_merge: always check invariants, Mark Rutland
        • Re: [PATCH] mm/mmap/vma_merge: always check invariants, Lorenzo Stoakes
          • Re: [PATCH] mm/mmap/vma_merge: always check invariants, Mike Rapoport
            • Re: [PATCH] mm/mmap/vma_merge: always check invariants, Lorenzo Stoakes
            • Re: [PATCH] mm/mmap/vma_merge: always check invariants, Lorenzo Stoakes
• [PATCH v2] mm/mempolicy: Correctly update prev when policy is equal on mbind, Lorenzo Stoakes
• [PATCH] mm/mempolicy: Correctly update prev when policy is equal on mbind, Lorenzo Stoakes
• [linux-stable-rc:linux-6.2.y] [mm/mempolicy] 75cd8305a0: WARNING:at_mm/mmap.c:#vma_merge, kernel test robot
  • Re: [linux-stable-rc:linux-6.2.y] [mm/mempolicy] 75cd8305a0: WARNING:at_mm/mmap.c:#vma_merge, Lorenzo Stoakes
  • Re: [linux-stable-rc:linux-6.2.y] [mm/mempolicy] 75cd8305a0: WARNING:at_mm/mmap.c:#vma_merge, Lorenzo Stoakes
• fs/dax.c:1087:23: sparse: sparse: Using plain integer as NULL pointer, kernel test robot
• Re: [PATCH v2] mm/mmap: Regression fix for unmapped_area{_topdown}, Tad
  • Re: [PATCH v2] mm/mmap: Regression fix for unmapped_area{_topdown}, Michael Keyes
    • Re: [PATCH v2] mm/mmap: Regression fix for unmapped_area{_topdown}, Liam R. Howlett
      • Re: [PATCH v2] mm/mmap: Regression fix for unmapped_area{_topdown}, Liam R. Howlett
        • Re: [PATCH v2] mm/mmap: Regression fix for unmapped_area{_topdown}, Juhyung Park
          • Re: [PATCH v2] mm/mmap: Regression fix for unmapped_area{_topdown}, Liam R. Howlett
• [cel:topic-shmem-stable-dir-cookies] [shmem] 77323f99e9: aim9.disk_src.ops_per_sec -18.6% regression, kernel test robot
• [linux-next:master] BUILD REGRESSION 92e815cf07ed24ee1c51b122f24ffcf2964b4b13, kernel test robot
• [PATCH v3 0/2] Reduce lock contention related with large folio, Yin Fengwei
  • [PATCH v3 1/2] THP: avoid lock when check whether THP is in deferred list, Yin Fengwei
    • Re: [PATCH v3 1/2] THP: avoid lock when check whether THP is in deferred list, kirill
      • Re: [PATCH v3 1/2] THP: avoid lock when check whether THP is in deferred list, Yin, Fengwei
      • Re: [PATCH v3 1/2] THP: avoid lock when check whether THP is in deferred list, Yin Fengwei
        • Re: [PATCH v3 1/2] THP: avoid lock when check whether THP is in deferred list, Yin, Fengwei
    • Re: [PATCH v3 1/2] THP: avoid lock when check whether THP is in deferred list, Huang, Ying
      • Re: [PATCH v3 1/2] THP: avoid lock when check whether THP is in deferred list, Yin, Fengwei
  • [PATCH v3 2/2] lru: allow large batched add large folio to lru list, Yin Fengwei
    • Re: [PATCH v3 2/2] lru: allow large batched add large folio to lru list, Matthew Wilcox
      • Re: [PATCH v3 2/2] lru: allow large batched add large folio to lru list, Yin, Fengwei
      • Re: [PATCH v3 2/2] lru: allow large batched add large folio to lru list, Yin, Fengwei
        • Re: [PATCH v3 2/2] lru: allow large batched add large folio to lru list, Yin, Fengwei
    • Re: [PATCH v3 2/2] lru: allow large batched add large folio to lru list, Matthew Wilcox
      • Re: [PATCH v3 2/2] lru: allow large batched add large folio to lru list, Yin Fengwei
      • Re: [PATCH v3 2/2] lru: allow large batched add large folio to lru list, Yin Fengwei
• [linux-next:master 14283/14376] trace.c:undefined reference to `ftrace_stub_direct_tramp', kernel test robot
• [PATCH AUTOSEL 6.1 2/3] selftests: cgroup: Add 'malloc' failures checks in test_memcontrol, Sasha Levin
  • <Possible follow-ups>
  • [PATCH AUTOSEL 6.1 2/3] selftests: cgroup: Add 'malloc' failures checks in test_memcontrol, Sasha Levin
• [PATCH AUTOSEL 6.2 2/3] selftests: cgroup: Add 'malloc' failures checks in test_memcontrol, Sasha Levin
• [PATCH AUTOSEL 6.3 2/3] selftests: cgroup: Add 'malloc' failures checks in test_memcontrol, Sasha Levin
  • <Possible follow-ups>
  • [PATCH AUTOSEL 6.3 2/3] selftests: cgroup: Add 'malloc' failures checks in test_memcontrol, Sasha Levin
• Maple tree MAP_32BIT issue, Edgecombe, Rick P
• [linux-next:pending-fixes] BUILD SUCCESS b3f869e79cdf0e15e03b2e77ca14e825c18d933e, kernel test robot
• Re: [PATCH 6.3 00/11] 6.3.1-rc1 review, Naresh Kamboju
• [PATCH v3] migrate_pages: Avoid blocking for IO in MIGRATE_SYNC_LIGHT, Douglas Anderson
  • Re: [PATCH v3] migrate_pages: Avoid blocking for IO in MIGRATE_SYNC_LIGHT, Matthew Wilcox
  • Re: [PATCH v3] migrate_pages: Avoid blocking for IO in MIGRATE_SYNC_LIGHT, Hillf Danton
    • Re: [PATCH v3] migrate_pages: Avoid blocking for IO in MIGRATE_SYNC_LIGHT, Doug Anderson
  • Re: [PATCH v3] migrate_pages: Avoid blocking for IO in MIGRATE_SYNC_LIGHT, Mel Gorman
  • Message not available
    • Re: [PATCH v3] migrate_pages: Avoid blocking for IO in MIGRATE_SYNC_LIGHT, Doug Anderson
      • Re: [PATCH v3] migrate_pages: Avoid blocking for IO in MIGRATE_SYNC_LIGHT, Hillf Danton
        • Re: [PATCH v3] migrate_pages: Avoid blocking for IO in MIGRATE_SYNC_LIGHT, Doug Anderson
          • Re: [PATCH v3] migrate_pages: Avoid blocking for IO in MIGRATE_SYNC_LIGHT, Hillf Danton
• [PATCH 1/1] mm: change per-VMA lock statistics to be disabled by default, Suren Baghdasaryan
  • Re: [PATCH 1/1] mm: change per-VMA lock statistics to be disabled by default, Lorenzo Stoakes
  • Re: [PATCH 1/1] mm: change per-VMA lock statistics to be disabled by default, David Hildenbrand
  • Re: [PATCH 1/1] mm: change per-VMA lock statistics to be disabled by default, Vlastimil Babka
• [sudeep-holla:android13-5.10/ffa 8920/9999] arch/x86/include/asm/syscall_wrapper.h:83:21: warning: no previous prototype for '__ia32_sys_process_mrelease', kernel test robot
• [PATCH RFC net-next/mm V3 0/2] page_pool: new approach for leak detection and shutdown phase, Jesper Dangaard Brouer
  • [PATCH RFC net-next/mm V3 1/2] page_pool: Remove workqueue in new shutdown scheme, Jesper Dangaard Brouer
    • Re: [PATCH RFC net-next/mm V3 1/2] page_pool: Remove workqueue in new shutdown scheme, Toke Høiland-Jørgensen
      • Re: [PATCH RFC net-next/mm V3 1/2] page_pool: Remove workqueue in new shutdown scheme, Jesper Dangaard Brouer
    • Re: [PATCH RFC net-next/mm V3 1/2] page_pool: Remove workqueue in new shutdown scheme, Jakub Kicinski
      • Re: [PATCH RFC net-next/mm V3 1/2] page_pool: Remove workqueue in new shutdown scheme, Toke Høiland-Jørgensen
        • Re: [PATCH RFC net-next/mm V3 1/2] page_pool: Remove workqueue in new shutdown scheme, Jesper Dangaard Brouer
          • Re: [PATCH RFC net-next/mm V3 1/2] page_pool: Remove workqueue in new shutdown scheme, Jakub Kicinski
    • Re: [PATCH RFC net-next/mm V3 1/2] page_pool: Remove workqueue in new shutdown scheme, Yunsheng Lin
      • Re: [PATCH RFC net-next/mm V3 1/2] page_pool: Remove workqueue in new shutdown scheme, Jesper Dangaard Brouer
        • Re: [PATCH RFC net-next/mm V3 1/2] page_pool: Remove workqueue in new shutdown scheme, Yunsheng Lin
          • Re: [PATCH RFC net-next/mm V3 1/2] page_pool: Remove workqueue in new shutdown scheme, Yunsheng Lin
  • [PATCH RFC net-next/mm V3 2/2] mm/page_pool: catch page_pool memory leaks, Jesper Dangaard Brouer
• [PATCH V8 2/2] mm: shmem: implement POSIX_FADV_[WILL|DONT]NEED for shmem, Charan Teja Kalla
• [PATCH V8 0/2] mm: shmem: support POSIX_FADV_[WILL|DONT]NEED for shmem files, Charan Teja Kalla
  • Re: [PATCH V8 0/2] mm: shmem: support POSIX_FADV_[WILL|DONT]NEED for shmem files, Charan Teja Kalla
• [PATCH V8 1/2] mm: fadvise: move 'endbyte' calculations to helper function, Charan Teja Kalla
• Re: [LSF/MM/BPF TOPIC] userspace control of memory management, Lorenzo Stoakes
• [sudeep-holla:android13-5.10/ffa 8920/9999] arch/x86/include/asm/syscall_wrapper.h:83:21: warning: no previous prototype for '__x64_sys_process_mrelease', kernel test robot
• Re: [Lsf-pc] Fwd: [LSF/MM/BPF TOPIC] userspace control of memory management, Michal Hocko
  • Re: [Lsf-pc] Fwd: [LSF/MM/BPF TOPIC] userspace control of memory management, Matthew Wilcox
    • Re: [Lsf-pc] Fwd: [LSF/MM/BPF TOPIC] userspace control of memory management, Michal Hocko
  • Re: [Lsf-pc] Fwd: [LSF/MM/BPF TOPIC] userspace control of memory management, Hao Luo
• [syzbot] [mm?] [net?] KASAN: null-ptr-deref Read in filemap_fault, syzbot
  • Re: [syzbot] [mm?] [udf?] KASAN: null-ptr-deref Read in filemap_fault, syzbot
  • Re: [syzbot] [mm?] [udf?] KASAN: null-ptr-deref Read in filemap_fault, syzbot
    • Re: [syzbot] [mm?] [udf?] KASAN: null-ptr-deref Read in filemap_fault, Jan Kara
• [PATCH v2 0/2] memcg: OOM log improvements, Yosry Ahmed
  • [PATCH v2 1/2] memcg: use seq_buf_do_printk() with mem_cgroup_print_oom_meminfo(), Yosry Ahmed
    • Re: [PATCH v2 1/2] memcg: use seq_buf_do_printk() with mem_cgroup_print_oom_meminfo(), Shakeel Butt
    • Re: [PATCH v2 1/2] memcg: use seq_buf_do_printk() with mem_cgroup_print_oom_meminfo(), Muchun Song
  • [PATCH v2 2/2] memcg: dump memory.stat during cgroup OOM for v1, Yosry Ahmed
    • Re: [PATCH v2 2/2] memcg: dump memory.stat during cgroup OOM for v1, Michal Hocko
      • Re: [PATCH v2 2/2] memcg: dump memory.stat during cgroup OOM for v1, Yosry Ahmed
    • Re: [PATCH v2 2/2] memcg: dump memory.stat during cgroup OOM for v1, Shakeel Butt
• [PATCH] mm: Do not reclaim private data from pinned page, Jan Kara
  • Re: [PATCH] mm: Do not reclaim private data from pinned page, Matthew Wilcox
  • Re: [PATCH] mm: Do not reclaim private data from pinned page, Lorenzo Stoakes
  • Re: [PATCH] mm: Do not reclaim private data from pinned page, Christoph Hellwig
  • Re: [PATCH] mm: Do not reclaim private data from pinned page, John Hubbard
  • Re: [PATCH] mm: Do not reclaim private data from pinned page, David Hildenbrand
  • Re: [PATCH] mm: Do not reclaim private data from pinned page, Peter Xu
    • Re: [PATCH] mm: Do not reclaim private data from pinned page, David Hildenbrand
      • Re: [PATCH] mm: Do not reclaim private data from pinned page, Peter Xu
        • Re: [PATCH] mm: Do not reclaim private data from pinned page, David Hildenbrand
  • Re: [PATCH] mm: Do not reclaim private data from pinned page, Andrew Morton
    • Re: [PATCH] mm: Do not reclaim private data from pinned page, Jan Kara
• [PATCH] mm: optimization on page allocation when CMA enabled, zhaoyang.huang
  • Re: [PATCH] mm: optimization on page allocation when CMA enabled, kernel test robot
  • Re: [PATCH] mm: optimization on page allocation when CMA enabled, kernel test robot
  • Re: [PATCH] mm: optimization on page allocation when CMA enabled, Roman Gushchin
    • 答复: [PATCH] mm: optimization on page allocation when CMA enabled, 黄朝阳 (Zhaoyang Huang)
      • Re: 答复: [PATCH] mm: optimization on page allocation when CMA enabled, Roman Gushchin
        • Re: 答复: [PATCH] mm: optimization on page allocation when CMA enabled, Zhaoyang Huang
          • Re: 答复: [PATCH] mm: optimization on page allocation when CMA enabled, Roman Gushchin
            • Re: 答复: [PATCH] mm: optimization on page allocation when CMA enabled, Zhaoyang Huang
              • Re: 答复: [PATCH] mm: optimization on page allocation when CMA enabled, Zhaoyang Huang
• [PATCH] mm/memory_hotplug: fix dead loop in offline_pages(), Yajun Deng
  • Re: [PATCH] mm/memory_hotplug: fix dead loop in offline_pages(), Michal Hocko
    • Re: [PATCH] mm/memory_hotplug: fix dead loop in offline_pages(), David Hildenbrand
• [PATCH RFC 18/43] x86/percpu: Use PC-relative addressing for percpu variable references, Hou Wenlong
• [linux-next:master] BUILD SUCCESS WITH WARNING 84e2893b4573da3bc0c9f24e2005442e420e3831, kernel test robot
• Re: fuse uring / wake_up on the same core, Hillf Danton
  • Re: fuse uring / wake_up on the same core, Bernd Schubert
    • Re: fuse uring / wake_up on the same core, Hillf Danton
    • Re: fuse uring / wake_up on the same core, Bernd Schubert
    • Message not available
      • Re: fuse uring / wake_up on the same core, Bernd Schubert
        • Re: fuse uring / wake_up on the same core, Hillf Danton
          • Re: fuse uring / wake_up on the same core, Bernd Schubert
• [RFC PATCH v1 0/7] PAGE_SIZE Unmapping in Memory Failure Recovery for HugeTLB Pages, Jiaqi Yan
  • [RFC PATCH v1 1/7] hugetlb: add HugeTLB splitting functionality, Jiaqi Yan
  • [RFC PATCH v1 2/7] hugetlb: create PTE level mapping when possible, Jiaqi Yan
  • [RFC PATCH v1 3/7] mm: publish raw_hwp_page in mm.h, Jiaqi Yan
  • [RFC PATCH v1 4/7] mm/memory_failure: unmap raw HWPoison PTEs when possible, Jiaqi Yan
    • Message not available
      • Re: [RFC PATCH v1 4/7] mm/memory_failure: unmap raw HWPoison PTEs when possible, Jiaqi Yan
        • Re: [RFC PATCH v1 4/7] mm/memory_failure: unmap raw HWPoison PTEs when possible, Jiaqi Yan
    • Re: [RFC PATCH v1 4/7] mm/memory_failure: unmap raw HWPoison PTEs when possible, HORIGUCHI NAOYA(堀口　直也)
  • [RFC PATCH v1 5/7] hugetlb: only VM_FAULT_HWPOISON_LARGE raw page, Jiaqi Yan
  • [RFC PATCH v1 6/7] selftest/mm: test PAGESIZE unmapping HWPOISON pages, Jiaqi Yan
  • [RFC PATCH v1 7/7] selftest/mm: test PAGESIZE unmapping UFFD WP marker HWPOISON pages, Jiaqi Yan
• [linux-next:pending-fixes] BUILD SUCCESS c94d3163e00b9e4412e984ba19a578ec2022f3c6, kernel test robot
• [PATCH v5] mm/gup: disallow GUP writing to file-backed mappings by default, Lorenzo Stoakes
  • Re: [PATCH v5] mm/gup: disallow GUP writing to file-backed mappings by default, John Hubbard
  • Re: [PATCH v5] mm/gup: disallow GUP writing to file-backed mappings by default, Mika Penttilä
  • Re: [PATCH v5] mm/gup: disallow GUP writing to file-backed mappings by default, Jan Kara
  • Re: [PATCH v5] mm/gup: disallow GUP writing to file-backed mappings by default, Lorenzo Stoakes
  • Re: [PATCH v5] mm/gup: disallow GUP writing to file-backed mappings by default, Jason Gunthorpe
  • Re: [PATCH v5] mm/gup: disallow GUP writing to file-backed mappings by default, David Hildenbrand
    • Re: [PATCH v5] mm/gup: disallow GUP writing to file-backed mappings by default, Jason Gunthorpe
      • Re: [PATCH v5] mm/gup: disallow GUP writing to file-backed mappings by default, David Hildenbrand
        • Re: [PATCH v5] mm/gup: disallow GUP writing to file-backed mappings by default, David Hildenbrand
          • Re: [PATCH v5] mm/gup: disallow GUP writing to file-backed mappings by default, Lorenzo Stoakes
            • Re: [PATCH v5] mm/gup: disallow GUP writing to file-backed mappings by default, David Hildenbrand
              • Re: [PATCH v5] mm/gup: disallow GUP writing to file-backed mappings by default, David Hildenbrand
                • Re: [PATCH v5] mm/gup: disallow GUP writing to file-backed mappings by default, Kirill A . Shutemov
                  • Re: [PATCH v5] mm/gup: disallow GUP writing to file-backed mappings by default, David Hildenbrand
                    • Re: [PATCH v5] mm/gup: disallow GUP writing to file-backed mappings by default, Kirill A . Shutemov
                      • Re: [PATCH v5] mm/gup: disallow GUP writing to file-backed mappings by default, Peter Xu
                        • Re: [PATCH v5] mm/gup: disallow GUP writing to file-backed mappings by default, David Hildenbrand
                          • Re: [PATCH v5] mm/gup: disallow GUP writing to file-backed mappings by default, Kirill A . Shutemov
                            • Re: [PATCH v5] mm/gup: disallow GUP writing to file-backed mappings by default, Lorenzo Stoakes
                            • Re: [PATCH v5] mm/gup: disallow GUP writing to file-backed mappings by default, David Hildenbrand
                              • Re: [PATCH v5] mm/gup: disallow GUP writing to file-backed mappings by default, Jason Gunthorpe
                                • Re: [PATCH v5] mm/gup: disallow GUP writing to file-backed mappings by default, Lorenzo Stoakes
                                  • Re: [PATCH v5] mm/gup: disallow GUP writing to file-backed mappings by default, Jason Gunthorpe
                              • Re: [PATCH v5] mm/gup: disallow GUP writing to file-backed mappings by default, Kirill A . Shutemov
                                • Re: [PATCH v5] mm/gup: disallow GUP writing to file-backed mappings by default, Jan Kara
                                  • Re: [PATCH v5] mm/gup: disallow GUP writing to file-backed mappings by default, Peter Zijlstra
                          • Re: [PATCH v5] mm/gup: disallow GUP writing to file-backed mappings by default, Lorenzo Stoakes
                            • Re: [PATCH v5] mm/gup: disallow GUP writing to file-backed mappings by default, David Hildenbrand
                              • Re: [PATCH v5] mm/gup: disallow GUP writing to file-backed mappings by default, Lorenzo Stoakes
                                • Re: [PATCH v5] mm/gup: disallow GUP writing to file-backed mappings by default, David Hildenbrand
                                  • Re: [PATCH v5] mm/gup: disallow GUP writing to file-backed mappings by default, John Hubbard
              • Re: [PATCH v5] mm/gup: disallow GUP writing to file-backed mappings by default, Peter Xu
                • Re: [PATCH v5] mm/gup: disallow GUP writing to file-backed mappings by default, David Hildenbrand
                • Re: [PATCH v5] mm/gup: disallow GUP writing to file-backed mappings by default, Jason Gunthorpe
                  • Re: [PATCH v5] mm/gup: disallow GUP writing to file-backed mappings by default, John Hubbard
        • Re: [PATCH v5] mm/gup: disallow GUP writing to file-backed mappings by default, Jason Gunthorpe
          • Re: [PATCH v5] mm/gup: disallow GUP writing to file-backed mappings by default, David Hildenbrand
      • Re: [PATCH v5] mm/gup: disallow GUP writing to file-backed mappings by default, Theodore Ts'o
        • Re: [PATCH v5] mm/gup: disallow GUP writing to file-backed mappings by default, Jason Gunthorpe
          • Re: [PATCH v5] mm/gup: disallow GUP writing to file-backed mappings by default, Theodore Ts'o
            • Re: [PATCH v5] mm/gup: disallow GUP writing to file-backed mappings by default, Jason Gunthorpe
              • Re: [PATCH v5] mm/gup: disallow GUP writing to file-backed mappings by default, Lorenzo Stoakes
              • Re: [PATCH v5] mm/gup: disallow GUP writing to file-backed mappings by default, Dave Chinner
                • Re: [PATCH v5] mm/gup: disallow GUP writing to file-backed mappings by default, Jason Gunthorpe
    • Re: [PATCH v5] mm/gup: disallow GUP writing to file-backed mappings by default, Lorenzo Stoakes
      • Re: [PATCH v5] mm/gup: disallow GUP writing to file-backed mappings by default, David Hildenbrand
        • Re: [PATCH v5] mm/gup: disallow GUP writing to file-backed mappings by default, Jens Axboe
          • Re: [PATCH v5] mm/gup: disallow GUP writing to file-backed mappings by default, Lorenzo Stoakes
        • Re: [PATCH v5] mm/gup: disallow GUP writing to file-backed mappings by default, Lorenzo Stoakes
          • Re: [PATCH v5] mm/gup: disallow GUP writing to file-backed mappings by default, David Hildenbrand
            • Re: [PATCH v5] mm/gup: disallow GUP writing to file-backed mappings by default, Lorenzo Stoakes
              • Re: [PATCH v5] mm/gup: disallow GUP writing to file-backed mappings by default, David Hildenbrand
• [GIT PULL] non-MM updates for 6.4-rc1, Andrew Morton
  • Re: [GIT PULL] non-MM updates for 6.4-rc1, pr-tracker-bot
• [GIT PULL] MM updates for 6.4-rc1, Andrew Morton
  • Re: [GIT PULL] MM updates for 6.4-rc1, Linus Torvalds
    • Re: [GIT PULL] MM updates for 6.4-rc1, Suren Baghdasaryan
      • Re: [GIT PULL] MM updates for 6.4-rc1, Linus Torvalds
        • Re: [GIT PULL] MM updates for 6.4-rc1, Suren Baghdasaryan
          • Re: [GIT PULL] MM updates for 6.4-rc1, Suren Baghdasaryan
            • Re: [GIT PULL] MM updates for 6.4-rc1, Linus Torvalds
              • Re: [GIT PULL] MM updates for 6.4-rc1, Suren Baghdasaryan
  • Re: [GIT PULL] MM updates for 6.4-rc1, pr-tracker-bot
  • Re: [GIT PULL] MM updates for 6.4-rc1, Linus Torvalds
    • Re: [GIT PULL] MM updates for 6.4-rc1, Linus Torvalds
    • Re: [GIT PULL] MM updates for 6.4-rc1, Christoph Hellwig
  • Re: [GIT PULL] MM updates for 6.4-rc1, Niklas Cassel
    • Re: [GIT PULL] MM updates for 6.4-rc1, Andrew Morton
      • Re: [GIT PULL] MM updates for 6.4-rc1, Keith Busch
• [PATCH RFC net-next/mm V2 0/2] page_pool: new approach for leak detection and shutdown phase, Jesper Dangaard Brouer
  • [PATCH RFC net-next/mm V2 1/2] page_pool: Remove workqueue in new shutdown scheme, Jesper Dangaard Brouer
    • Re: [PATCH RFC net-next/mm V2 1/2] page_pool: Remove workqueue in new shutdown scheme, Toke Høiland-Jørgensen
      • Re: [PATCH RFC net-next/mm V2 1/2] page_pool: Remove workqueue in new shutdown scheme, Jesper Dangaard Brouer
        • Re: [PATCH RFC net-next/mm V2 1/2] page_pool: Remove workqueue in new shutdown scheme, Toke Høiland-Jørgensen
      • Re: [PATCH RFC net-next/mm V2 1/2] page_pool: Remove workqueue in new shutdown scheme, Jesper Dangaard Brouer
      • Re: [PATCH RFC net-next/mm V2 1/2] page_pool: Remove workqueue in new shutdown scheme, Jesper Dangaard Brouer
  • [PATCH RFC net-next/mm V2 2/2] mm/page_pool: catch page_pool memory leaks, Jesper Dangaard Brouer
• [syzbot] [mm?] kernel BUG in folio_unlock, syzbot
  • Re: [syzbot] [mm?] kernel BUG in folio_unlock, Yang Shi
• [PATCH for v6.3 regression] mm/mremap: fix vm_pgoff in vma_merge() case 3, Vlastimil Babka
  • Re: [PATCH for v6.3 regression] mm/mremap: fix vm_pgoff in vma_merge() case 3, Vlastimil Babka
  • Re: [PATCH for v6.3 regression] mm/mremap: fix vm_pgoff in vma_merge() case 3, Greg KH
    • Re: [PATCH for v6.3 regression] mm/mremap: fix vm_pgoff in vma_merge() case 3, Vlastimil Babka
      • Re: [PATCH for v6.3 regression] mm/mremap: fix vm_pgoff in vma_merge() case 3, Linus Torvalds
        • Re: [PATCH for v6.3 regression] mm/mremap: fix vm_pgoff in vma_merge() case 3, Linus Torvalds
          • Re: [PATCH for v6.3 regression] mm/mremap: fix vm_pgoff in vma_merge() case 3, Vlastimil Babka
        • Re: [PATCH for v6.3 regression] mm/mremap: fix vm_pgoff in vma_merge() case 3, Greg KH
    • Re: [PATCH for v6.3 regression] mm/mremap: fix vm_pgoff in vma_merge() case 3, Jiri Slaby
• Re: [LSF/MM/BPF TOPIC] SLOB+SLAB allocators removal and future SLUB improvements, Vlastimil Babka
  • Re: [LSF/MM/BPF TOPIC] SLOB+SLAB allocators removal and future SLUB improvements, Binder Makin
• Re: [PATCH] mm/mempolicy: Fix use-after-free of VMA iterator, Sven Schnelle
  • Re: [PATCH] mm/mempolicy: Fix use-after-free of VMA iterator, Liam R. Howlett
    • Re: [PATCH] mm/mempolicy: Fix use-after-free of VMA iterator, Lorenzo Stoakes
      • Re: [PATCH] mm/mempolicy: Fix use-after-free of VMA iterator, Sven Schnelle
• [linux-next:master] BUILD SUCCESS WITH WARNING b7455b10da762f2d447678c88e37cc1eb6cb45ee, kernel test robot
• [LSF/MM/BPF TOPIC] The future of memory tiering, David Rientjes
  • Re: [LSF/MM/BPF TOPIC] The future of memory tiering, Frank van der Linden
    • Re: [LSF/MM/BPF TOPIC] The future of memory tiering, Wei Xu
  • Re: [LSF/MM/BPF TOPIC] The future of memory tiering, Huang, Ying
  • Re: [LSF/MM/BPF TOPIC] The future of memory tiering, Yang Shi
  • Re: [LSF/MM/BPF TOPIC] The future of memory tiering, Jason Gunthorpe
  • Re: [LSF/MM/BPF TOPIC] The future of memory tiering, John Hubbard
• [ext4 io hang] buffered write io hang in balance_dirty_pages, Ming Lei
  • Re: [ext4 io hang] buffered write io hang in balance_dirty_pages, Matthew Wilcox
    • Re: [ext4 io hang] buffered write io hang in balance_dirty_pages, Ming Lei
      • Re: [ext4 io hang] buffered write io hang in balance_dirty_pages, Baokun Li
        • Re: [ext4 io hang] buffered write io hang in balance_dirty_pages, Baokun Li
        • Re: [ext4 io hang] buffered write io hang in balance_dirty_pages, Ming Lei
          • Re: [ext4 io hang] buffered write io hang in balance_dirty_pages, Baokun Li
            • Re: [ext4 io hang] buffered write io hang in balance_dirty_pages, Ming Lei
              • Re: [ext4 io hang] buffered write io hang in balance_dirty_pages, Ming Lei
                • Re: [ext4 io hang] buffered write io hang in balance_dirty_pages, Baokun Li
                  • Re: [ext4 io hang] buffered write io hang in balance_dirty_pages, Theodore Ts'o
                    • Re: [ext4 io hang] buffered write io hang in balance_dirty_pages, Ming Lei
                      • Re: [ext4 io hang] buffered write io hang in balance_dirty_pages, Christoph Hellwig
                        • Re: [ext4 io hang] buffered write io hang in balance_dirty_pages, Ming Lei
                          • Re: [ext4 io hang] buffered write io hang in balance_dirty_pages, Christoph Hellwig
                            • Re: [ext4 io hang] buffered write io hang in balance_dirty_pages, Ming Lei
                              • Re: [ext4 io hang] buffered write io hang in balance_dirty_pages, Dave Chinner
                                • Re: [ext4 io hang] buffered write io hang in balance_dirty_pages, Darrick J. Wong
                                  • Re: [ext4 io hang] buffered write io hang in balance_dirty_pages, Dave Chinner
                                    • Re: [ext4 io hang] buffered write io hang in balance_dirty_pages, Darrick J. Wong
                      • Re: [ext4 io hang] buffered write io hang in balance_dirty_pages, Theodore Ts'o
                        • Re: [ext4 io hang] buffered write io hang in balance_dirty_pages, Dave Chinner
                    • Re: [ext4 io hang] buffered write io hang in balance_dirty_pages, Baokun Li
  • Re: [ext4 io hang] buffered write io hang in balance_dirty_pages, Dave Chinner
    • Re: [ext4 io hang] buffered write io hang in balance_dirty_pages, Matthew Wilcox
      • Re: [ext4 io hang] buffered write io hang in balance_dirty_pages, Dave Chinner
  • Re: [ext4 io hang] buffered write io hang in balance_dirty_pages, Keith Busch
    • Re: [ext4 io hang] buffered write io hang in balance_dirty_pages, Matthew Wilcox
    • Re: [ext4 io hang] buffered write io hang in balance_dirty_pages, Ming Lei
• [linux-next:pending-fixes] BUILD SUCCESS be56a31d3d651e8eb263715e370a80fe59214889, kernel test robot
• [RFC v3 00/21] Preserved-over-Kexec RAM, Anthony Yznaga
  • [RFC v3 02/21] mm: PKRAM: implement node load and save functions, Anthony Yznaga
  • [RFC v3 06/21] mm: PKRAM: link nodes by pfn before reboot, Anthony Yznaga
  • [RFC v3 08/21] PKRAM: track preserved pages in a physical mapping pagetable, Anthony Yznaga
  • [RFC v3 10/21] PKRAM: prepare for adding preserved ranges to memblock reserved, Anthony Yznaga
  • [RFC v3 12/21] PKRAM: free the preserved ranges list, Anthony Yznaga
  • [RFC v3 11/21] mm: PKRAM: reserve preserved memory at boot, Anthony Yznaga
  • [RFC v3 01/21] mm: add PKRAM API stubs and Kconfig, Anthony Yznaga
  • [RFC v3 20/21] x86/KASLR: PKRAM: support physical kaslr, Anthony Yznaga
  • [RFC v3 14/21] PKRAM: provide a way to ban pages from use by PKRAM, Anthony Yznaga
  • [RFC v3 21/21] x86/boot/compressed/64: use 1GB pages for mappings, Anthony Yznaga
    • Re: [RFC v3 21/21] x86/boot/compressed/64: use 1GB pages for mappings, H. Peter Anvin
      • Re: [RFC v3 21/21] x86/boot/compressed/64: use 1GB pages for mappings, Anthony Yznaga
  • [RFC v3 09/21] PKRAM: pass a list of preserved ranges to the next kernel, Anthony Yznaga
  • [RFC v3 15/21] kexec: PKRAM: prevent kexec clobbering preserved pages in some cases, Anthony Yznaga
  • [RFC v3 05/21] mm: PKRAM: implement byte stream operations, Anthony Yznaga
  • [RFC v3 07/21] mm: PKRAM: introduce super block, Anthony Yznaga
    • Re: [RFC v3 07/21] mm: PKRAM: introduce super block, Coiby Xu
      • Re: [RFC v3 07/21] mm: PKRAM: introduce super block, Anthony Yznaga
        • Re: [RFC v3 07/21] mm: PKRAM: introduce super block, Coiby Xu
          • Re: [RFC v3 07/21] mm: PKRAM: introduce super block, Anthony Yznaga
  • [RFC v3 17/21] kexec: PKRAM: avoid clobbering already preserved pages, Anthony Yznaga
  • [RFC v3 18/21] mm: PKRAM: allow preserved memory to be freed from userspace, Anthony Yznaga
  • [RFC v3 04/21] mm: PKRAM: implement folio stream operations, Anthony Yznaga
  • [RFC v3 19/21] PKRAM: disable feature when running the kdump kernel, Anthony Yznaga
  • [RFC v3 03/21] mm: PKRAM: implement object load and save functions, Anthony Yznaga
  • [RFC v3 16/21] PKRAM: provide a way to check if a memory range has preserved pages, Anthony Yznaga
  • [RFC v3 13/21] PKRAM: prevent inadvertent use of a stale superblock, Anthony Yznaga
  • Re: [RFC v3 00/21] Preserved-over-Kexec RAM, Gowans, James
    • Re: [RFC v3 00/21] Preserved-over-Kexec RAM, Anthony Yznaga
  • Re: [RFC v3 00/21] Preserved-over-Kexec RAM, Baoquan He
    • Re: [RFC v3 00/21] Preserved-over-Kexec RAM, Anthony Yznaga
• drivers/infiniband/hw/qedr/verbs.c:4238:33: sparse: sparse: incorrect type in assignment (different base types), kernel test robot