From: zhong jiang <zhongjiang@huawei.com>
To: aarcange@redhat.com, kirill.shutemov@linux.intel.com,
Vlastimil Babka <vbabka@suse.cz>, Michal Hocko <mhocko@suse.cz>,
Hugh Dickins <hughd@google.com>
Cc: Linux Memory Management List <linux-mm@kvack.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Qustion:: hungtask will come up when ksm enable.
Date: Tue, 13 Sep 2016 21:37:51 +0800 [thread overview]
Message-ID: <57D8012F.7080508@huawei.com> (raw)
I hit a following problem when run a oom case in ltp. The kernel version is 4.1 stable.
[ 601.937145] Call trace:
[ 601.939600] [<ffffffc000086a88>] __switch_to+0x74/0x8c
[ 601.944760] [<ffffffc000a1bae0>] __schedule+0x23c/0x7bc
[ 601.950007] [<ffffffc000a1c09c>] schedule+0x3c/0x94
[ 601.954907] [<ffffffc000a1eb84>] rwsem_down_write_failed+0x214/0x350
[ 601.961289] [<ffffffc000a1e32c>] down_write+0x64/0x80
[ 601.966363] [<ffffffc00021f794>] __ksm_exit+0x90/0x19c
[ 601.971523] [<ffffffc0000be650>] mmput+0x118/0x11c
[ 601.976335] [<ffffffc0000c3ec4>] do_exit+0x2dc/0xa74
[ 601.981321] [<ffffffc0000c46f8>] do_group_exit+0x4c/0xe4
[ 601.986656] [<ffffffc0000d0f34>] get_signal+0x444/0x5e0
[ 601.991904] [<ffffffc000089fcc>] do_signal+0x1d8/0x450
[ 601.997065] [<ffffffc00008a35c>] do_notify_resume+0x70/0x78
ksm_exit should take the write lock and wait all read lock is released. in fact, but I find
ksmd still hold a read lock in scan_get_next_rmap_item. thefefore, it will lead to hungtask.
Any suggestion will be appreciated.
Thanks
zhongjiang
--
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:[~2016-09-13 13:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=57D8012F.7080508@huawei.com \
--to=zhongjiang@huawei.com \
--cc=aarcange@redhat.com \
--cc=hughd@google.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.cz \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox