Fix ELF / FDPIC ELF core dumping, and use mmap_lock properly in there
Subsystems (10)
Jann Horn
reviewerv5 cover Fix ELF / FDPIC ELF core dumping, and use mmap_lock properly in there
new in v5:
- patches 1-3 and 6 are unchanged
- added patch 4: rework vma_dump_size() into a common helper (Linus)
- added patch 7: actually do the mmget_still_valid() removal (Linus)
- for now, let dump_vma_snapshot() take the mmap_lock in write mode instead of read mode to avoid the data race with stack expansion
new in v4:
- simplify patch 4/5 by replacing the heuristic for dumping the first pages of ELF mappings with what Linus suggested
At the moment, we have that rather ugly mmget_still_valid() helper to work around <https://crbug.com/project-zero/1790>: ELF core dumping doesn't take the mmap_sem while traversing the task's VMAs, and if anything (like userfaultfd) then remotely messes with the VMA tree, fireworks ensue. So at the moment we use mmget_still_valid() to bail out in any writers that might be operating on a remote mm's VMAs.
With this series, I'm trying to get rid of the need for that as cleanly as possible. ("cleanly" meaning "avoid holding the mmap_lock across unbounded sleeps".)
Patches 1, 2, 3 and 4 are relatively unrelated cleanups in the core dumping code.
Patches 5 and 6 implement the main change: Instead of repeatedly accessing the VMA list with sleeps in between, we snapshot it at the start with proper locking, and then later we just use our copy of the VMA list. This ensures that the kernel won't crash, that VMA metadata in the coredump is consistent even in the presence of concurrent modifications, and that any virtual addresses that aren't being concurrently modified have their contents show up in the core dump properly.
The disadvantage of this approach is that we need a bit more memory during core dumping for storing metadata about all VMAs.
At the end of the series, patch 7 removes the old workaround for this issue (mmget_still_valid()).
I have tested:
- Creating a simple core dump on X86-64 still works.
- The created coredump on X86-64 opens in GDB and looks plausible.
- X86-64 core dumps contain the first page for executable mappings at offset 0, and don't contain the first page for non-executable file mappings or executable mappings at offset !=0.
- NOMMU 32-bit ARM can still generate plausible-looking core dumps through the FDPIC implementation. (I can't test this with GDB because GDB is missing some structure definition for nommu ARM, but I've poked around in the hexdump and it looked decent.)
Jann Horn (7):
binfmt_elf_fdpic: Stop using dump_emit() on user pointers on !MMU
coredump: Let dump_emit() bail out on short writes
coredump: Refactor page range dumping into common helper
coredump: Rework elf/elf_fdpic vma_dump_size() into common helper binfmt_elf, binfmt_elf_fdpic: Use a VMA list snapshot mm/gup: Take mmap_lock in get_dump_page()
mm: Remove the now-unnecessary mmget_still_valid() hack
drivers/infiniband/core/uverbs_main.c | 3 - drivers/vfio/pci/vfio_pci.c | 38 ++-- fs/binfmt_elf.c | 238 +++----------------------- fs/binfmt_elf_fdpic.c | 162 +++--------------- fs/coredump.c | 236 +++++++++++++++++++++++-- fs/proc/task_mmu.c | 18 -- fs/userfaultfd.c | 28 +-- include/linux/coredump.h | 11 ++ include/linux/sched/mm.h | 25 --- mm/gup.c | 61 +++---- mm/khugepaged.c | 2 +- mm/madvise.c | 17 -- mm/mmap.c | 5 +- 13 files changed, 346 insertions(+), 498 deletions(-)
base-commit: 06a4ec1d9dc652e17ee3ac2ceb6c7cf6c2b75cdd
Signature · 1 line
2.28.0.297.g1956fa8f8d-goog
Jann Horn
reviewerPATCH v5 1/7 binfmt_elf_fdpic: Stop using dump_emit() on user pointers on !MMU
dump_emit() is for kernel pointers, and VMAs describe userspace memory. Let's be tidy here and avoid accessing userspace pointers under KERNEL_DS, even if it probably doesn't matter much on !MMU systems - especially given that it looks like we can just use the same get_dump_page() as on MMU if we move it out of the CONFIG_MMU block.
One small change we have to make in get_dump_page() is to use __get_user_pages_locked() instead of __get_user_pages(), since the latter doesn't exist on nommu. On mmu builds, __get_user_pages_locked() will just call __get_user_pages() for us.
--- fs/binfmt_elf_fdpic.c | 8 ------ mm/gup.c | 57 +++++++++++++++++++++---------------------- 2 files changed, 28 insertions(+), 37 deletions(-)
fs/binfmt_elf_fdpic.c +0 -8
@@ -1529,14 +1529,11 @@ static bool elf_fdpic_dump_segments(struct coredump_params *cprm)struct vm_area_struct *vma;for (vma = current->mm->mmap; vma; vma = vma->vm_next) { -#ifdef CONFIG_MMU unsigned long addr; -#endif if (!maydump (vma, cprm->mm_flags))continue ; -#ifdef CONFIG_MMU for (addr = vma->vm_start; addr < vma->vm_end; addr +=PAGE_SIZE ) {bool res;
@@ -1552,11 +1549,6 @@ static bool elf_fdpic_dump_segments(struct coredump_params *cprm)if (!res)return false; } -#else -if (!dump_emit (cprm, (void *) vma->vm_start, - vma->vm_end - vma->vm_start)) -return false; -#endif }return true; }
mm/gup.c +28 -29
69 lines not on this page · raw message
Signature · 1 line
2.28.0.297.g1956fa8f8d-goog
Jann Horn
reviewerPATCH v5 2/7 coredump: Let dump_emit() bail out on short writes
In reply to Jann Horndump_emit() has a retry loop, but there seems to be no way for that retry logic to actually be used; and it was also buggy, writing the same data repeatedly after a short write.
Let's just bail out on a short write.
--- fs/coredump.c | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-)
fs/coredump.c +11 -11
@@ -840,17 +840,17 @@ int dump_emit(struct coredump_params *cprm, const void *addr, int nr)ssize_t n;if (cprm->written + nr > cprm->limit)return 0 ; -while (nr) { -if (dump_interrupted ()) -return 0 ; - n =__kernel_write (file, addr, nr, &pos); -if (n <=0 ) -return 0 ; - file->f_pos = pos; - cprm->written += n; - cprm->pos += n; - nr -= n; - } + + +if (dump_interrupted ()) +return 0 ; + n =__kernel_write (file, addr, nr, &pos); +if (n != nr) +return 0 ; + file->f_pos = pos; + cprm->written += n; + cprm->pos += n; +return 1 ; }EXPORT_SYMBOL (dump_emit);
Signature · 1 line
2.28.0.297.g1956fa8f8d-goog
Jann Horn
reviewerPATCH v5 3/7 coredump: Refactor page range dumping into common helper
In reply to Jann HornBoth fs/binfmt_elf.c and fs/binfmt_elf_fdpic.c need to dump ranges of pages into the coredump file. Extract that logic into a common helper.
--- fs/binfmt_elf.c | 22 ++-------------------- fs/binfmt_elf_fdpic.c | 18 +++--------------- fs/coredump.c | 34 ++++++++++++++++++++++++++++++++++ include/linux/coredump.h | 2 ++ 4 files changed, 41 insertions(+), 35 deletions(-)
fs/binfmt_elf.c +2 -20
@@ -2419,26 +2419,8 @@ static int elf_core_dump(struct coredump_params *cprm)for (i =0 , vma =first_vma (current, gate_vma); vma !=NULL ; vma =next_vma (vma, gate_vma)) { -unsigned long addr; -unsigned long end; - - end = vma->vm_start + vma_filesz[i++]; - -for (addr = vma->vm_start; addr < end; addr +=PAGE_SIZE ) { -struct page *page; -int stop; - - page =get_dump_page (addr); -if (page) { -void *kaddr =kmap (page); - stop = !dump_emit (cprm, kaddr,PAGE_SIZE ); -kunmap (page); -put_page (page); - }else - stop = !dump_skip (cprm,PAGE_SIZE ); -if (stop) - goto end_coredump; - } +if (!dump_user_range (cprm, vma->vm_start, vma_filesz[i++])) + goto end_coredump; }dump_truncate (cprm);
fs/binfmt_elf_fdpic.c +3 -15
@@ -1534,21 +1534,9 @@ static bool elf_fdpic_dump_segments(struct coredump_params *cprm)if (!maydump (vma, cprm->mm_flags))continue ; -for (addr = vma->vm_start; addr < vma->vm_end; - addr +=PAGE_SIZE ) { -bool res; -struct page *page =get_dump_page (addr); -if (page) { -void *kaddr =kmap (page); - res =dump_emit (cprm, kaddr,PAGE_SIZE ); -kunmap (page); -put_page (page); - }else { - res =dump_skip (cprm,PAGE_SIZE ); - } -if (!res) -return false; - } +if (!dump_user_range (cprm, vma->vm_start, + vma->vma_end - vma->vm_start)) +return false; }return true; }
fs/coredump.c +34 -0
@@ -876,6 +876,40 @@ int dump_skip(struct coredump_params *cprm, size_t nr) }EXPORT_SYMBOL (dump_skip); +#ifdef CONFIG_ELF_CORE +int dump_user_range (struct coredump_params *cprm,unsigned long start, +unsigned long len) +{ +unsigned long addr; + +for (addr = start; addr < start + len; addr +=PAGE_SIZE ) { +struct page *page; +int stop; + +/* +* To avoid having to allocate page tables for virtual address +* ranges that have never been used yet, and also to make it +* easy to generate sparse core files, use a helper that returns +* NULL when encountering an empty page table entry that would +* otherwise have been filled with the zero page. +*/ + page =get_dump_page (addr); +if (page) { +void *kaddr =kmap (page); + + stop = !dump_emit (cprm, kaddr,PAGE_SIZE ); +kunmap (page); +put_page (page); + }else { + stop = !dump_skip (cprm,PAGE_SIZE ); + } +if (stop) +return 0 ; + } +return 1 ; +} +#endif +int dump_align (struct coredump_params *cprm,int align) {unsigned mod = cprm->pos & (align -1 );
include/linux/coredump.h +2 -0
@@ -16,6 +16,8 @@ extern int dump_skip(struct coredump_params *cprm, size_t nr);extern int dump_emit (struct coredump_params *cprm,const void *addr,int nr);extern int dump_align (struct coredump_params *cprm,int align);extern void dump_truncate (struct coredump_params *cprm); +int dump_user_range (struct coredump_params *cprm,unsigned long start, +unsigned long len);#ifdef CONFIG_COREDUMP extern void do_coredump (const kernel_siginfo_t *siginfo);#else
Signature · 1 line
2.28.0.297.g1956fa8f8d-goog
Jann Horn
reviewerPATCH v5 4/7 coredump: Rework elf/elf_fdpic vma_dump_size() into common helper
In reply to Jann HornAt the moment, the binfmt_elf and binfmt_elf_fdpic code have slightly different code to figure out which VMAs should be dumped, and if so, whether the dump should contain the entire VMA or just its first page.
Eliminate duplicate code by reworking the binfmt_elf version into a generic core dumping helper in coredump.c.
As part of that, change the heuristic for detecting executable/library header pages to check whether the inode is executable instead of looking at the file mode.
This is less problematic in terms of locking because it lets us avoid get_user() under the mmap_sem. (And arguably it looks nicer and makes more sense in generic code.)
Adjust a little bit based on the binfmt_elf_fdpic version:
->anon_vma is only meaningful under CONFIG_MMU, otherwise we have to assume that the VMA has been written to.
--- fs/binfmt_elf.c | 120 --------------------------------------- fs/binfmt_elf_fdpic.c | 83 ++------------------------- fs/coredump.c | 101 ++++++++++++++++++++++++++++++++ include/linux/coredump.h | 1 + 4 files changed, 106 insertions(+), 199 deletions(-)
fs/binfmt_elf.c +0 -120
@@ -1389,126 +1389,6 @@ static int load_elf_library(struct file *file)* Jeremy Fitzhardinge <[email protected]> */ -/* -* The purpose of always_dump_vma() is to make sure that special kernel mappings -* that are useful for post-mortem analysis are included in every core dump. -* In that way we ensure that the core dump is fully interpretable later -* without matching up the same kernel and hardware config to see what PC values -* meant. These special mappings include - vDSO, vsyscall, and other -* architecture specific mappings -*/ -static bool always_dump_vma (struct vm_area_struct *vma) -{ -/* Any vsyscall mappings? */ -if (vma ==get_gate_vma (vma->vm_mm)) -return true; - -/* -* Assume that all vmas with a .name op should always be dumped. -* If this changes, a new vm_ops field can easily be added. -*/ -if (vma->vm_ops && vma->vm_ops->name && vma->vm_ops->name (vma)) -return true; - -/* -* arch_vma_name() returns non-NULL for special architecture mappings, -* such as vDSO sections. -*/ -if (arch_vma_name (vma)) -return true; - -return false; -} - -/* -* Decide what to dump of a segment, part, all or none. -*/ -static unsigned long vma_dump_size (struct vm_area_struct *vma, -unsigned long mm_flags) -{ -#define FILTER (type) (mm_flags & (1UL << MMF_DUMP_##type)) - -/* always dump the vdso and vsyscall sections */ -if (always_dump_vma (vma)) - goto whole; - -if (vma->vm_flags &VM_DONTDUMP ) -return 0 ; - -/* support for DAX */ -if (vma_is_dax (vma)) { -if ((vma->vm_flags &VM_SHARED ) &&FILTER (DAX_SHARED )) - goto whole; -if (!(vma->vm_flags &VM_SHARED ) &&FILTER (DAX_PRIVATE )) - goto whole; -return 0 ; - } - -/* Hugetlb memory check */ -if (is_vm_hugetlb_page (vma)) { -if ((vma->vm_flags &VM_SHARED ) &&FILTER (HUGETLB_SHARED )) - goto whole; -if (!(vma->vm_flags &VM_SHARED ) &&FILTER (HUGETLB_PRIVATE )) - goto whole; -return 0 ; - } - -/* Do not dump I/O mapped devices or special mappings */ -if (vma->vm_flags &VM_IO ) -return 0 ; - -/* By default, dump shared memory if mapped from an anonymous file. */ -if (vma->vm_flags &VM_SHARED ) { -if (file_inode (vma->vm_file)->i_nlink ==0 ? -FILTER (ANON_SHARED ) :FILTER (MAPPED_SHARED )) - goto whole; -return 0 ; - } - -/* Dump segments that have been written to. */ -if (vma->anon_vma &&FILTER (ANON_PRIVATE )) - goto whole; -if (vma->vm_file ==NULL ) -return 0 ; - -if (FILTER (MAPPED_PRIVATE )) - goto whole; - -/* -* If this looks like the beginning of a DSO or executable mapping, -* check for an ELF header. If we find one, dump the first page to -* aid in determining what was mapped here. -*/ -if (FILTER (ELF_HEADERS ) && - vma->vm_pgoff ==0 && (vma->vm_flags &VM_READ )) { -u32 __user *header = (u32 __user *) vma->vm_start; -u32 word; -/* -* Doing it this way gets the constant folded by GCC. -*/ -union { -u32 cmp; -char elfmag[SELFMAG ]; - } magic; -BUILD_BUG_ON (SELFMAG !=sizeof word); - magic.elfmag[EI_MAG0 ] =ELFMAG0 ; - magic.elfmag[EI_MAG1 ] =ELFMAG1 ; - magic.elfmag[EI_MAG2 ] =ELFMAG2 ; - magic.elfmag[EI_MAG3 ] =ELFMAG3 ; -if (unlikely (get_user (word, header))) - word =0 ; -if (word == magic.cmp) -return PAGE_SIZE ; - } - -#undef FILTER - -return 0 ; - -whole: -return vma->vm_end - vma->vm_start; -} -/* An ELF note in memory */ struct memelfnote {
fs/binfmt_elf_fdpic.c +4 -79
108 lines not on this page · raw message
fs/coredump.c +101 -0
104 lines not on this page · raw message
include/linux/coredump.h +1 -0
@@ -16,6 +16,7 @@ extern int dump_skip(struct coredump_params *cprm, size_t nr);extern int dump_emit (struct coredump_params *cprm,const void *addr,int nr);extern int dump_align (struct coredump_params *cprm,int align);extern void dump_truncate (struct coredump_params *cprm); +unsigned long vma_dump_size (struct vm_area_struct *vma,unsigned long mm_flags);int dump_user_range (struct coredump_params *cprm,unsigned long start,unsigned long len);#ifdef CONFIG_COREDUMP
Signature · 1 line
2.28.0.297.g1956fa8f8d-goog
Jann Horn
reviewerPATCH v5 5/7 binfmt_elf, binfmt_elf_fdpic: Use a VMA list snapshot
In reply to Jann HornIn both binfmt_elf and binfmt_elf_fdpic, use a new helper dump_vma_snapshot() to take a snapshot of the VMA list (including the gate VMA, if we have one) while protected by the mmap_lock, and then use that snapshot instead of walking the VMA list without locking.
An alternative approach would be to keep the mmap_lock held across the entire core dumping operation; however, keeping the mmap_lock locked while we may be blocked for an unbounded amount of time (e.g. because we're dumping to a FUSE filesystem or so) isn't really optimal; the mmap_lock blocks things like the ->release handler of userfaultfd, and we don't really want critical system daemons to grind to a halt just because someone "gifted" them SCM_RIGHTS to an eternally-locked userfaultfd, or something like that.
Since both the normal ELF code and the FDPIC ELF code need this functionality (and if any other binfmt wants to add coredump support in the future, they'd probably need it, too), implement this with a common helper in fs/coredump.c.
A downside of this approach is that we now need a bigger amount of kernel memory per userspace VMA in the normal ELF case, and that we need O(n) kernel memory in the FDPIC ELF case at all; but 40 bytes per VMA shouldn't be terribly bad.
There currently is a data race between stack expansion and anything that reads ->vm_start or ->vm_end under the mmap_lock held in read mode; to mitigate that for core dumping, take the mmap_lock in write mode when taking a snapshot of the VMA hierarchy.
(If we only took the mmap_lock in read mode, we could end up with a corrupted core dump if someone does get_user_pages_remote() concurrently. Not really a major problem, but taking the mmap_lock either way works here, so we might as well avoid the issue.)
(This doesn't do anything about the existing data races with stack expansion in other mm code.)
--- fs/binfmt_elf.c | 100 +++++++++------------------------------ fs/binfmt_elf_fdpic.c | 67 +++++++++++--------------- fs/coredump.c | 81 ++++++++++++++++++++++++++++++- include/linux/coredump.h | 10 +++- 4 files changed, 138 insertions(+), 120 deletions(-)
fs/binfmt_elf.c +22 -78
@@ -2100,32 +2100,6 @@ static void free_note_info(struct elf_note_info *info)#endif -static struct vm_area_struct *first_vma (struct task_struct *tsk, -struct vm_area_struct *gate_vma) -{ -struct vm_area_struct *ret = tsk->mm->mmap; - -if (ret) -return ret; -return gate_vma; -} -/* -* Helper function for iterating across a vma list. It ensures that the caller -* will visit `gate_vma' prior to terminating the search. -*/ -static struct vm_area_struct *next_vma (struct vm_area_struct *this_vma, -struct vm_area_struct *gate_vma) -{ -struct vm_area_struct *ret; - - ret = this_vma->vm_next; -if (ret) -return ret; -if (this_vma == gate_vma) -return NULL ; -return gate_vma; -} -static void fill_extnum_info (struct elfhdr *elf,struct elf_shdr *shdr4extnum,elf_addr_t e_shoff,int segs) {
@@ -2152,9 +2126,8 @@ static void fill_extnum_info(struct elfhdr *elf, struct elf_shdr *shdr4extnum,static int elf_core_dump (struct coredump_params *cprm) {int has_dumped =0 ; -int segs, i; -size_t vma_data_size =0 ; -struct vm_area_struct *vma, *gate_vma; +int vma_count, segs, i; +size_t vma_data_size;struct elfhdr elf;loff_t offset =0 , dataoff;struct elf_note_info info = { };
@@ -2162,30 +2135,16 @@ static int elf_core_dump(struct coredump_params *cprm)struct elf_shdr *shdr4extnum =NULL ;Elf_Half e_phnum;elf_addr_t e_shoff; -elf_addr_t *vma_filesz =NULL ; +struct core_vma_metadata *vma_meta; + +if (dump_vma_snapshot (cprm, &vma_count, &vma_meta, &vma_data_size)) +return 0 ; -/* -* We no longer stop all VM operations. -* -* This is because those proceses that could possibly change map_count -* or the mmap / vma pages are now blocked in do_exit on current -* finishing this core dump. -* -* Only ptrace can touch these memory addresses, but it doesn't change -* the map_count or the pages allocated. So no possibility of crashing -* exists while dumping the mm->vm_next areas to the core file. -*/ -/* * The number of segs are recored into ELF header as 16bit value. * Please check DEFAULT_MAX_MAP_COUNT definition when you modify here. */ - segs = current->mm->map_count; - segs +=elf_core_extra_phdrs (); - - gate_vma =get_gate_vma (current->mm); -if (gate_vma !=NULL ) - segs++; + segs = vma_count +elf_core_extra_phdrs ();/* for notes section */ segs++;
@@ -2223,24 +2182,6 @@ static int elf_core_dump(struct coredump_params *cprm) dataoff = offset =roundup (offset,ELF_EXEC_PAGESIZE ); -/* -* Zero vma process will get ZERO_SIZE_PTR here. -* Let coredump continue for register state at least. -*/ - vma_filesz =kvmalloc (array_size (sizeof (*vma_filesz), (segs -1 )), -GFP_KERNEL ); -if (!vma_filesz) - goto end_coredump; - -for (i =0 , vma =first_vma (current, gate_vma); vma !=NULL ; - vma =next_vma (vma, gate_vma)) { -unsigned long dump_size; - - dump_size =vma_dump_size (vma, cprm->mm_flags); - vma_filesz[i++] = dump_size; - vma_data_size += dump_size; - } - offset += vma_data_size; offset +=elf_core_extra_data_size (); e_shoff = offset;
@@ -2261,21 +2202,23 @@ static int elf_core_dump(struct coredump_params *cprm) goto end_coredump;/* Write program headers for segments dump */ -for (i =0 , vma =first_vma (current, gate_vma); vma !=NULL ; - vma =next_vma (vma, gate_vma)) { +for (i =0 ; i < vma_count; i++) { +struct core_vma_metadata *meta = vma_meta + i;struct elf_phdr phdr; phdr.p_type =PT_LOAD ; phdr.p_offset = offset; - phdr.p_vaddr = vma->vm_start; + phdr.p_vaddr = meta->start; phdr.p_paddr =0 ; - phdr.p_filesz = vma_filesz[i++]; - phdr.p_memsz = vma->vm_end - vma->vm_start; + phdr.p_filesz = meta->dump_size; + phdr.p_memsz = meta->end - meta->start; offset += phdr.p_filesz; - phdr.p_flags = vma->vm_flags &VM_READ ?PF_R :0 ; -if (vma->vm_flags &VM_WRITE ) + phdr.p_flags =0 ; +if (meta->flags &VM_READ ) + phdr.p_flags |=PF_R ; +if (meta->flags &VM_WRITE ) phdr.p_flags |=PF_W ; -if (vma->vm_flags &VM_EXEC ) +if (meta->flags &VM_EXEC ) phdr.p_flags |=PF_X ; phdr.p_align =ELF_EXEC_PAGESIZE ;
@@ -2297,9 +2240,10 @@ static int elf_core_dump(struct coredump_params *cprm)if (!dump_skip (cprm, dataoff - cprm->pos)) goto end_coredump; -for (i =0 , vma =first_vma (current, gate_vma); vma !=NULL ; - vma =next_vma (vma, gate_vma)) { -if (!dump_user_range (cprm, vma->vm_start, vma_filesz[i++])) +for (i =0 ; i < vma_count; i++) { +struct core_vma_metadata *meta = vma_meta + i; + +if (!dump_user_range (cprm, meta->start, meta->dump_size)) goto end_coredump; }dump_truncate (cprm);
@@ -2315,7 +2259,7 @@ static int elf_core_dump(struct coredump_params *cprm) end_coredump:free_note_info (&info);kfree (shdr4extnum); -kvfree (vma_filesz); +kvfree (vma_meta);kfree (phdr4note);return has_dumped; }
fs/binfmt_elf_fdpic.c +27 -40
140 lines not on this page · raw message
fs/coredump.c +80 -1
90 lines not on this page · raw message
include/linux/coredump.h +9 -1
@@ -7,6 +7,12 @@#include <linux/fs.h> #include <asm/siginfo.h> +struct core_vma_metadata { +unsigned long start, end; +unsigned long flags; +unsigned long dump_size; +}; +/* * These are the only things you should do on a core-file: use only these * functions to write out all the necessary info.
@@ -16,9 +22,11 @@ extern int dump_skip(struct coredump_params *cprm, size_t nr);extern int dump_emit (struct coredump_params *cprm,const void *addr,int nr);extern int dump_align (struct coredump_params *cprm,int align);extern void dump_truncate (struct coredump_params *cprm); -unsigned long vma_dump_size (struct vm_area_struct *vma,unsigned long mm_flags);int dump_user_range (struct coredump_params *cprm,unsigned long start,unsigned long len); +int dump_vma_snapshot (struct coredump_params *cprm,int *vma_count, +struct core_vma_metadata **vma_meta, +size_t *vma_data_size_ptr);#ifdef CONFIG_COREDUMP extern void do_coredump (const kernel_siginfo_t *siginfo);#else
Signature · 1 line
2.28.0.297.g1956fa8f8d-goog
Jann Horn
reviewerPATCH v5 6/7 mm/gup: Take mmap_lock in get_dump_page()
In reply to Jann HornProperly take the mmap_lock before calling into the GUP code from get_dump_page(); and play nice, allowing the GUP code to drop the mmap_lock if it has to sleep.
As Linus pointed out, we don't actually need the VMA because __get_user_pages() will flush the dcache for us if necessary.
--- mm/gup.c | 16 ++++++++++------ 1 file changed, 10 insertions(+), 6 deletions(-)
mm/gup.c +10 -6
@@ -1552,19 +1552,23 @@ static long __get_user_pages_locked(struct mm_struct *mm, unsigned long start,* NULL wherever the ZERO_PAGE, or an anonymous pte_none, has been found - * allowing a hole to be left in the corefile to save diskspace. * -* Called without mmap_lock, but after all other threads have been killed. +* Called without mmap_lock (takes and releases the mmap_lock by itself). */ #ifdef CONFIG_ELF_CORE struct page *get_dump_page (unsigned long addr) { -struct vm_area_struct *vma; +struct mm_struct *mm = current->mm;struct page *page; +int locked =1 ; +int ret; -if (__get_user_pages_locked (current->mm, addr,1 , &page, &vma,NULL , -FOLL_FORCE |FOLL_DUMP |FOLL_GET ) <1 ) +if (mmap_read_lock_killable (mm))return NULL ; -flush_cache_page (vma, addr,page_to_pfn (page)); -return page; + ret =__get_user_pages_locked (mm, addr,1 , &page,NULL , &locked, +FOLL_FORCE |FOLL_DUMP |FOLL_GET ); +if (locked) +mmap_read_unlock (mm); +return (ret ==1 ) ? page :NULL ; }#endif /* CONFIG_ELF_CORE */
Signature · 1 line
2.28.0.297.g1956fa8f8d-goog
Re: [PATCH v5 6/7] mm/gup: Take mmap_lock in get_dump_page()
Quoted 4 lines · Jann Horn
Properly take the
mmap_lockbefore calling into the GUP code fromget_dump_page(); and play nice, allowing the GUP code to drop themmap_lockif it has to sleep.
Hmm. Of all the patches in the series, this simple one is now the only one I feel makes for ugly code. Certainly not uglier than it used to be, but also not as pretty as it could be..
I think you're pretty much just re-implementingget_user_pages_unlocked(), aren't you?
There are differences - you use mmap_read_lock_killable(), for example. But I think get_user_pages_unlocked() should too.
The other difference is that you don't set FOLL_TOUCH. So it's not *exactly* the same thing, but it's close enough that I get the feeling that this should be cleaned up to use a common helper between the two.
That said, I suspect that falls under the heading of "future cleanup". I don't think there's any need to re-spin this series for this, it's just the only slightly negative reaction I had for the whole series now.
Linus
Jann Horn
reviewerPATCH v5 7/7 mm: Remove the now-unnecessary mmget_still_valid() hack
In reply to Jann HornThe preceding patches have ensured that core dumping properly takes the mmap_lock. Thanks to that, we can now remove mmget_still_valid() and all its users.
--- drivers/infiniband/core/uverbs_main.c | 3 --- drivers/vfio/pci/vfio_pci.c | 38 +++++++++++++-------------- fs/proc/task_mmu.c | 18 ------------- fs/userfaultfd.c | 28 +++++++------------- include/linux/sched/mm.h | 25 ------------------ mm/khugepaged.c | 2 +- mm/madvise.c | 17 ------------ mm/mmap.c | 5 +--- 8 files changed, 29 insertions(+), 107 deletions(-)
drivers/infiniband/core/uverbs_main.c +0 -3
@@ -845,8 +845,6 @@ void uverbs_user_mmap_disassociate(struct ib_uverbs_file *ufile)* will only be one mm, so no big deal. */ mmap_read_lock (mm); -if (!mmget_still_valid (mm)) - goto skip_mm;mutex_lock (&ufile->umap_lock);list_for_each_entry_safe (priv, next_priv, &ufile->umaps, list) {
@@ -865,7 +863,6 @@ void uverbs_user_mmap_disassociate(struct ib_uverbs_file *ufile) } }mutex_unlock (&ufile->umap_lock); - skip_mm:mmap_read_unlock (mm);mmput (mm); }
drivers/vfio/pci/vfio_pci.c +18 -20
@@ -1480,31 +1480,29 @@ static int vfio_pci_zap_and_vma_lock(struct vfio_pci_device *vdev, bool try) }else {mmap_read_lock (mm); } -if (mmget_still_valid (mm)) { -if (try) { -if (!mutex_trylock (&vdev->vma_lock)) { -mmap_read_unlock (mm); -mmput (mm); -return 0 ; - } - }else { -mutex_lock (&vdev->vma_lock); +if (try) { +if (!mutex_trylock (&vdev->vma_lock)) { +mmap_read_unlock (mm); +mmput (mm); +return 0 ; } -list_for_each_entry_safe (mmap_vma, tmp, - &vdev->vma_list, vma_next) { -struct vm_area_struct *vma = mmap_vma->vma; + }else { +mutex_lock (&vdev->vma_lock); + } +list_for_each_entry_safe (mmap_vma, tmp, + &vdev->vma_list, vma_next) { +struct vm_area_struct *vma = mmap_vma->vma; -if (vma->vm_mm != mm) -continue ; +if (vma->vm_mm != mm) +continue ; -list_del (&mmap_vma->vma_next); -kfree (mmap_vma); +list_del (&mmap_vma->vma_next); +kfree (mmap_vma); -zap_vma_ptes (vma, vma->vm_start, - vma->vm_end - vma->vm_start); - } -mutex_unlock (&vdev->vma_lock); +zap_vma_ptes (vma, vma->vm_start, + vma->vm_end - vma->vm_start); } +mutex_unlock (&vdev->vma_lock);mmap_read_unlock (mm);mmput (mm); }
fs/proc/task_mmu.c +0 -18
@@ -1168,24 +1168,6 @@ static ssize_t clear_refs_write(struct file *file, const char __user *buf, count = -EINTR ; goto out_mm; } -/* -* Avoid to modify vma->vm_flags -* without locked ops while the -* coredump reads the vm_flags. -*/ -if (!mmget_still_valid (mm)) { -/* -* Silently return "count" -* like if get_task_mm() -* failed. FIXME: should this -* function have returned -* -ESRCH if get_task_mm() -* failed like if -* get_proc_task() fails? -*/ -mmap_write_unlock (mm); - goto out_mm; - }for (vma = mm->mmap; vma; vma = vma->vm_next) { vma->vm_flags &= ~VM_SOFTDIRTY ;vma_set_page_prot (vma);
fs/userfaultfd.c +9 -19
@@ -601,8 +601,6 @@ static void userfaultfd_event_wait_completion(struct userfaultfd_ctx *ctx,/* the various vma->vm_userfaultfd_ctx still points to it */ mmap_write_lock (mm); -/* no task can run (and in turn coredump) yet */ -VM_WARN_ON (!mmget_still_valid (mm));for (vma = mm->mmap; vma; vma = vma->vm_next)if (vma->vm_userfaultfd_ctx.ctx == release_new_ctx) { vma->vm_userfaultfd_ctx =NULL_VM_UFFD_CTX ;
@@ -842,7 +840,6 @@ static int userfaultfd_release(struct inode *inode, struct file *file)/* len == 0 means wake all */ struct userfaultfd_wake_range range = { .len =0 , };unsigned long new_flags; -bool still_valid;WRITE_ONCE (ctx->released, true);
@@ -858,7 +855,6 @@ static int userfaultfd_release(struct inode *inode, struct file *file)* taking the mmap_lock for writing. */ mmap_write_lock (mm); - still_valid =mmget_still_valid (mm); prev =NULL ;for (vma = mm->mmap; vma; vma = vma->vm_next) {cond_resched ();
@@ -869,17 +865,15 @@ static int userfaultfd_release(struct inode *inode, struct file *file)continue ; } new_flags = vma->vm_flags & ~(VM_UFFD_MISSING |VM_UFFD_WP ); -if (still_valid) { - prev =vma_merge (mm, prev, vma->vm_start, vma->vm_end, - new_flags, vma->anon_vma, - vma->vm_file, vma->vm_pgoff, -vma_policy (vma), -NULL_VM_UFFD_CTX ); -if (prev) - vma = prev; -else - prev = vma; - } + prev =vma_merge (mm, prev, vma->vm_start, vma->vm_end, + new_flags, vma->anon_vma, + vma->vm_file, vma->vm_pgoff, +vma_policy (vma), +NULL_VM_UFFD_CTX ); +if (prev) + vma = prev; +else + prev = vma; vma->vm_flags = new_flags; vma->vm_userfaultfd_ctx =NULL_VM_UFFD_CTX ; }
@@ -1309,8 +1303,6 @@ static int userfaultfd_register(struct userfaultfd_ctx *ctx, goto out;mmap_write_lock (mm); -if (!mmget_still_valid (mm)) - goto out_unlock; vma =find_vma_prev (mm, start, &prev);if (!vma) goto out_unlock;
@@ -1511,8 +1503,6 @@ static int userfaultfd_unregister(struct userfaultfd_ctx *ctx, goto out;mmap_write_lock (mm); -if (!mmget_still_valid (mm)) - goto out_unlock; vma =find_vma_prev (mm, start, &prev);if (!vma) goto out_unlock;
include/linux/sched/mm.h +0 -25
@@ -49,31 +49,6 @@ static inline void mmdrop(struct mm_struct *mm)__mmdrop (mm); } -/* -* This has to be called after a get_task_mm()/mmget_not_zero() -* followed by taking the mmap_lock for writing before modifying the -* vmas or anything the coredump pretends not to change from under it. -* -* It also has to be called when mmgrab() is used in the context of -* the process, but then the mm_count refcount is transferred outside -* the context of the process to run down_write() on that pinned mm. -* -* NOTE: find_extend_vma() called from GUP context is the only place -* that can modify the "mm" (notably the vm_start/end) under mmap_lock -* for reading and outside the context of the process, so it is also -* the only case that holds the mmap_lock for reading that must call -* this function. Generally if the mmap_lock is hold for reading -* there's no need of this check after get_task_mm()/mmget_not_zero(). -* -* This function can be obsoleted and the check can be removed, after -* the coredump code will hold the mmap_lock for writing before -* invoking the ->core_dump methods. -*/ -static inline bool mmget_still_valid (struct mm_struct *mm) -{ -return likely (!mm->core_state); -} -/** * mmget() - Pin the address space associated with a &struct mm_struct. * @mm: The address space to pin.
mm/khugepaged.c +1 -1
@@ -431,7 +431,7 @@ static void insert_to_mm_slots_hash(struct mm_struct *mm,static inline int khugepaged_test_exit (struct mm_struct *mm) { -return atomic_read (&mm->mm_users) ==0 || !mmget_still_valid (mm); +return atomic_read (&mm->mm_users) ==0 ; } static bool hugepage_vma_check(struct vm_area_struct *vma,
mm/madvise.c +0 -17
@@ -1091,23 +1091,6 @@ int do_madvise(unsigned long start, size_t len_in, int behavior)if (write) {if (mmap_write_lock_killable (current->mm))return -EINTR ; - -/* -* We may have stolen the mm from another process -* that is undergoing core dumping. -* -* Right now that's io_ring, in the future it may -* be remote process management and not "current" -* at all. -* -* We need to fix core dumping to not do this, -* but for now we have the mmget_still_valid() -* model. -*/ -if (!mmget_still_valid (current->mm)) { -mmap_write_unlock (current->mm); -return -EINTR ; - } }else {mmap_read_lock (current->mm); }
mm/mmap.c +1 -4
@@ -2552,7 +2552,7 @@ find_extend_vma(struct mm_struct *mm, unsigned long addr)if (vma && (vma->vm_start <= addr))return vma;/* don't alter vm_end if the coredump is running */ -if (!prev || !mmget_still_valid (mm) ||expand_stack (prev, addr)) +if (!prev ||expand_stack (prev, addr))return NULL ;if (prev->vm_flags &VM_LOCKED )populate_vma_page_range (prev, addr, prev->vm_end,NULL );
@@ -2578,9 +2578,6 @@ find_extend_vma(struct mm_struct *mm, unsigned long addr)return vma;if (!(vma->vm_flags &VM_GROWSDOWN ))return NULL ; -/* don't alter vm_start if the coredump is running */ -if (!mmget_still_valid (mm)) -return NULL ; start = vma->vm_start;if (expand_stack (vma, addr))return NULL ;
Signature · 1 line
2.28.0.297.g1956fa8f8d-goog
Re: [PATCH v5 7/7] mm: Remove the now-unnecessary mmget_still_valid() hack
Quoted 3 lines · Jann Horn
The preceding patches have ensured that core dumping properly takes the
mmap_lock. Thanks to that, we can now removemmget_still_valid()and all its users.
Hi Jann, while the only tears to be shed over losing mmget_still_valid() will be tears of joy, I think you need to explain why you believe it's safe to remove the instance in mm/khugepaged.c: which you'll have found I moved just recently, to cover an extra case (sorry for not Cc'ing you).
mm/khugepaged.c static void insert_to_mm_slots_hash(struct mm_struct *mm, · line 437
Quoted 11 lines
mm/khugepaged.c +1
-1@@ -431,7 +431,7 @@ static void insert_to_mm_slots_hash(struct mm_struct *mm,static inline int khugepaged_test_exit (struct mm_struct *mm) { -return atomic_read (&mm->mm_users) ==0 || !mmget_still_valid (mm); +return atomic_read (&mm->mm_users) ==0 ; } static bool hugepage_vma_check(struct vm_area_struct *vma,
The movement (which you have correctly followed) was in bbe98f9cadff ("khugepaged: khugepaged_test_exit() check mmget_still_valid()") but the "pmd .. physical page 0" issue is explained better in its parent 18e77600f7a1 ("khugepaged: retract_page_tables() remember to test exit")
I think your core dumping is still reading the page tables without holding mmap_lock, so still vulnerable to that extra issue. It won't be as satisfying as removing all traces of mmget_still_valid(), but right now I think you should add an mm->core_state check there instead.
(I do have a better solution in use, but it's a much larger patch, that will take a lot more effort to get in: checks in pte_offset_map_lock(), perhaps returning NULL when pmd is transitioning, requiring retry.)
Or maybe it's me who has missed what you're doing instead.
Hugh
Jann Horn
reviewerRe: [PATCH v5 7/7] mm: Remove the now-unnecessary mmget_still_valid() hack
Quoted 28 lines · Hugh Dickins
Quoted 3 lines · Jann Horn
The preceding patches have ensured that core dumping properly takes the
mmap_lock. Thanks to that, we can now removemmget_still_valid()and all its users.Hi Jann, while the only tears to be shed over losing
mmget_still_valid()will be tears of joy, I think you need to explain why you believe it's safe to remove the instance inmm/khugepaged.c: which you'll have found I moved just recently, to cover an extra case (sorry for not Cc'ing you).mm/khugepaged.c static void insert_to_mm_slots_hash(struct mm_struct *mm, · line 437
Quoted 11 lines
mm/khugepaged.c +1
-1@@ -431,7 +431,7 @@ static void insert_to_mm_slots_hash(struct mm_struct *mm,static inline int khugepaged_test_exit (struct mm_struct *mm) { -return atomic_read (&mm->mm_users) ==0 || !mmget_still_valid (mm); +return atomic_read (&mm->mm_users) ==0 ; } static bool hugepage_vma_check(struct vm_area_struct *vma,The movement (which you have correctly followed) was in
bbe98f9cadff("khugepaged:khugepaged_test_exit()checkmmget_still_valid()") but the "pmd .. physical page 0" issue is explained better in its parent18e77600f7a1("khugepaged:retract_page_tables()remember to test exit")
Quoted 2 lines
I think your core dumping is still reading the page tables without holding
mmap_lock
Where? get_dump_page() takes mmap_lock now:
<https://lore.kernel.org/lkml/[email protected]/>
I don't think there should be any paths into __get_user_pages() left that don't hold the mmap_lock. Actually, we should probably try sticking mmap_assert_locked() in there now as a follow-up?
Quoted 7 lines
so still vulnerable to that extra issue. It won't
be as satisfying as removing all traces ofmmget_still_valid(), but right now I think you should add anmm->core_statecheck there instead.(I do have a better solution in use, but it's a much larger patch, that will take a lot more effort to get in: checks in
pte_offset_map_lock(), perhaps returning NULL when pmd is transitioning, requiring retry.)
Just to clarify: This is an issue only between GUP's software page table walks when running without mmap_lock and concurrent page table modifications from hugepage code, correct? Hardware page table walks and get_user_pages_fast() are fine because they properly load PTEs atomically and are written to assume that the page tables can change arbitrarily under them, and the only guarantee is that disabling interrupts ensures that pages referenced by PTEs can't be freed, right?
Quoted 3 lines
Or maybe it's me who has missed what you're doing instead.
Hugh
Re: [PATCH v5 7/7] mm: Remove the now-unnecessary mmget_still_valid() hack
Quoted 29 lines · Jann Horn
Quoted 28 lines · Hugh Dickins
Quoted 3 lines · Jann Horn
The preceding patches have ensured that core dumping properly takes the
mmap_lock. Thanks to that, we can now removemmget_still_valid()and all its users.Hi Jann, while the only tears to be shed over losing
mmget_still_valid()will be tears of joy, I think you need to explain why you believe it's safe to remove the instance inmm/khugepaged.c: which you'll have found I moved just recently, to cover an extra case (sorry for not Cc'ing you).mm/khugepaged.c static void insert_to_mm_slots_hash(struct mm_struct *mm, · line 437
Quoted 11 lines
mm/khugepaged.c +1
-1@@ -431,7 +431,7 @@ static void insert_to_mm_slots_hash(struct mm_struct *mm,static inline int khugepaged_test_exit (struct mm_struct *mm) { -return atomic_read (&mm->mm_users) ==0 || !mmget_still_valid (mm); +return atomic_read (&mm->mm_users) ==0 ; } static bool hugepage_vma_check(struct vm_area_struct *vma,The movement (which you have correctly followed) was in
bbe98f9cadff("khugepaged:khugepaged_test_exit()checkmmget_still_valid()") but the "pmd .. physical page 0" issue is explained better in its parent18e77600f7a1("khugepaged:retract_page_tables()remember to test exit")
Quoted 5 lines
Quoted 2 lines
I think your core dumping is still reading the page tables without holding
mmap_lockWhere?
get_dump_page()takesmmap_locknow:
<https://lore.kernel.org/lkml/[email protected]/>
Right, sorry for the noise, that's precisely what 6/7 is all about, and properly declares itself there in its Subject - I plead that I got distracted by the vma snapshot part of the series, and paid too little attention before bleating.
Looks good to me - thanks.
Quoted 4 lines
I don't think there should be any paths into
__get_user_pages()left that don't hold themmap_lock. Actually, we should probably try stickingmmap_assert_locked()in there now as a follow-up?
Maybe: I haven't given it thought, to be honest.
Hugh
Re: [PATCH v5 7/7] mm: Remove the now-unnecessary mmget_still_valid() hack
In reply to Jann HornI didn't answer your questions further down, sorry, resuming...
Quoted 1 line · Jann Horn
On Mon, Aug 31, 2020 at 8:07 AM Hugh Dickins <[email protected]> wrote:
...
Quoted 2 lines
Quoted 2 lines
but the "pmd .. physical page 0" issue is explained better in its parent
18e77600f7a1("khugepaged:retract_page_tables()remember to test exit")
...
Quoted 1 line
Just to clarify: This is an issue only between GUP's software page
Not just GUP's software page table walks: any of our software page table walks that could occur concurrently (notably, unmapping when exiting).
Quoted 2 lines
table walks when running without
mmap_lockand concurrent page table modifications from hugepage code, correct?
Correct.
Quoted 1 line
Hardware page table walks
Have no problem: the necessary TLB flush is already done.
Quoted 5 lines
and
get_user_pages_fast()are fine because they properly load PTEs atomically and are written to assume that the page tables can change arbitrarily under them, and the only guarantee is that disabling interrupts ensures that pages referenced by PTEs can't be freed, right?
mm/gup.c has changed a lot since I was familiar with it, and I'm out of touch with the history of architectural variants. I think internal_get_user_pages_fast() is now the place to look, and I see
local_irq_save(flags); gup_pgd_range(addr, end, fast_flags, pages, &nr_pinned); local_irq_restore(flags);
reassuringly there, which is how x86 always used to do it, and the dependence of x86 TLB flush on IPIs made it all safe.
Looking at gup_pmd_range(), its operations on pmd (= READ_ONCE(*pmdp)) look correct to me, and where I said "any of our software page table walks" above, there should be an exception for GUP_fast.
But the other software page table walks are more loosely coded, and less able to fall back - if gup_pmd_range() catches sight of a fleeting *pmdp 0, it rightly just gives up immediately on !pmd_present(pmd); whereas tearing down a userspace mapping needs to wait or retry on seeing a transient state (but mmap_lock happens to give protection against that particular transient state).
I assume that all the architectures which support GUP_fast have now been gathered into the same mechanism (perhaps by an otherwise superfluous IPI on TLB flush?) and are equally safe.
Hugh
Quoted 2 lines · Jann Horn
13 files changed, 346 insertions(+), 498 deletions(-)
Me likey. I had one comment, but I don't think it really matters for this series. So ack to all of these as far as I'm concerned.
Does anybody else see any problems?
Linus