Re: [PATCH 0/2] oom, memcg: do not report racy no-eligible OOM

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: linux-mm@xxxxxxxxx
Subject: Re: [PATCH 0/2] oom, memcg: do not report racy no-eligible OOM
From: Michal Hocko <mhocko@xxxxxxxxxx>
Date: Wed, 9 Jan 2019 12:03:28 +0100
Cc: Tetsuo Handa <penguin-kernel@xxxxxxxxxxxxxxxxxxx>, Johannes Weiner <hannes@xxxxxxxxxxx>, Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>, LKML <linux-kernel@xxxxxxxxxxxxxxx>
In-reply-to: <20190107143802.16847-1-mhocko@kernel.org>
References: <20190107143802.16847-1-mhocko@kernel.org>
User-agent: Mutt/1.10.1 (2018-07-13)

Tetsuo,
can you confirm that these two patches are fixing the issue you have
reported please?
-- 
Michal Hocko
SUSE Labs

Follow-Ups:
- Re: [PATCH 0/2] oom, memcg: do not report racy no-eligible OOM
  - From: Tetsuo Handa

References:
- [PATCH 0/2] oom, memcg: do not report racy no-eligible OOM
  - From: Michal Hocko

Prev by Date: Re: [PATCH v7] mm/page_alloc.c: memory_hotplug: free pages as higher order
Next by Date: Re: [PATCH v7] mm/page_alloc.c: memory_hotplug: free pages as higher order
Previous by thread: Re: [PATCH 3/2] memcg: Facilitate termination of memcg OOM victims.
Next by thread: Re: [PATCH 0/2] oom, memcg: do not report racy no-eligible OOM
Index(es):
- Date
- Thread

[Index of Archives] [Linux ARM Kernel] [Linux ARM] [Linux Omap] [Fedora ARM] [IETF Annouce] [Bugtraq] [Linux OMAP] [Linux MIPS] [eCos] [Asterisk Internet PBX] [Linux API]

Powered by Linux