From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753884AbcFPI7F (ORCPT ); Thu, 16 Jun 2016 04:59:05 -0400 Received: from mail-pf0-f195.google.com ([209.85.192.195]:33369 "EHLO mail-pf0-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753818AbcFPI6q (ORCPT ); Thu, 16 Jun 2016 04:58:46 -0400 Date: Thu, 16 Jun 2016 10:58:37 +0200 From: Michal Hocko To: Sergey Senozhatsky Cc: Andrew Morton , linux-mm@kvack.org, linux-kernel@vger.kernel.org, Vlastimil Babka , Minchan Kim , Stephen Rothwell , Sergey Senozhatsky Subject: Re: [next-20160615] kernel BUG at mm/rmap.c:1251! Message-ID: <20160616085836.GC6836@dhcp22.suse.cz> References: <20160616084656.GB432@swordfish> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160616084656.GB432@swordfish> 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 Thu 16-06-16 17:46:57, Sergey Senozhatsky wrote: > Hello, > > [..] > [ 272.687656] vma ffff8800b855a5a0 start 00007f3576d58000 end 00007f3576f66000 > next ffff8800b977d2c0 prev ffff8800bdfb1860 mm ffff8801315ff200 > prot 8000000000000025 anon_vma ffff8800b7e583b0 vm_ops (null) > pgoff 7f3576d58 file (null) private_data (null) > flags: 0x100073(read|write|mayread|maywrite|mayexec|account) > [ 272.691793] ------------[ cut here ]------------ > [ 272.692820] kernel BUG at mm/rmap.c:1251! Is this? page_add_new_anon_rmap: VM_BUG_ON_VMA(address < vma->vm_start || address >= vma->vm_end, vma) [...] > [ 272.727842] BUG: sleeping function called from invalid context at include/linux/sched.h:2960 If yes then I am not sure we can do much about the this part. BUG_ON in an atomic context is unfortunate but the BUG_ON points out a real bug so we shouldn't drop it because of the potential atomic context. The above VM_BUG_ON should definitely be addressed. I thought that Vlastimil has pointed out some issues with the khugepaged lock inconsistencies which might lead to issues like this. -- Michal Hocko SUSE Labs