Re: [RFC PATCH] mm/oom_kill: allow oom kill allocating task for non-global case

[Aaron Tomlin]

On Tue 2021-06-08 08:22 +0200, Michal Hocko wrote:
> OK. A full report (including the backtrace) would tell us more what is
> the source of the charge. I thought that most #PF charging paths use the
> same gfp mask as the allocation (which would include other flags on top
> of GFP_KERNEL) but it seems we just use GFP_KERNEL at many places.

The following is what I can provide for now:

  [ 8227.242706] Out of memory and no killable processes...
  [ 8227.242731] node invoked oom-killer: gfp_mask=0x6000c0(GFP_KERNEL), nodemask=(null), order=0, oom_score_adj=999
  [ 8227.242732] node cpuset=XXXX mems_allowed=0-1
  [ 8227.242736] CPU: 12 PID: 1703347 Comm: node Kdump: loaded Not tainted 4.18.0-193.51.1.el8_2.x86_64 #1
  [ 8227.242737] Hardware name: XXXX
  [ 8227.242738] Call Trace:
  [ 8227.242746]  dump_stack+0x5c/0x80
  [ 8227.242751]  dump_header+0x6e/0x27a
  [ 8227.242753]  out_of_memory.cold.31+0x39/0x8d
  [ 8227.242756]  mem_cgroup_out_of_memory+0x49/0x80
  [ 8227.242758]  try_charge+0x58c/0x780
  [ 8227.242761]  ? __alloc_pages_nodemask+0xef/0x280
  [ 8227.242763]  mem_cgroup_try_charge+0x8b/0x1a0
  [ 8227.242764]  mem_cgroup_try_charge_delay+0x1c/0x40
  [ 8227.242767]  do_anonymous_page+0xb5/0x360
  [ 8227.242770]  ? __switch_to_asm+0x35/0x70
  [ 8227.242772]  __handle_mm_fault+0x662/0x6a0
  [ 8227.242774]  handle_mm_fault+0xda/0x200
  [ 8227.242778]  __do_page_fault+0x22d/0x4e0
  [ 8227.242780]  do_page_fault+0x32/0x110
  [ 8227.242782]  ? page_fault+0x8/0x30
  [ 8227.242783]  page_fault+0x1e/0x30

-- 
Aaron Tomlin