All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Emelyanov <xemul@parallels.com>
To: Oleg Nesterov <oleg@redhat.com>
Cc: Tejun Heo <tj@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Cyrill Gorcunov <gorcunov@openvz.org>
Subject: Re: [PATCH] sysctl: Add the kernel.ns_last_pid control
Date: Tue, 29 Nov 2011 22:12:19 +0400	[thread overview]
Message-ID: <4ED52083.8090605@parallels.com> (raw)
In-Reply-To: <20111129174741.GA32209@redhat.com>

On 11/29/2011 09:47 PM, Oleg Nesterov wrote:
> On 11/28, Pavel Emelyanov wrote:
>>
>> --- a/kernel/pid_namespace.c
>> +++ b/kernel/pid_namespace.c
>> @@ -191,9 +191,40 @@ void zap_pid_ns_processes(struct pid_namespace *pid_ns)
>>  	return;
>>  }
>>
>> +static int pid_ns_ctl_handler(struct ctl_table *table, int write,
>> +		void __user *buffer, size_t *lenp, loff_t *ppos)
>> +{
>> +	struct ctl_table tmp = *table;
>> +
>> +	if (write && !capable(CAP_SYS_ADMIN))
>> +		return -EPERM;
>> +
>> +	/*
>> +	 * Writing directly to ns' last_pid field is OK, since this field
>> +	 * is volatile in a living namespace anyway and a code writing to
>> +	 * it should synchronize its usage with external means.
>> +	 */
>> +
>> +	tmp.data = &current->nsproxy->pid_ns->last_pid;
>> +	return proc_dointvec(&tmp, write, buffer, lenp, ppos);
>> +}
>> +
>> +static struct ctl_table pid_ns_ctl_table[] = {
>> +	{
>> +		.procname = "ns_last_pid",
>> +		.maxlen = sizeof(int),
>> +		.mode = 0666, /* permissions are checked in the handler */
>> +		.proc_handler = pid_ns_ctl_handler,
>> +	},
>> +	{ }
>> +};
>> +
>> +static struct ctl_path kern_path[] = { { .procname = "kernel", }, { } };
>> +
>>  static __init int pid_namespaces_init(void)
>>  {
>>  	pid_ns_cachep = KMEM_CACHE(pid_namespace, SLAB_PANIC);
>> +	register_sysctl_paths(kern_path, pid_ns_ctl_table);
>>  	return 0;
>>  }
> 
> Hmm. This way it depends on CONFIG_PID_NS.

Yes, since this _is_ for namespaces. As we've found out this is close to completely
unusable in the initial namespace in which tasks are just forking without caring
much about what CAP_SYS_ADMIN-s think about this.

> Can't we simply add an entry into kern_table[] ?

And store the .proc_handler function dealing with somewhat which is pid namespace
specific in the same generic file?

> And without ns_, just /proc/sys/kernel/last_pid.

But that's the namespace's last pid, not just some system-wide last pid.

> Oleg.
> 
> .
> 


  reply	other threads:[~2011-11-29 18:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-28 15:21 [PATCH] sysctl: Add the kernel.ns_last_pid control Pavel Emelyanov
2011-11-28 15:53 ` Tejun Heo
2011-11-28 16:04   ` Pavel Emelyanov
2011-11-28 16:09     ` Tejun Heo
2011-11-29 17:47 ` Oleg Nesterov
2011-11-29 18:12   ` Pavel Emelyanov [this message]
2011-11-29 19:22     ` Oleg Nesterov
2012-01-12 22:49 ` Andrew Morton

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=4ED52083.8090605@parallels.com \
    --to=xemul@parallels.com \
    --cc=akpm@linux-foundation.org \
    --cc=gorcunov@openvz.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oleg@redhat.com \
    --cc=tj@kernel.org \
    /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.