From: "Serge E. Hallyn" <serge@hallyn.com>
To: "Raphael S. Carvalho" <raphael.scarv@gmail.com>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
Andrew Morton <akpm@linux-foundation.org>,
"Serge E. Hallyn" <serge@hallyn.com>,
Serge Hallyn <serge.hallyn@canonical.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] kernel/pid.c: Moving statement.
Date: Thu, 13 Jun 2013 07:40:36 -0500 [thread overview]
Message-ID: <20130613124036.GB28706@austin.hallyn.com> (raw)
In-Reply-To: <1370901160-3156-1-git-send-email-raphael.scarv@gmail.com>
Quoting Raphael S. Carvalho (raphael.scarv@gmail.com):
> Moving statement to static initilization of init_pid_ns.
>
> Signed-off-by: Raphael S. Carvalho <raphael.scarv@gmail.com>
This seems innocuous enough.
Acked-by: Serge Hallyn <serge.hallyn@canonical.com>
> ---
> kernel/pid.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/kernel/pid.c b/kernel/pid.c
> index 0db3e79..c577d3c 100644
> --- a/kernel/pid.c
> +++ b/kernel/pid.c
> @@ -75,6 +75,7 @@ struct pid_namespace init_pid_ns = {
> [ 0 ... PIDMAP_ENTRIES-1] = { ATOMIC_INIT(BITS_PER_PAGE), NULL }
> },
> .last_pid = 0,
> + .nr_hashed = PIDNS_HASH_ADDING,
> .level = 0,
> .child_reaper = &init_task,
> .user_ns = &init_user_ns,
> @@ -594,7 +595,6 @@ void __init pidmap_init(void)
> /* Reserve PID 0. We never call free_pidmap(0) */
> set_bit(0, init_pid_ns.pidmap[0].page);
> atomic_dec(&init_pid_ns.pidmap[0].nr_free);
> - init_pid_ns.nr_hashed = PIDNS_HASH_ADDING;
>
> init_pid_ns.pid_cachep = KMEM_CACHE(pid,
> SLAB_HWCACHE_ALIGN | SLAB_PANIC);
> --
> 1.7.2.5
prev parent reply other threads:[~2013-06-13 17:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-10 21:52 Raphael S. Carvalho
2013-06-13 12:40 ` Serge E. Hallyn [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=20130613124036.GB28706@austin.hallyn.com \
--to=serge@hallyn.com \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=raphael.scarv@gmail.com \
--cc=serge.hallyn@canonical.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
all inboxes | Powered by JetHome®