On 2018/08/07 0:42, syzbot wrote: > Hello, > > syzbot has tested the proposed patch but the reproducer still triggered crash: > WARNING in try_charge > > Killed process 6410 (syz-executor5) total-vm:37708kB, anon-rss:2128kB, file-rss:0kB, shmem-rss:0kB > oom_reaper: reaped process 6410 (syz-executor5), now anon-rss:0kB, file-rss:0kB, shmem-rss:0kB > task=syz-executor5 pid=6410 invoked memcg oom killer. oom_victim=1 > ------------[ cut here ]------------ > Memory cgroup charge failed because of no reclaimable memory! This looks like a misconfiguration or a kernel bug. > WARNING: CPU: 1 PID: 6410 at mm/memcontrol.c:1707 mem_cgroup_oom mm/memcontrol.c:1706 [inline] > WARNING: CPU: 1 PID: 6410 at mm/memcontrol.c:1707 try_charge+0x734/0x1680 mm/memcontrol.c:2264 > Kernel panic - not syncing: panic_on_warn set ... Michal, this is "mm, oom: task_will_free_mem(current) should ignore MMF_OOM_SKIP for once." problem which you are refusing at https://www.spinics.net/lists/linux-mm/msg133774.html . -- To unsubscribe from this list: send the line "unsubscribe cgroups" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
