From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
To: akpm@linux-foundation.org
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v9] mm: Add memory allocation watchdog kernel thread.
Date: Sun, 28 May 2017 16:01:02 +0900 [thread overview]
Message-ID: <201705281601.BBE81220.HFLOtSFFOJVQMO@I-love.SAKURA.ne.jp> (raw)
In-Reply-To: <1495331504-12480-1-git-send-email-penguin-kernel@I-love.SAKURA.ne.jp>
Tetsuo Handa wrote:
> Changes from v7 [11]:
>
> (1) Reflect review comments from Andrew Morton. (Convert "u8 type" to
> "bool report", use CPUHP_PAGE_ALLOC_DEAD event and replace
> for_each_possible_cpu() with for_each_online_cpu(), reuse existing
> rcu_lock_break() and hung_timeout_jiffies() for now, update comments).
>
> Changes from v8 [12]:
>
> (1) Check mempool_alloc() as well, for mempool_alloc() is a sort of
> open-coded __GFP_NOFAIL allocation request where warn_alloc() cannot
> detect stalls due to __GFP_NORETRY, and actually I found a case where
> kswapd was unable to get memory for bio from mempool at
> bio_alloc_bioset(GFP_NOFS) [13], and I believe there are similar bugs.
Andrew, I believe it is time to start testing at linux-next.
Nobody shows interests in detecting/analyzing OOM livelock but there are
still unsolved suspicious cases
http://lkml.kernel.org/r/da13c3c7-b514-67b0-2eb9-6d6af277901b@wiesinger.com
http://lkml.kernel.org/r/20170502141544.rufykv6blliqzqfd@merlins.org
http://lkml.kernel.org/r/CAM_iQpWuPVGc2ky8M-9yukECtS+zKjiDasNymX7rMcBjBFyM_A@mail.gmail.com
where this patch might have given some clues if this patch were available.
There is no reason not to allow users to try this debugging aid.
--
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>
prev parent reply other threads:[~2017-05-28 7:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-21 1:51 Tetsuo Handa
2017-05-28 7:01 ` Tetsuo Handa [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=201705281601.BBE81220.HFLOtSFFOJVQMO@I-love.SAKURA.ne.jp \
--to=penguin-kernel@i-love.sakura.ne.jp \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/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