From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751758AbdG0JEI (ORCPT ); Thu, 27 Jul 2017 05:04:08 -0400 Received: from mail-wm0-f67.google.com ([74.125.82.67]:38469 "EHLO mail-wm0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751448AbdG0JEH (ORCPT ); Thu, 27 Jul 2017 05:04:07 -0400 From: Michal Hocko To: Andrew Morton Cc: David Rientjes , Johannes Weiner , Roman Gushchin , Tetsuo Handa , , LKML Subject: [PATCH 0/2] mm, oom: do not grant oom victims full memory reserves access Date: Thu, 27 Jul 2017 11:03:55 +0200 Message-Id: <20170727090357.3205-1-mhocko@kernel.org> X-Mailer: git-send-email 2.13.2 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, this is a part of a larger series I posted back in Oct last year [1]. I have dropped patch 3 because it was incorrect and patch 4 is not applicable without it. The primary reason to apply patch 1 is to remove a risk of the complete memory depletion by oom victims. While this is a theoretical risk right now there is a demand for memcg aware oom killer which might kill all processes inside a memcg which can be a lot of tasks. That would make the risk quite real. This issue is addressed by limiting access to memory reserves. We no longer use TIF_MEMDIE to grant the access and use tsk_is_oom_victim instead. See Patch 1 for more details. Patch 2 is a trivial follow up cleanup. I would still like to get rid of TIF_MEMDIE completely but I do not have time to do it now and it is not a pressing issue. [1] http://lkml.kernel.org/r/20161004090009.7974-1-mhocko@kernel.org