All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yisheng Xie <xieyisheng1@huawei.com>
To: <minchan@kernel.org>, <ngupta@vflare.org>,
	<sergey.senozhatsky.work@gmail.com>
Cc: <linux-mm@kvack.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Xishi Qiu <qiuxishi@huawei.com>,
	Hanjun Guo <guohanjun@huawei.com>
Subject: [RFC]mm/zsmalloc,: trigger BUG_ON in function zs_map_object.
Date: Tue, 28 Mar 2017 15:20:22 +0800	[thread overview]
Message-ID: <e8aa282e-ad53-bfb8-2b01-33d2779f247a@huawei.com> (raw)

Hi, all,

We had backport the no-lru migration to linux-4.1, meanwhile change the
ZS_MAX_ZSPAGE_ORDER to 3. Then we met a BUG_ON(!page[1]).

It rarely happen, and presently, what I get is:
[6823.316528s]obj=a160701f, obj_idx=15, class{size:2176,objs_per_zspage:15,pages_per_zspage:8}
[...]
[6823.316619s]BUG: failure at /home/ethan/kernel/linux-4.1/mm/zsmalloc.c:1458/zs_map_object()! ----> BUG_ON(!page[1])

It seems that we have allocated an object from a ZS_FULL group?
(Actually， I do not get the inuse number of this zspage, which I am trying to.)
And presently, I can not find why it happened. Any idea about it?

Any comment is more than welcome!

Thanks
Yisheng Xie

WARNING: multiple messages have this Message-ID (diff)
From: Yisheng Xie <xieyisheng1@huawei.com>
To: minchan@kernel.org, ngupta@vflare.org, sergey.senozhatsky.work@gmail.com
Cc: linux-mm@kvack.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Xishi Qiu <qiuxishi@huawei.com>,
	Hanjun Guo <guohanjun@huawei.com>
Subject: [RFC]mm/zsmalloc,: trigger BUG_ON in function zs_map_object.
Date: Tue, 28 Mar 2017 15:20:22 +0800	[thread overview]
Message-ID: <e8aa282e-ad53-bfb8-2b01-33d2779f247a@huawei.com> (raw)

Hi, all,

We had backport the no-lru migration to linux-4.1, meanwhile change the
ZS_MAX_ZSPAGE_ORDER to 3. Then we met a BUG_ON(!page[1]).

It rarely happen, and presently, what I get is:
[6823.316528s]obj=a160701f, obj_idx=15, class{size:2176,objs_per_zspage:15,pages_per_zspage:8}
[...]
[6823.316619s]BUG: failure at /home/ethan/kernel/linux-4.1/mm/zsmalloc.c:1458/zs_map_object()! ----> BUG_ON(!page[1])

It seems that we have allocated an object from a ZS_FULL group?
(Actuallyi 1/4 ? I do not get the inuse number of this zspage, which I am trying to.)
And presently, I can not find why it happened. Any idea about it?

Any comment is more than welcome!

Thanks
Yisheng Xie



--
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>

             reply	other threads:[~2017-03-28  7:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-28  7:20 Yisheng Xie [this message]
2017-03-28  7:20 ` [RFC]mm/zsmalloc,: trigger BUG_ON in function zs_map_object Yisheng Xie
2017-03-29  0:20 ` Minchan Kim
2017-03-29  0:20   ` Minchan Kim
2017-03-29  6:42   ` Sergey Senozhatsky
2017-03-29  6:42     ` Sergey Senozhatsky
2017-03-29  7:53     ` Yisheng Xie
2017-03-29  7:53       ` Yisheng Xie
2017-03-29  7:51   ` Yisheng Xie
2017-03-29  7:51     ` Yisheng Xie

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=e8aa282e-ad53-bfb8-2b01-33d2779f247a@huawei.com \
    --to=xieyisheng1@huawei.com \
    --cc=guohanjun@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=minchan@kernel.org \
    --cc=ngupta@vflare.org \
    --cc=qiuxishi@huawei.com \
    --cc=sergey.senozhatsky.work@gmail.com \
    /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.