From: Tejun Heo <tj@kernel.org>
To: ltp@lists.linux.it
Subject: [LTP] [BUG] oom hangs the system, NMI backtrace shows most CPUs in shrink_slab
Date: Wed, 20 Jan 2016 10:10:44 -0500 [thread overview]
Message-ID: <20160120151044.GA5157@mtj.duckdns.org> (raw)
In-Reply-To: <201601202217.BEF43262.QOLFHOOJFVFtMS@I-love.SAKURA.ne.jp>
On Wed, Jan 20, 2016 at 10:17:23PM +0900, Tetsuo Handa wrote:
> What happens if memory allocation requests from items using this workqueue
> got stuck due to OOM livelock? Are pending items in this workqueue cannot
> be processed because this workqueue was created without WQ_MEM_RECLAIM?
If something gets stuck due to OOM livelock, anything which tries to
allocate memory can hang. That's why it's called a livelock.
WQ_MEM_RECLAIM or not wouldn't make any difference.
> I don't know whether accessing swap memory depends on this workqueue.
> But if disk driver depends on this workqueue for accessing swap partition
> on the disk, some event is looping inside memory allocator will result in
> unable to process disk I/O request for accessing swap partition on the disk?
What you're saying is too vauge for me to decipher exactly what you
have on mind. Can you please elaborate?
--
tejun
WARNING: multiple messages have this Message-ID (diff)
From: Tejun Heo <tj@kernel.org>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Cc: jiangshanlai@gmail.com, jstancek@redhat.com, linux-mm@kvack.org,
ltp@lists.linux.it
Subject: Re: [BUG] oom hangs the system, NMI backtrace shows most CPUs in shrink_slab
Date: Wed, 20 Jan 2016 10:10:44 -0500 [thread overview]
Message-ID: <20160120151044.GA5157@mtj.duckdns.org> (raw)
In-Reply-To: <201601202217.BEF43262.QOLFHOOJFVFtMS@I-love.SAKURA.ne.jp>
On Wed, Jan 20, 2016 at 10:17:23PM +0900, Tetsuo Handa wrote:
> What happens if memory allocation requests from items using this workqueue
> got stuck due to OOM livelock? Are pending items in this workqueue cannot
> be processed because this workqueue was created without WQ_MEM_RECLAIM?
If something gets stuck due to OOM livelock, anything which tries to
allocate memory can hang. That's why it's called a livelock.
WQ_MEM_RECLAIM or not wouldn't make any difference.
> I don't know whether accessing swap memory depends on this workqueue.
> But if disk driver depends on this workqueue for accessing swap partition
> on the disk, some event is looping inside memory allocator will result in
> unable to process disk I/O request for accessing swap partition on the disk?
What you're saying is too vauge for me to decipher exactly what you
have on mind. Can you please elaborate?
--
tejun
--
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>
next prev parent reply other threads:[~2016-01-20 15:10 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-18 15:38 [LTP] [BUG] oom hangs the system, NMI backtrace shows most CPUs in shrink_slab Jan Stancek
2016-01-18 15:38 ` Jan Stancek
2016-01-19 10:29 ` [LTP] " Tetsuo Handa
2016-01-19 10:29 ` Tetsuo Handa
2016-01-19 15:13 ` [LTP] " Jan Stancek
2016-01-19 15:13 ` Jan Stancek
2016-01-20 10:23 ` [LTP] [BUG] oom hangs the system, NMI backtrace shows most CPUs inshrink_slab Tetsuo Handa
2016-01-20 10:23 ` Tetsuo Handa
2016-01-20 13:17 ` [LTP] [BUG] oom hangs the system, NMI backtrace shows most CPUs in shrink_slab Tetsuo Handa
2016-01-20 13:17 ` Tetsuo Handa
2016-01-20 15:10 ` Tejun Heo [this message]
2016-01-20 15:10 ` Tejun Heo
2016-01-20 15:54 ` [LTP] " Tetsuo Handa
2016-01-20 15:54 ` Tetsuo Handa
2016-01-22 15:14 ` [LTP] " Jan Stancek
2016-01-22 15:14 ` Jan Stancek
2016-01-23 6:30 ` [LTP] " Tetsuo Handa
2016-01-23 6:30 ` Tetsuo Handa
2016-01-26 7:48 ` [LTP] " Jan Stancek
2016-01-26 7:48 ` Jan Stancek
2016-01-26 14:46 ` Tetsuo Handa
2016-01-26 14:46 ` Tetsuo Handa
2016-01-27 11:02 ` Tetsuo Handa
2016-01-28 15:48 ` Tetsuo Handa
2016-01-29 7:32 ` Jan Stancek
2016-01-29 12:35 ` Tetsuo Handa
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=20160120151044.GA5157@mtj.duckdns.org \
--to=tj@kernel.org \
--cc=ltp@lists.linux.it \
/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.