linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Oleg Nesterov <oleg@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Michal Hocko <mhocko@suse.cz>, Sergey Dyasly <dserrg@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] don't use task->pid/tgid in same_thread_group/has_group_leader_pid
Date: Wed, 29 May 2013 13:54:45 -0700	[thread overview]
Message-ID: <87r4gpy0a2.fsf@xmission.com> (raw)
In-Reply-To: <20130529143938.GA22211@redhat.com> (Oleg Nesterov's message of "Wed, 29 May 2013 16:39:38 +0200")

Oleg Nesterov <oleg@redhat.com> writes:

> task_struct->pid/tgid should go away.
>
> 1. Change same_thread_group() to use task->signal for comparison.
>
> 2. Change has_group_leader_pid(task) to compare task_pid(task) with
>    signal->leader_pid.

Reviewed-by: "Eric W. Biederman" <ebiederm@xmission.com>

This change looks good, thanks.

The posix cpu timers usage of has_group_leader_pid looks a little iffy,
but this change doesn't look like it will break them.

Thanks for this cleanup Oleg.

> Signed-off-by: Oleg Nesterov <oleg@redhat.com>
> ---
>  include/linux/sched.h |    8 ++++----
>  1 files changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/include/linux/sched.h b/include/linux/sched.h
> index 178a8d9..ce51dfd 100644
> --- a/include/linux/sched.h
> +++ b/include/linux/sched.h
> @@ -2179,15 +2179,15 @@ static inline bool thread_group_leader(struct task_struct *p)
>   * all we care about is that we have a task with the appropriate
>   * pid, we don't actually care if we have the right task.
>   */
> -static inline int has_group_leader_pid(struct task_struct *p)
> +static inline bool has_group_leader_pid(struct task_struct *p)
>  {
> -	return p->pid == p->tgid;
> +	return task_pid(p) == p->signal->leader_pid;
>  }
>  
>  static inline
> -int same_thread_group(struct task_struct *p1, struct task_struct *p2)
> +bool same_thread_group(struct task_struct *p1, struct task_struct *p2)
>  {
> -	return p1->tgid == p2->tgid;
> +	return p1->signal == p2->signal;
>  }
>  
>  static inline struct task_struct *next_thread(const struct task_struct *p)

      reply	other threads:[~2013-05-29 20:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-29 14:39 [PATCH] don't use task->pid/tgid in same_thread_group/has_group_leader_pid Oleg Nesterov
2013-05-29 20:54 ` Eric W. Biederman [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=87r4gpy0a2.fsf@xmission.com \
    --to=ebiederm@xmission.com \
    --cc=akpm@linux-foundation.org \
    --cc=dserrg@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhocko@suse.cz \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).