On Tue, Jun 24, 2014 at 11:06:15AM -0400, Dave Jones wrote: > > For things like the fuzz test runs I do, I'd have to patch this out. > > Things like migrate_pages() with bad arguments will trigger a page > allocation failure rather easily. Likewise set_mempolicy(), and a > handful of other vm syscalls.
I grepped logs for the last week. There's also a lot of non-obvious causes of page alloc failures. (Possibly because free memory had been filled with dirty huge pages), but here we can't even successfully alloc a single order 0 page. Traces from separate runs, on various kernels from the last week. page allocation failure: order:0, mode:0x280da dump_stack+0x4e/0x7a warn_alloc_failed+0xff/0x170 __alloc_pages_nodemask+0x78e/0xc90 alloc_pages_vma+0xaf/0x1c0 handle_mm_fault+0xa31/0xc50 ? default_wake_function+0x12/0x20 __do_page_fault+0x1c9/0x630 ? __acct_update_integrals+0x8b/0x120 ? preempt_count_sub+0xab/0x100 trace_do_page_fault+0x3d/0x130 trace_page_fault+0x22/0x30 page allocation failure: order:0, mode:0x200da dump_stack+0x4e/0x7a warn_alloc_failed+0xff/0x170 __alloc_pages_nodemask+0x78e/0xc90 alloc_pages_vma+0xaf/0x1c0 read_swap_cache_async+0x123/0x220 swapin_readahead+0x106/0x1d0 handle_mm_fault+0x9d5/0xc50 ? default_wake_function+0x12/0x20 ? autoremove_wake_function+0x2b/0x40 __do_page_fault+0x1c9/0x630 ? __wake_up+0x44/0x50 ? __acct_update_integrals+0x8b/0x120 ? preempt_count_sub+0xab/0x100 trace_do_page_fault+0x3d/0x130 trace_page_fault+0x22/0x30 page allocation failure: order:0, mode:0x280da dump_stack+0x4e/0x7a warn_alloc_failed+0xff/0x170 __alloc_pages_nodemask+0x78e/0xc90 alloc_pages_vma+0xaf/0x1c0 handle_mm_fault+0xa31/0xc50 ? follow_page_mask+0x1f0/0x320 __get_user_pages+0x22b/0x660 ? kmem_cache_alloc+0x183/0x210 __mlock_vma_pages_range+0x9e/0xd0 __mm_populate+0xca/0x180 vm_mmap_pgoff+0xd3/0xe0 SyS_mmap_pgoff+0x116/0x2c0 ? syscall_trace_enter+0x14d/0x2a0 SyS_mmap+0x22/0x30 tracesys+0xdd/0xe2 page allocation failure: order:0, mode:0x2084d0 dump_stack+0x4e/0x7a warn_alloc_failed+0xff/0x170 __alloc_pages_nodemask+0x78e/0xc90 alloc_pages_current+0xb1/0x160 pte_alloc_one+0x17/0x90 __pte_alloc+0x27/0x150 handle_mm_fault+0x68d/0xc50 ? follow_page_mask+0xcb/0x320 __get_user_pages+0x22b/0x660 ? kmem_cache_alloc+0x183/0x210 __mlock_vma_pages_range+0x9e/0xd0 __mm_populate+0xca/0x180 vm_mmap_pgoff+0xd3/0xe0 SyS_mmap_pgoff+0x116/0x2c0 ? syscall_trace_enter+0x14d/0x2a0 SyS_mmap+0x22/0x30 tracesys+0xdd/0xe2 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
