From: Qian Cai <cai@lca.pw>
To: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Cc: linux-mm@kvack.org, Michal Hocko <mhocko@kernel.org>
Subject: Re: [RFC PATCH] mm, oom: disable dump_tasks by default
Date: Fri, 06 Sep 2019 09:48:32 -0400 [thread overview]
Message-ID: <1567777712.5576.111.camel@lca.pw> (raw)
In-Reply-To: <7eada349-90d0-a12f-701c-adac3c395e3c@i-love.sakura.ne.jp>
On Fri, 2019-09-06 at 22:41 +0900, Tetsuo Handa wrote:
> On 2019/09/06 22:08, Qian Cai wrote:
> > Yes, mlocked is troublesome. I have other incidents where crond and systemd-
> > udevd were killed by mistake,
>
> Yes. How to mitigate this regression is a controversial topic.
> Michal thinks that we should make mlocked pages reclaimable, but
> we haven't reached there. I think that we can monitor whether
> counters decay over time (with timeout), but Michal refuses any
> timeout based approach. We are deadlocked there.
>
> > and it even tried to kill kworker/0.
>
> No. The OOM killer never tries to kill kernel threads like kworker/0.
I meant,
[40040.401575] kworker/0:1 invoked oom-killer:
gfp_mask=0x40cc0(GFP_KERNEL|__GFP_COMP), order=2, oom_score_adj=0
>
> >
> > https://cailca.github.io/files/dmesg.txt
>
>
next prev parent reply other threads:[~2019-09-06 13:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-03 14:45 [RFC PATCH] mm, oom: disable dump_tasks by default Michal Hocko
2019-09-03 15:02 ` Qian Cai
2019-09-03 15:13 ` Michal Hocko
2019-09-03 15:32 ` Qian Cai
2019-09-03 19:12 ` Michal Hocko
2019-09-05 16:10 ` Qian Cai
[not found] ` <8ea5da51-a1ac-4450-17d9-0ea7be346765@i-love.sakura.ne.jp>
2019-09-05 21:21 ` Qian Cai
[not found] ` <192f2cb9-172e-06f4-d9e4-a58b5e167231@i-love.sakura.ne.jp>
2019-09-06 13:08 ` Qian Cai
[not found] ` <7eada349-90d0-a12f-701c-adac3c395e3c@i-love.sakura.ne.jp>
2019-09-06 13:48 ` Qian Cai [this message]
2019-09-06 13:49 ` Michal Hocko
2019-09-03 20:52 ` Tetsuo Handa
2019-09-04 5:40 ` Michal Hocko
2019-09-04 20:04 ` David Rientjes
2019-09-05 13:39 ` Tetsuo Handa
2019-09-05 14:08 ` Michal Hocko
2019-09-06 10:46 ` Tetsuo Handa
2019-09-06 11:02 ` Michal Hocko
2019-09-06 11:11 ` 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=1567777712.5576.111.camel@lca.pw \
--to=cai@lca.pw \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
/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.