From: Lin Feng <linfeng@cn.fujitsu.com>
To: cavokz@gmail.com
Cc: akpm@linux-foundation.org, viro@zeniv.linux.org.uk,
bcrl@kvack.org, kamezawa.hiroyu@jp.fujitsu.com, mhocko@suse.cz,
hughd@google.com, cl@linux.com, mgorman@suse.de,
minchan@kernel.org, isimatu.yasuaki@jp.fujitsu.com,
laijs@cn.fujitsu.com, wency@cn.fujitsu.com,
tangchen@cn.fujitsu.com, linux-fsdevel@vger.kernel.org,
linux-aio@kvack.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [BUG REPORT] [mm-hotplug, aio] aio ring_pages can't be offlined
Date: Mon, 03 Dec 2012 10:05:04 +0800 [thread overview]
Message-ID: <50BC08D0.5070006@cn.fujitsu.com> (raw)
In-Reply-To: <20121130152421.GA19849@glitch>
hi Domenico,
Sorry for my late reply and thanks for your attention, see below :)
On 11/30/2012 11:24 PM, Domenico Andreoli wrote:
> On Thu, Nov 29, 2012 at 02:54:58PM +0800, Lin Feng wrote:
>> Hi all,
>
> Hi Lin,
>
>> We encounter a "Resource temporarily unavailable" fail while trying
>> to offline a memory section in a movable zone. We found that there are
>> some pages can't be migrated. The offline operation fails in function
>> migrate_page_move_mapping() returning -EAGAIN till timeout because
>> the if assertion 'page_count(page) != 1' fails.
>
> is this something that worked before? if yes (then it's a regression)
> do you know with which kernel?
I think it's a problem exist long ago since we got the offline feature,
while I'm not sure from which version :)
It can only be reproduce by a zone-movable configured system holding
pages allocated by get_user_pages() for a long time.
Maybe we could also reproduce it by write a app just calls io_setup()
syscall and never release until it dies. Then locate the memory section
from which pages are allocated and try to offline it.
In fact if one doesn't want to use offline/hotplug memory feature,
to whom it's not a bug :)
Thanks,
linfeng
>
> Thanks,
> Domenico
>
prev parent reply other threads:[~2012-12-03 2:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-29 6:54 [BUG REPORT] [mm-hotplug, aio] aio ring_pages can't be offlined Lin Feng
2012-11-29 23:39 ` Andrew Morton
2012-11-30 0:04 ` Zach Brown
2012-11-30 3:39 ` Lin Feng
2012-11-30 3:42 ` Lin Feng
2012-11-30 5:57 ` Andrew Morton
2012-11-30 7:01 ` Lin Feng
2012-11-30 7:55 ` Andrew Morton
2012-11-30 10:29 ` Lin Feng
2012-11-30 10:47 ` Andrew Morton
2012-12-03 3:00 ` Lin Feng
2012-11-30 11:00 ` Mel Gorman
2012-12-03 2:52 ` Lin Feng
2012-12-03 11:37 ` Mel Gorman
2012-11-30 7:13 ` Kamezawa Hiroyuki
2012-11-30 8:00 ` Andrew Morton
2012-11-30 10:57 ` Mel Gorman
2012-11-30 15:24 ` Domenico Andreoli
2012-12-03 2:05 ` Lin Feng [this message]
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=50BC08D0.5070006@cn.fujitsu.com \
--to=linfeng@cn.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=bcrl@kvack.org \
--cc=cavokz@gmail.com \
--cc=cl@linux.com \
--cc=hughd@google.com \
--cc=isimatu.yasuaki@jp.fujitsu.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=laijs@cn.fujitsu.com \
--cc=linux-aio@kvack.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mhocko@suse.cz \
--cc=minchan@kernel.org \
--cc=tangchen@cn.fujitsu.com \
--cc=viro@zeniv.linux.org.uk \
--cc=wency@cn.fujitsu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).