From: Michal Hocko <mhocko@kernel.org> To: <linux-mm@kvack.org> Cc: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>, Johannes Weiner <hannes@cmpxchg.org>, Andrew Morton <akpm@linux-foundation.org>, LKML <linux-kernel@vger.kernel.org> Subject: [PATCH 0/2] oom, memcg: do not report racy no-eligible OOM Date: Mon, 7 Jan 2019 15:38:00 +0100 [thread overview] Message-ID: <20190107143802.16847-1-mhocko@kernel.org> (raw) Hi, I have posted this as an RFC previously [1]. Tetsuo has pointed out some issues with the patch 1 which I have fixed hopefully. Other than that this is just a rebase on top of Linus tree. The original cover: this is a follow up for [2] 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 [2] 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. Feedback is appreciated of course. [1] http://lkml.kernel.org/r/20181022071323.9550-1-mhocko@kernel.org [2] http://lkml.kernel.org/r/20181010151135.25766-1-mhocko@kernel.org
WARNING: multiple messages have this Message-ID (diff)
From: Michal Hocko <mhocko@kernel.org> To: linux-mm@kvack.org Cc: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>, Johannes Weiner <hannes@cmpxchg.org>, Andrew Morton <akpm@linux-foundation.org>, LKML <linux-kernel@vger.kernel.org> Subject: [PATCH 0/2] oom, memcg: do not report racy no-eligible OOM Date: Mon, 7 Jan 2019 15:38:00 +0100 [thread overview] Message-ID: <20190107143802.16847-1-mhocko@kernel.org> (raw) Hi, I have posted this as an RFC previously [1]. Tetsuo has pointed out some issues with the patch 1 which I have fixed hopefully. Other than that this is just a rebase on top of Linus tree. The original cover: this is a follow up for [2] 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 [2] 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. Feedback is appreciated of course. [1] http://lkml.kernel.org/r/20181022071323.9550-1-mhocko@kernel.org [2] http://lkml.kernel.org/r/20181010151135.25766-1-mhocko@kernel.org
next reply other threads:[~2019-01-07 14:39 UTC|newest] Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-01-07 14:38 Michal Hocko [this message] 2019-01-07 14:38 ` [PATCH 0/2] oom, memcg: do not report racy no-eligible OOM Michal Hocko 2019-01-07 14:38 ` [PATCH 1/2] mm, oom: marks all killed tasks as oom victims Michal Hocko 2019-01-07 14:38 ` Michal Hocko 2019-01-07 20:58 ` Tetsuo Handa 2019-01-08 8:11 ` Michal Hocko 2019-01-07 14:38 ` [PATCH 2/2] memcg: do not report racy no-eligible OOM tasks Michal Hocko 2019-01-07 14:38 ` Michal Hocko 2019-01-07 20:59 ` Tetsuo Handa 2019-01-08 8:14 ` Michal Hocko 2019-01-08 10:39 ` Tetsuo Handa 2019-01-08 11:46 ` Michal Hocko 2019-01-08 8:35 ` kbuild test robot 2019-01-08 9:39 ` Michal Hocko 2019-01-11 0:23 ` [kbuild-all] " Rong Chen 2019-01-08 14:21 ` [PATCH 3/2] memcg: Facilitate termination of memcg OOM victims Tetsuo Handa 2019-01-08 14:38 ` Michal Hocko 2019-01-09 11:03 ` [PATCH 0/2] oom, memcg: do not report racy no-eligible OOM Michal Hocko 2019-01-09 11:34 ` Tetsuo Handa 2019-01-09 12:02 ` Michal Hocko 2019-01-10 23:59 ` Tetsuo Handa 2019-01-11 10:25 ` Tetsuo Handa 2019-01-11 11:33 ` Michal Hocko 2019-01-11 12:40 ` Tetsuo Handa 2019-01-11 13:34 ` Michal Hocko 2019-01-11 14:31 ` Tetsuo Handa 2019-01-11 15:07 ` Michal Hocko 2019-01-11 15:37 ` Tetsuo Handa 2019-01-11 16:45 ` Michal Hocko 2019-01-12 10:52 ` Tetsuo Handa 2019-01-13 17:36 ` Michal Hocko
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=20190107143802.16847-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 \ /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: linkBe 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.