From: "Ken Chen" <kenchen@google.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: Paul Jackson <pj@sgi.com>, akpm@linux-foundation.org, linux-mm@kvack.org
Subject: Re: [patch] check cpuset mems_allowed for sys_mbind
Date: Thu, 10 May 2007 12:30:48 -0700 [thread overview]
Message-ID: <b040c32a0705101230n7cd557eaw8dbd00f7a2f8a58@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0705101141160.10271@schroedinger.engr.sgi.com>
On 5/10/07, Christoph Lameter <clameter@sgi.com> wrote:
> On Thu, 10 May 2007, Ken Chen wrote:
> > diff --git a/mm/mempolicy.c b/mm/mempolicy.c
> > index da94639..c2aec0e 100644
> > --- a/mm/mempolicy.c
> > +++ b/mm/mempolicy.c
> > @@ -884,6 +884,10 @@ asmlinkage long sys_mbind(unsigned long
> > err = get_nodes(&nodes, nmask, maxnode);
> > if (err)
> > return err;
> > +#ifdef CONFIG_CPUSETS
> > + /* Restrict the nodes to the allowed nodes in the cpuset */
> > + nodes_and(nodes, nodes, current->mems_allowed);
> > +#endif
> > return do_mbind(start, len, mode, &nodes, flags);
>
> Did I screw up whitespace there?
No, the patch was fine. I copy'n paste from xterm which turns all tab
into space. It's crappy xterm stuff.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2007-05-10 19:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-09 23:11 Ken Chen
2007-05-09 23:48 ` Paul Jackson
2007-05-10 0:47 ` Ken Chen
2007-05-10 0:55 ` Christoph Lameter
2007-05-10 1:26 ` Ken Chen
2007-05-10 1:44 ` Christoph Lameter
2007-05-10 18:32 ` Ken Chen
2007-05-10 18:41 ` Christoph Lameter
2007-05-10 19:30 ` Ken Chen [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=b040c32a0705101230n7cd557eaw8dbd00f7a2f8a58@mail.gmail.com \
--to=kenchen@google.com \
--cc=akpm@linux-foundation.org \
--cc=clameter@sgi.com \
--cc=linux-mm@kvack.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