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!
Date: Fri, 17 Jun 2016 17:17:26 +0900 [thread overview]
Message-ID: <20160617081726.GA30699@swordfish> (raw)
In-Reply-To: <20160616101216.GT17127@bbox>
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
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
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!
Date: Fri, 17 Jun 2016 17:17:26 +0900 [thread overview]
Message-ID: <20160617081726.GA30699@swordfish> (raw)
In-Reply-To: <20160616101216.GT17127@bbox>
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
next prev parent reply other threads:[~2016-06-17 8:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-16 8:46 [next-20160615] kernel BUG at mm/rmap.c:1251! Sergey Senozhatsky
2016-06-16 8:46 ` Sergey Senozhatsky
2016-06-16 8:58 ` Michal Hocko
2016-06-16 8:58 ` Michal Hocko
2016-06-16 9:23 ` Sergey Senozhatsky
2016-06-16 9:23 ` Sergey Senozhatsky
2016-06-16 9:41 ` Michal Hocko
2016-06-16 9:41 ` Michal Hocko
2016-06-16 9:54 ` Sergey Senozhatsky
2016-06-16 9:54 ` Sergey Senozhatsky
2016-06-16 10:12 ` Minchan Kim
2016-06-16 10:12 ` Minchan Kim
2016-06-16 10:18 ` Sergey Senozhatsky
2016-06-16 10:18 ` Sergey Senozhatsky
2016-06-17 8:17 ` Sergey Senozhatsky [this message]
2016-06-17 8:17 ` Sergey Senozhatsky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160617081726.GA30699@swordfish \
--to=sergey.senozhatsky.work@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=minchan@kernel.org \
--cc=sergey.senozhatsky@gmail.com \
--cc=sfr@canb.auug.org.au \
--cc=vbabka@suse.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.