All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@suse.com>
To: Oleg Nesterov <oleg@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] get_task_mm: check PF_KTHREAD lockless
Date: Thu, 27 Jun 2024 09:49:05 +0200	[thread overview]
Message-ID: <Zn0ZcZRqejmSRqsZ@tiehlicka> (raw)
In-Reply-To: <20240626191017.GA20031@redhat.com>

On Wed 26-06-24 21:10:17, Oleg Nesterov wrote:
> Nowadays PF_KTHREAD is sticky and it was never protected by ->alloc_lock.
> Move the PF_KTHREAD check outside of task_lock() section to make this code
> more understandable.
> 
> Signed-off-by: Oleg Nesterov <oleg@redhat.com>

Acked-by: Michal Hocko <mhocko@suse.com>
Thanks!

> ---
>  kernel/fork.c | 11 +++++------
>  1 file changed, 5 insertions(+), 6 deletions(-)
> 
> diff --git a/kernel/fork.c b/kernel/fork.c
> index 4c361d2bdc12..d3dc623a1247 100644
> --- a/kernel/fork.c
> +++ b/kernel/fork.c
> @@ -1536,14 +1536,13 @@ struct mm_struct *get_task_mm(struct task_struct *task)
>  {
>  	struct mm_struct *mm;
>  
> +	if (task->flags & PF_KTHREAD)
> +		return NULL;
> +
>  	task_lock(task);
>  	mm = task->mm;
> -	if (mm) {
> -		if (task->flags & PF_KTHREAD)
> -			mm = NULL;
> -		else
> -			mmget(mm);
> -	}
> +	if (mm)
> +		mmget(mm);
>  	task_unlock(task);
>  	return mm;
>  }
> -- 
> 2.25.1.362.g51ebf55
> 

-- 
Michal Hocko
SUSE Labs

      reply	other threads:[~2024-06-27  7:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-26 19:10 [PATCH] get_task_mm: check PF_KTHREAD lockless Oleg Nesterov
2024-06-27  7:49 ` 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=Zn0ZcZRqejmSRqsZ@tiehlicka \
    --to=mhocko@suse.com \
    --cc=akpm@linux-foundation.org \
    --cc=ebiederm@xmission.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oleg@redhat.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 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.