linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@suse.com>
To: Tang Yizhou <tangyizhou@huawei.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	David Rientjes <rientjes@google.com>,
	KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
	Shakeel Butt <shakeelb@google.com>
Subject: Re: [PATCH v2] mm, oom: Fix a comment in dump_task
Date: Mon, 18 Jan 2021 10:11:40 +0100	[thread overview]
Message-ID: <20210118091140.GA14336@dhcp22.suse.cz> (raw)
In-Reply-To: <20210115142314.12903-1-tangyizhou@huawei.com>

On Fri 15-01-21 22:23:14, Tang Yizhou wrote:
> If p is a kthread, it will be checked in oom_unkillable_task() so
> we can delete the corresponding comment.
> 
> Signed-off-by: Tang Yizhou <tangyizhou@huawei.com>
> Cc: David Rientjes <rientjes@google.com>
> Cc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
> Cc: Shakeel Butt <shakeelb@google.com>
> Cc: Michal Hocko <mhocko@kernel.org>

Yes, this is outdated for a long time. Thanks
Acked-by: Michal Hocko <mhocko@suse.com>

> ---
> v2: Update Cc list
>  mm/oom_kill.c | 5 ++---
>  1 file changed, 2 insertions(+), 3 deletions(-)
> 
> diff --git a/mm/oom_kill.c b/mm/oom_kill.c
> index 04b19b7b5435..9f043ad29554 100644
> --- a/mm/oom_kill.c
> +++ b/mm/oom_kill.c
> @@ -395,9 +395,8 @@ static int dump_task(struct task_struct *p, void *arg)
>  	task = find_lock_task_mm(p);
>  	if (!task) {
>  		/*
> -		 * This is a kthread or all of p's threads have already
> -		 * detached their mm's.  There's no need to report
> -		 * them; they can't be oom killed anyway.
> +		 * All of p's threads have already detached their mm's. There's
> +		 * no need to report them; they can't be oom killed anyway.
>  		 */
>  		return 0;
>  	}
> -- 
> 2.22.0

-- 
Michal Hocko
SUSE Labs


      parent reply	other threads:[~2021-01-18  9:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-15 14:23 Tang Yizhou
2021-01-15 19:46 ` David Rientjes
2021-01-18  9:11 ` Michal Hocko [this message]

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=20210118091140.GA14336@dhcp22.suse.cz \
    --to=mhocko@suse.com \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=rientjes@google.com \
    --cc=shakeelb@google.com \
    --cc=tangyizhou@huawei.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