Re: cgroups iptables-restor: vmalloc: allocation failure

From: Georgi Nikolov
Date: Thu Jul 26 2018 - 02:53:32 EST


Servers are with 64bit kernel and 32bit userland.

here is the log:

[Â 485.467359] iptables-restor: vmalloc: allocation failure, allocated 2367488 of 3608576 bytes, mode:0x14010c0(GFP_KERNEL|__GFP_NORETRY), nodemask=(null)
[Â 485.467871] iptables-restor cpuset=/ mems_allowed=0
[Â 485.468089] CPU: 0 PID: 18093 Comm: iptables-restor Not tainted 4.14.50 #1
[Â 485.468399] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1 04/01/2014
[Â 485.468725]Â 0000000000000000 ffffffff81ed2b8b ffffffff8333a330 bb5cfe6a5a821e59
[Â 485.469114]Â 0000000000000000 ffffc90004aaba80 ffffffff811fa3ea ffffc90004aaba90
[Â 485.469422]Â ffffffff825e11d0 014010c000000000 ffffffff825e11d0 ffffc90004aaba18
[Â 485.469735] Call Trace:
[Â 485.469941]Â [<ffffffff81ed2b8b>] dump_stack+0x9a/0x10f
[Â 485.470159]Â [<ffffffff811fa3ea>] warn_alloc+0x18a/0x270
[Â 485.470379]Â [<ffffffff8124c9c1>] __vmalloc_node_range+0x251/0x470
[Â 485.470614]Â [<ffffffff8124ccfe>] ? __vmalloc_node_flags_caller+0x3e/0x70
[Â 485.470881]Â [<ffffffff8124ccfe>] __vmalloc_node_flags_caller+0x3e/0x70
[Â 485.471160]Â [<ffffffff81d7cebe>] ? xt_alloc_table_info+0x4e/0xa0
[Â 485.471395]Â [<ffffffff8121a1ca>] kvmalloc_node+0x7a/0xd0
[Â 485.471618]Â [<ffffffff81d7cebe>] xt_alloc_table_info+0x4e/0xa0
[Â 485.471849]Â [<ffffffff81e57357>] ? translate_compat_table.constprop.19+0x447/0x870
[Â 485.472197]Â [<ffffffff81e57357>] translate_compat_table.constprop.19+0x447/0x870
[Â 485.472514]Â [<ffffffff81e57917>] ? compat_do_replace.isra.10.constprop.18+0x197/0x370
[Â 485.472833]Â [<ffffffff81e57917>] compat_do_replace.isra.10.constprop.18+0x197/0x370
[Â 485.473230]Â [<ffffffff81e57b7b>] compat_do_ipt_set_ctl+0x8b/0xb0
[Â 485.473465]Â [<ffffffff81d643ea>] compat_nf_setsockopt+0x6a/0xd0
[Â 485.473701]Â [<ffffffff81df3ad3>] compat_ip_setsockopt+0x73/0xd0
[Â 485.473936]Â [<ffffffff81e2129c>] compat_raw_setsockopt+0x7c/0xd0
[Â 485.474208]Â [<ffffffff8123750c>] ? handle_mm_fault+0xec/0x240
[Â 485.474441]Â [<ffffffff81cd3852>] compat_sock_common_setsockopt+0x32/0x80
[Â 485.474689]Â [<ffffffff81d2ed6a>] compat_sys_setsockopt+0x9a/0x2e0
[Â 485.474926]Â [<ffffffff81d309e5>] compat_sys_socketcall+0x415/0x570
[Â 485.475197]Â [<ffffffff820018bc>] ? page_fault+0x5c/0x90
[Â 485.475416]Â [<ffffffff82000ae6>] ? retint_user+0x2b/0x2b
[Â 485.475638]Â [<ffffffff81d30b54>] ? rap_compat_sys_socketcall+0x14/0x40
[Â 485.475884]Â [<ffffffff81002391>] ? do_fast_syscall_32+0xe1/0x2f0
[Â 485.476170]Â [<ffffffff82001f03>] ? entry_SYSENTER_compat+0x93/0xa5
[Â 485.476414] Mem-Info:
[Â 485.476579] active_anon:79884 inactive_anon:103007 isolated_anon:0
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ active_file:54010 inactive_file:219014 isolated_file:0
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ unevictable:1822 dirty:22 writeback:0 unstable:0
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ slab_reclaimable:8637 slab_unreclaimable:25015
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ mapped:16094 shmem:2271 pagetables:1481 bounce:0
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ free:3459 free_pcp:180 free_cma:0
[Â 485.477691] Node 0 active_anon:320376kB inactive_anon:412028kB active_file:216040kB inactive_file:875844kB unevictable:7288kB isolated(anon):0kB isolated(file):0kB mapped:64376kB dirty:88kB writeback:0kB shmem:9084kB writeback_tmp:0kB unstable:0kB all_unreclaimable? no
[Â 485.478457] Node 0 DMA free:7896kB min:44kB low:56kB high:68kB active_anon:2324kB inactive_anon:0kB active_file:12kB inactive_file:5228kB unevictable:0kB writepending:0kB present:15992kB managed:15892kB mlocked:0kB kernel_stack:0kB pagetables:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB
[Â 485.479233] lowmem_reserve[]: 0 1963 1963 1963
[Â 485.479483] Node 0 DMA32 free:5364kB min:5644kB low:7652kB high:9660kB active_anon:317672kB inactive_anon:412028kB active_file:216028kB inactive_file:871340kB unevictable:7288kB writepending:88kB present:2080624kB managed:2015900kB mlocked:7288kB kernel_stack:5584kB pagetables:5924kB bounce:0kB free_pcp:1052kB local_pcp:720kB free_cma:0kB
[Â 485.480425] lowmem_reserve[]: 0 0 0 0
[Â 485.480612] Node 0 DMA: 38*4kB (UMEH) 54*8kB (MEH) 51*16kB (UMEH) 35*32kB (UMEH) 16*64kB (MEH) 12*128kB (MH) 7*256kB (UMEH) 0*512kB 1*1024kB (E) 0*2048kB 0*4096kB = 7896kB
[Â 485.481173] Node 0 DMA32: 12*4kB (MH) 16*8kB (H) 264*16kB (UH) 7*32kB (H) 6*64kB (H) 1*128kB (H) 0*256kB 1*512kB (H) 0*1024kB 0*2048kB 0*4096kB = 5648kB
[Â 485.481642] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=1048576kB
[Â 485.481975] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=2048kB
[Â 485.482309] 275972 total pagecache pages
[Â 485.482535] 0 pages in swap cache
[Â 485.482717] Swap cache stats: add 0, delete 0, find 0/0
[ 485.482937] Free swap = 1976316kB
[Â 485.483118] Total swap = 1976316kB
[Â 485.483300] 524154 pages RAM
[Â 485.483492] 0 pages HighMem/MovableOnly
[Â 485.483711] 16206 pages reserved
[Â 485.483889] 0 pages hwpoisoned


Georgi Nikolov

On 07/25/2018 10:42 PM, David Rientjes wrote:
On Wed, 25 Jul 2018, Georgi Nikolov wrote:


I posted a kernel bug and
i hope this is the correct place to discuss this.

Could you post the full allocation failure from the kernel log?  It's not 
possible to vmalloc any additional memory due to the memory pressure, so 
this is expected to fail but I'm curious as to the actual allocation that 
is triggering it.