From: Michal Hocko <mhocko@kernel.org>
To: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Cc: linux-mm@kvack.org, Johannes Weiner <hannes@cmpxchg.org>,
David Rientjes <rientjes@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH 1/2] mm, oom: marks all killed tasks as oom victims
Date: Mon, 22 Oct 2018 10:48:42 +0200 [thread overview]
Message-ID: <20181022084842.GW18839@dhcp22.suse.cz> (raw)
In-Reply-To: <201810220758.w9M7wojE016890@www262.sakura.ne.jp>
On Mon 22-10-18 16:58:50, Tetsuo Handa wrote:
> Michal Hocko wrote:
> > --- a/mm/oom_kill.c
> > +++ b/mm/oom_kill.c
> > @@ -898,6 +898,7 @@ static void __oom_kill_process(struct task_struct *victim)
> > if (unlikely(p->flags & PF_KTHREAD))
> > continue;
> > do_send_sig_info(SIGKILL, SEND_SIG_FORCED, p, PIDTYPE_TGID);
> > + mark_oom_victim(p);
> > }
> > rcu_read_unlock();
> >
> > --
>
> Wrong. Either
You are right. The mm might go away between process_shares_mm and here.
While your find_lock_task_mm would be correct I believe we can do better
by using the existing mm that we already have. I will make it a separate
patch to clarity.
Thanks for pointing this out.
diff --git a/mm/oom_kill.c b/mm/oom_kill.c
index 188ae490cf3e..4c205061ed67 100644
--- a/mm/oom_kill.c
+++ b/mm/oom_kill.c
@@ -663,6 +663,7 @@ static inline void wake_oom_reaper(struct task_struct *tsk)
/**
* mark_oom_victim - mark the given task as OOM victim
* @tsk: task to mark
+ * @mm: mm associated with the task
*
* Has to be called with oom_lock held and never after
* oom has been disabled already.
@@ -670,10 +671,8 @@ static inline void wake_oom_reaper(struct task_struct *tsk)
* tsk->mm has to be non NULL and caller has to guarantee it is stable (either
* under task_lock or operate on the current).
*/
-static void mark_oom_victim(struct task_struct *tsk)
+static void mark_oom_victim(struct task_struct *tsk, struct mm_struct *mm)
{
- struct mm_struct *mm = tsk->mm;
-
WARN_ON(oom_killer_disabled);
/* OOM killer might race with memcg OOM */
if (test_and_set_tsk_thread_flag(tsk, TIF_MEMDIE))
@@ -860,7 +859,7 @@ static void __oom_kill_process(struct task_struct *victim)
* reserves from the user space under its control.
*/
do_send_sig_info(SIGKILL, SEND_SIG_FORCED, victim, PIDTYPE_TGID);
- mark_oom_victim(victim);
+ mark_oom_victim(victim, mm);
pr_err("Killed process %d (%s) total-vm:%lukB, anon-rss:%lukB, file-rss:%lukB, shmem-rss:%lukB\n",
task_pid_nr(victim), victim->comm, K(victim->mm->total_vm),
K(get_mm_counter(victim->mm, MM_ANONPAGES)),
@@ -898,7 +897,7 @@ static void __oom_kill_process(struct task_struct *victim)
if (unlikely(p->flags & PF_KTHREAD))
continue;
do_send_sig_info(SIGKILL, SEND_SIG_FORCED, p, PIDTYPE_TGID);
- mark_oom_victim(p);
+ mark_oom_victim(p, mm);
}
rcu_read_unlock();
@@ -942,7 +941,7 @@ static void oom_kill_process(struct oom_control *oc, const char *message)
*/
task_lock(p);
if (task_will_free_mem(p)) {
- mark_oom_victim(p);
+ mark_oom_victim(p, p->mm);
wake_oom_reaper(p);
task_unlock(p);
put_task_struct(p);
@@ -1072,7 +1071,7 @@ bool out_of_memory(struct oom_control *oc)
* quickly exit and free its memory.
*/
if (task_will_free_mem(current)) {
- mark_oom_victim(current);
+ mark_oom_victim(current, current->mm);
wake_oom_reaper(current);
return true;
}
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2018-10-22 8:48 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-22 7:13 [RFC PATCH 0/2] oom, memcg: do not report racy no-eligible OOM Michal Hocko
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 [this message]
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=20181022084842.GW18839@dhcp22.suse.cz \
--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