From: Michal Hocko <mhocko@kernel.org>
To: <linux-mm@kvack.org>
Cc: Johannes Weiner <hannes@cmpxchg.org>,
Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
David Rientjes <rientjes@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: [RFC PATCH 0/2] oom, memcg: do not report racy no-eligible OOM
Date: Mon, 22 Oct 2018 09:13:21 +0200 [thread overview]
Message-ID: <20181022071323.9550-1-mhocko@kernel.org> (raw)
Hi,
this is a follow up for [1] which has been nacked mostly because Tetsuo
was able to find a simple workload which can trigger a race where
no-eligible task is reported without a good reason. I believe the patch2
addresses that issue and we do not have to play dirty games with
throttling just because of the race. I still believe that patch proposed
in [1] is a useful one but this can be addressed later.
This series comprises 2 patch. The first one is something I meant to do
loooong time ago, I just never have time to do that. We need it here to
handle CLONE_VM without CLONE_SIGHAND cases. The second patch closes the
race.
I didn't get to test this throughly so it is posted as an RFC.
Feedback is appreciated of course.
[1] http://lkml.kernel.org/r/20181010151135.25766-1-mhocko@kernel.org
next reply other threads:[~2018-10-22 7:13 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-22 7:13 Michal Hocko [this message]
2018-10-22 7:13 ` [RFC PATCH 1/2] mm, oom: marks all killed tasks as oom victims Michal Hocko
2018-10-22 7:58 ` Tetsuo Handa
2018-10-22 8:48 ` Michal Hocko
2018-10-22 9:42 ` Tetsuo Handa
2018-10-22 10:43 ` Michal Hocko
2018-10-22 10:56 ` Tetsuo Handa
2018-10-22 11:12 ` Michal Hocko
2018-10-22 11:16 ` [RFC PATCH v2 " Michal Hocko
2018-10-22 7:13 ` [RFC PATCH 2/2] memcg: do not report racy no-eligible OOM tasks Michal Hocko
2018-10-22 11:45 ` Tetsuo Handa
2018-10-22 12:03 ` Michal Hocko
2018-10-22 13:20 ` Tetsuo Handa
2018-10-22 13:43 ` Michal Hocko
2018-10-22 15:12 ` Tetsuo Handa
2018-10-23 1:01 ` Tetsuo Handa
2018-10-23 11:42 ` Michal Hocko
2018-10-23 12:10 ` Michal Hocko
2018-10-23 12:33 ` Tetsuo Handa
2018-10-23 12:48 ` Michal Hocko
2018-10-26 14:25 ` Johannes Weiner
2018-10-26 19:25 ` Michal Hocko
2018-10-26 19:33 ` Michal Hocko
2018-10-27 1:10 ` Tetsuo Handa
2018-11-06 9:44 ` Tetsuo Handa
2018-11-06 12:42 ` Michal Hocko
2018-11-07 9:45 ` Tetsuo Handa
2018-11-07 10:08 ` Michal Hocko
2018-12-07 12:43 ` Tetsuo Handa
2018-12-12 10:23 ` 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=20181022071323.9550-1-mhocko@kernel.org \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=rientjes@google.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;
as well as URLs for NNTP newsgroup(s).