From: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
To: Shakeel Butt <shakeelb@google.com>
Cc: Linux MM <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
Michal Hocko <mhocko@suse.com>, Roman Gushchin <guro@fb.com>
Subject: Re: [PATCH] mm, oom: avoid printk() iteration under RCU
Date: Thu, 18 Jul 2019 19:22:04 +0900 [thread overview]
Message-ID: <68706110-199d-a6ec-5b1d-7a433b4cccb9@i-love.sakura.ne.jp> (raw)
In-Reply-To: <CALvZod7kBpDC+rdz=-FrLn_jVAEdBNSLNEgAzGKeBe9HpJvkpA@mail.gmail.com>
On 2019/07/18 9:31, Shakeel Butt wrote:
>> diff --git a/include/linux/sched.h b/include/linux/sched.h
>> index 8dc1811..cb6696b 100644
>> --- a/include/linux/sched.h
>> +++ b/include/linux/sched.h
>> @@ -1246,6 +1246,7 @@ struct task_struct {
>> #ifdef CONFIG_MMU
>> struct task_struct *oom_reaper_list;
>> #endif
>> + struct list_head oom_victim_list;
>
> Shouldn't there be INIT_LIST_HEAD(&tsk->oom_victim_list) somewhere?
Yes if we need to use list_empty(&tsk->oom_victim_list) test.
This patch does not use such test; tsk->oom_victim_list is initialized
by list_add_tail() inside the OOM killer.
>
>> #ifdef CONFIG_VMAP_STACK
>> struct vm_struct *stack_vm_area;
>> #endif
next prev parent reply other threads:[~2019-07-18 11:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-17 10:55 Tetsuo Handa
2019-07-18 0:31 ` Shakeel Butt
2019-07-18 10:22 ` Tetsuo Handa [this message]
2019-07-18 8:30 ` Michal Hocko
2019-07-18 13:50 ` Tetsuo Handa
2019-07-18 14:02 ` Michal Hocko
2019-07-20 11:29 ` Tetsuo Handa
[not found] ` <20190920171042.8d970f9fc6f360de9b20ebbe@linux-foundation.org>
2019-09-21 20:30 ` Michal Hocko
[not found] ` <11c42f07-74d1-d4be-99bc-ca50d7c0ec71@i-love.sakura.ne.jp>
2019-09-22 6:20 ` Michal Hocko
[not found] ` <e4fac741-7dbc-41a1-7b9e-249415fba612@i-love.sakura.ne.jp>
2019-09-23 8:23 ` Michal Hocko
2019-07-23 23:14 ` Andrew Morton
2019-07-24 1:47 ` 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=68706110-199d-a6ec-5b1d-7a433b4cccb9@i-love.sakura.ne.jp \
--to=penguin-kernel@i-love.sakura.ne.jp \
--cc=akpm@linux-foundation.org \
--cc=guro@fb.com \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=shakeelb@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