From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qg0-f53.google.com (mail-qg0-f53.google.com [209.85.192.53]) by kanga.kvack.org (Postfix) with ESMTP id 22EBD6B0009 for ; Thu, 28 Jan 2016 10:47:50 -0500 (EST) Received: by mail-qg0-f53.google.com with SMTP id o11so41921512qge.2 for ; Thu, 28 Jan 2016 07:47:50 -0800 (PST) Received: from mx1.redhat.com (mx1.redhat.com. [209.132.183.28]) by mx.google.com with ESMTPS id w132si10192215qka.53.2016.01.28.07.47.49 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 28 Jan 2016 07:47:49 -0800 (PST) Date: Thu, 28 Jan 2016 16:47:46 +0100 From: Andrea Arcangeli Subject: Re: mm: BUG in expand_downwards Message-ID: <20160128154746.GI12228@redhat.com> References: <20160127194132.GA896@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: owner-linux-mm@kvack.org List-ID: To: Dmitry Vyukov Cc: Oleg Nesterov , Konstantin Khlebnikov , Andrew Morton , "Kirill A. Shutemov" , Chen Gang , Michal Hocko , Piotr Kwapulinski , "linux-mm@kvack.org" , LKML , Hugh Dickins , Sasha Levin , syzkaller , Kostya Serebryany , Alexander Potapenko Hello, On Wed, Jan 27, 2016 at 10:11:44PM +0100, Dmitry Vyukov wrote: > Sorry, I meant only the second once. The mm bug. > I guess you need at least CONFIG_DEBUG_VM. Run it in a tight parallel > loop with CPU oversubscription (e.g. 32 parallel processes on 2 cores) > for at least an hour. Does this help for the mm bug?