From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
To: mhocko@kernel.org
Cc: akpm@linux-foundation.org, oleg@redhat.com, linux-mm@kvack.org
Subject: Re: linux-4.4-rc1: TIF_MEMDIE without SIGKILL pending?
Date: Mon, 23 Nov 2015 21:38:33 +0900 [thread overview]
Message-ID: <201511232138.DJG69728.SQLFOJOFOMVHFt@I-love.SAKURA.ne.jp> (raw)
In-Reply-To: <20151123113352.GH21050@dhcp22.suse.cz>
Michal Hocko wrote:
> I haven't checked where exactly you added the BUG_ON, I was merely
> comenting on the possibility that TIF_MEMDIE is set without sending
> SIGKILL.
>
> Now that I am looking at your BUG_ON more closely I am wondering whether
> it makes sense at all. The fatal signal has been dequeued in get_signal
> before we call into do_group_exit AFAICS.
Indeed, it makes no sense at all.
Making below change made expected output.
MemAlloc: oom-tester4(11306) uninterruptible exiting victim
----------
diff --git a/mm/page_alloc.c b/mm/page_alloc.c
index 01127b8..8c8fb6d 100644
--- a/mm/page_alloc.c
+++ b/mm/page_alloc.c
@@ -3289,8 +3289,9 @@ static int kmallocwd(void *unused)
snprintf(buf, sizeof(buf),
" gfp=0x%x order=%u delay=%lu", memalloc.gfp,
memalloc.order, now - memalloc.start);
- pr_warn("MemAlloc: %s(%u)%s%s%s%s\n", p->comm, p->pid, buf,
+ pr_warn("MemAlloc: %s(%u)%s%s%s%s%s\n", p->comm, p->pid, buf,
(type & 8) ? " uninterruptible" : "",
+ (p->flags & PF_EXITING) ? " exiting" : "",
(type & 2) ? " dying" : "",
(type & 1) ? " victim" : "");
touch_nmi_watchdog();
----------
I'll make V3 of kmallocwd. Thank you.
--
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:[~2015-11-23 12:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-22 12:13 Tetsuo Handa
2015-11-23 8:30 ` Michal Hocko
2015-11-23 11:06 ` Tetsuo Handa
2015-11-23 11:33 ` Michal Hocko
2015-11-23 12:38 ` 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=201511232138.DJG69728.SQLFOJOFOMVHFt@I-love.SAKURA.ne.jp \
--to=penguin-kernel@i-love.sakura.ne.jp \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=oleg@redhat.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