From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S932137AbcFQIRs (ORCPT <rfc822;w@1wt.eu>);
	Fri, 17 Jun 2016 04:17:48 -0400
Received: from mail-pf0-f195.google.com ([209.85.192.195]:35775 "EHLO
	mail-pf0-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1754025AbcFQIRo (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Fri, 17 Jun 2016 04:17:44 -0400
Date: Fri, 17 Jun 2016 17:17:26 +0900
From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Minchan Kim <minchan@kernel.org>
Cc: Joonsoo Kim <iamjoonsoo.kim@lge.com>,
        Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
        Michal Hocko <mhocko@kernel.org>,
        Andrew Morton <akpm@linux-foundation.org>, linux-mm@kvack.org,
        linux-kernel@vger.kernel.org, Vlastimil Babka <vbabka@suse.cz>,
        Stephen Rothwell <sfr@canb.auug.org.au>,
        Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Subject: Re: [next-20160615] kernel BUG at mm/rmap.c:1251!
Message-ID: <20160617081726.GA30699@swordfish>
References: <20160616084656.GB432@swordfish>
 <20160616085836.GC6836@dhcp22.suse.cz>
 <20160616092345.GC432@swordfish>
 <20160616094139.GE6836@dhcp22.suse.cz>
 <20160616095457.GD432@swordfish>
 <20160616101216.GT17127@bbox>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20160616101216.GT17127@bbox>
User-Agent: Mutt/1.6.1 (2016-04-27)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

Hello,

On (06/16/16 19:12), Minchan Kim wrote:
[..]
> > I'll copy-paste one more backtrace I swa today [originally was posted to another
> > mail thread].
> 
> Please, look at http://lkml.kernel.org/r/20160616100932.GS17127@bbox

I don't have a solid/stable reproducer for this one, but after some
mixed workloads beating (mempressure + zsmalloc + compiler workload)
with reverted b3ceb05f4bae844f67ce I haven't seen any problems.

So I think you nailed it Minchan!


reverted the entire patch set (for simplicity):

    Revert "mm/compaction: split freepages without holding the zone lock"
    Revert "mm/page_owner: initialize page owner without holding the zone lock"
    Revert "mm/page_owner: copy last_migrate_reason in copy_page_owner()"
    Revert "mm/page_owner: introduce split_page_owner and replace manual handling"
    Revert "tools/vm/page_owner: increase temporary buffer size"
    Revert "mm/page_owner: use stackdepot to store stacktrace"
    Revert "mm/page_owner: avoid null pointer dereference"
    Revert "mm/page_alloc: introduce post allocation processing on page allocator"

adding "mm/compaction: split freepages without holding the zone lock"
back seem to introduce the page->map_count bug after some time.

	-ss