From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754178AbcAVQHG (ORCPT ); Fri, 22 Jan 2016 11:07:06 -0500 Received: from resqmta-ch2-01v.sys.comcast.net ([69.252.207.33]:39492 "EHLO resqmta-ch2-01v.sys.comcast.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754140AbcAVQHD (ORCPT ); Fri, 22 Jan 2016 11:07:03 -0500 Date: Fri, 22 Jan 2016 10:07:01 -0600 (CST) From: Christoph Lameter X-X-Sender: cl@east.gentwo.org To: Michal Hocko cc: Sasha Levin , LKML , "linux-mm@kvack.org" , Andrew Morton Subject: Re: mm, vmstat: kernel BUG at mm/vmstat.c:1408! In-Reply-To: <20160122140418.GB19465@dhcp22.suse.cz> Message-ID: References: <20160120151007.GG14187@dhcp22.suse.cz> <569FAC90.5030407@oracle.com> <20160120212806.GA26965@dhcp22.suse.cz> <20160121082402.GA29520@dhcp22.suse.cz> <20160121165148.GF29520@dhcp22.suse.cz> <20160122140418.GB19465@dhcp22.suse.cz> Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 22 Jan 2016, Michal Hocko wrote: > Wouldn't it be much more easier and simply get rid of the VM_BUG_ON? > What is the point of keeping it in the first place. The code can > perfectly cope with the race. Ok then lets do that.