Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932712AbcCVLAz (ORCPT ); Tue, 22 Mar 2016 07:00:55 -0400 Received: from mail-wm0-f66.google.com ([74.125.82.66]:35005 "EHLO mail-wm0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932607AbcCVLAl (ORCPT ); Tue, 22 Mar 2016 07:00:41 -0400 From: Michal Hocko To: Andrew Morton Cc: , LKML , Tetsuo Handa , David Rientjes , Ingo Molnar , Johannes Weiner , Mel Gorman , Michal Hocko , Oleg Nesterov , Peter Zijlstra , Vladimir Davydov Subject: [PATCH 0/9] oom reaper v6 Date: Tue, 22 Mar 2016 12:00:17 +0100 Message-Id: <1458644426-22973-1-git-send-email-mhocko@kernel.org> X-Mailer: git-send-email 2.7.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1647 Lines: 34 Hi, I am reposting the whole patchset on top of the current Linus tree which should already contain big pile of Andrew's mm patches. This should serve an easier reviewability and I also hope that this core part of the work can go to 4.6. The previous version was posted here [1] Hugh and David have suggested to drop [2] because the munlock path currently depends on the page lock and it is better if the initial version was conservative and prevent from any potential lockups even though it is not clear whether they are real - nobody has seen oom_reaper stuck on the page lock AFAICK. Me or Hugh will have a look and try to make the munlock path not depend on the page lock as a follow up work. Apart from that the feedback revealed one bug for a very unusual configuration (sysctl_oom_kill_allocating_task) and that has been fixed by patch 8 and one potential mis interaction with the pm freezer fixed by patch 7. I think the current code base is already very useful for many situations. The rest of the feedback was mostly about potential enhancements of the current code which I would really prefer to build on top of the current series. I plan to finish my mmap_sem killable for write in the upcoming release cycle and hopefully have it merged in the next merge window. I believe more extensions will follow. This code has been sitting in the mmotm (thus linux-next) for a while. Are there any fundamental objections to have this part merged in this merge window? Thanks! [1] http://lkml.kernel.org/r/1454505240-23446-1-git-send-email-mhocko@kernel.org [2] http://lkml.kernel.org/r/1454505240-23446-3-git-send-email-mhocko@kernel.org