From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754151AbbI3S0y (ORCPT ); Wed, 30 Sep 2015 14:26:54 -0400 Received: from mx1.redhat.com ([209.132.183.28]:54649 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932190AbbI3S0w (ORCPT ); Wed, 30 Sep 2015 14:26:52 -0400 Date: Wed, 30 Sep 2015 20:23:41 +0200 From: Oleg Nesterov To: Andrew Morton Cc: David Rientjes , Kyle Walker , Michal Hocko , Stanislav Kozina , Tetsuo Handa , linux-kernel@vger.kernel.org Subject: [PATCH -mm v2 0/3] mm/oom_kill: ensure we actually kill all tasks sharing the same mm Message-ID: <20150930182341.GA15047@redhat.com> References: <20150929141758.GA10934@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150929141758.GA10934@redhat.com> User-Agent: Mutt/1.5.18 (2008-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 09/29, Oleg Nesterov wrote: > > Let me send some initial changes which imo makes sense regardless, > but if we want to zap the victim's memory we need to ensure that all > tasks which share this ->mm were actually killed (see 3/3). > > Please review, this series is simple but only compile tested. > > Andrew, this is on top of linux-mmotm.git + the recent mm-oom-remove- > task_lock-protecting-comm-printing.patch from David. Please consider v2 based on the comments from Tetsuo and David (thanks a lot!). Oleg.