From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751669AbcGLHRH (ORCPT ); Tue, 12 Jul 2016 03:17:07 -0400 Received: from mail-wm0-f50.google.com ([74.125.82.50]:37420 "EHLO mail-wm0-f50.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750717AbcGLHRE (ORCPT ); Tue, 12 Jul 2016 03:17:04 -0400 Date: Tue, 12 Jul 2016 09:17:01 +0200 From: Michal Hocko To: Shayan Pooya Cc: cgroups mailinglist , LKML , linux-mm@kvack.org Subject: Re: bug in memcg oom-killer results in a hung syscall in another process in the same cgroup Message-ID: <20160712071701.GC14586@dhcp22.suse.cz> References: <20160711064150.GB5284@dhcp22.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.6.0 (2016-04-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon 11-07-16 10:40:55, Shayan Pooya wrote: > > > > Could you post the stack trace of the hung oom victim? Also could you > > post the full kernel log? > > Here is the stack of the process that lives (it is *not* the > oom-victim) in a run with 100 processes and *without* strace: > > # cat /proc/7688/stack > [] futex_wait_queue_me+0xc2/0x120 > [] futex_wait+0x116/0x280 > [] do_futex+0x120/0x540 > [] SyS_futex+0x81/0x180 > [] entry_SYSCALL_64_fastpath+0x16/0x71 > [] 0xffffffffffffffff I am not sure I understand. Is this the hung task? -- Michal Hocko SUSE Labs