mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Paul Jackson <pj@sgi.com>
Cc: Andrew Morton <akpm@osdl.org>,
	Simon.Derr@bull.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Cpuset: remove unnecessary NULL check
Date: Sun, 19 Mar 2006 07:08:10 -0700	[thread overview]
Message-ID: <m1acbmzfw5.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <20060319085743.18841.45970.sendpatchset@jackhammer.engr.sgi.com> (Paul Jackson's message of "Sun, 19 Mar 2006 00:57:43 -0800")

Paul Jackson <pj@sgi.com> writes:

> From: Paul Jackson <pj@sgi.com>
>
> Remove a no longer needed test for NULL cpuset pointer, with
> a little comment explaining why the test isn't needed.

Could we make that comment a little more explicit.  Say:

No need to check that tsk->cpuset != NULL, since cpuset_exit() sets
it to top_cpuset instead.

Comments that refer to a nebulous hack in some other function
a little hard to understand when new, and get really confusing
when the other function changes and it isn't clear what aspect
of that other function the comment depended on and if that property
still exists.

>   *  - No need to task_lock(tsk) on this tsk->cpuset reference, as it
>   *    doesn't really matter if tsk->cpuset changes after we read it,
>   *    and we take manage_mutex, keeping attach_task() from changing it
> - *    anyway.
> + *    anyway.  No need to check that tsk->cpuset != NULL, thanks to the
> + *    cpuset_exit() Hack.
>   */


Eric

  reply	other threads:[~2006-03-19 14:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-19  8:57 Paul Jackson
2006-03-19 14:08 ` Eric W. Biederman [this message]
2006-03-19 14:56   ` Paul Jackson
2006-03-19 15:06     ` Eric W. Biederman
2006-03-19 15:10     ` Eric W. Biederman
  -- strict thread matches above, loose matches on Subject: below --
2006-03-02  7:08 Paul Jackson

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=m1acbmzfw5.fsf@ebiederm.dsl.xmission.com \
    --to=ebiederm@xmission.com \
    --cc=Simon.Derr@bull.net \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pj@sgi.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

Powered by JetHome