From: Rui Xiang <rui.xiang@huawei.com>
To: Gu Zheng <guz.fnst@cn.fujitsu.com>
Cc: <containers@lists.linux-foundation.org>,
<linux-kernel@vger.kernel.org>, <serge.hallyn@ubuntu.com>,
<ebiederm@xmission.com>, <akpm@linux-foundation.org>,
<gaofeng@cn.fujitsu.com>, <libo.chen@huawei.com>
Subject: Re: [PATCH 7/9] syslog_ns: implement function for creating syslog ns
Date: Tue, 30 Jul 2013 11:39:01 +0800 [thread overview]
Message-ID: <51F73555.1020204@huawei.com> (raw)
In-Reply-To: <51F64313.4010700@cn.fujitsu.com>
On 2013/7/29 18:25, Gu Zheng wrote:
> Hi Rui,
>
> On 07/29/2013 10:31 AM, Rui Xiang wrote:
>
>> Add create_syslog_ns function to create a new ns. We
>> must create a user_ns before create a new syslog ns.
>> And then tie the new syslog_ns to current user_ns
>> instead of original syslog_ns which comes from
>> parent user_ns.
...
>> diff --git a/kernel/printk.c b/kernel/printk.c
>> index fd2d600..6b561db 100644
>> --- a/kernel/printk.c
>> +++ b/kernel/printk.c
>> @@ -384,6 +384,10 @@ static int check_syslog_permissions(int type, bool from_file,
>> || type == SYSLOG_ACTION_CONSOLE_LEVEL)
>> ns = &init_syslog_ns;
>>
>> + /* create a new syslog ns */
>> + if (type == SYSLOG_ACTION_NEW_NS)
>> + return 0;
>> +
>
> Don't we need further permission or caps check here? Return success directly seems sloppy.
>
CAP_SYSLOG is checked in create_syslog_ns, so I think we can return 0 temporarily.
next prev parent reply other threads:[~2013-07-30 3:39 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-29 2:31 [PATCH 0/9] Add namespace support for syslog v2 Rui Xiang
2013-07-29 2:31 ` [PATCH 1/9] syslog_ns: add syslog_namespace and put/get_syslog_ns Rui Xiang
2013-07-29 9:40 ` Gu Zheng
2013-07-29 11:47 ` Rui Xiang
2013-07-30 0:46 ` Gu Zheng
2013-07-29 2:31 ` [PATCH 2/9] syslog_ns: add syslog_ns into user_namespace Rui Xiang
2013-07-29 9:46 ` Gu Zheng
2013-07-29 9:54 ` Gao feng
2013-07-29 9:56 ` Gu Zheng
2013-07-29 2:31 ` [PATCH 3/9] syslog_ns: add init syslog_ns for global syslog Rui Xiang
2013-07-29 2:31 ` [PATCH 4/9] syslog_ns: make syslog handling per namespace Rui Xiang
2013-07-29 9:50 ` Gu Zheng
2013-08-01 1:36 ` Gao feng
2013-08-01 3:10 ` Rui Xiang
2013-08-01 5:38 ` Gao feng
2013-08-01 6:29 ` Rui Xiang
2013-07-29 2:31 ` [PATCH 5/9] syslog_ns: make permisiion check per user namespace Rui Xiang
2013-07-29 2:31 ` [PATCH 6/9] syslog_ns: use init syslog_ns for console action Rui Xiang
2013-07-29 2:31 ` [PATCH 7/9] syslog_ns: implement function for creating syslog ns Rui Xiang
2013-07-29 10:25 ` Gu Zheng
2013-07-30 3:39 ` Rui Xiang [this message]
2013-07-30 3:42 ` Gu Zheng
2013-07-29 10:39 ` Gao feng
2013-07-29 2:31 ` [PATCH 8/9] syslog_ns: implement ns_printk for specific syslog_ns Rui Xiang
2013-07-29 10:37 ` Gu Zheng
2013-07-29 12:17 ` Rui Xiang
2013-07-29 2:31 ` [PATCH 9/9] netfilter: use ns_printk in iptable context Rui Xiang
2013-07-29 9:48 ` Gao feng
2013-07-29 12:37 ` Rui Xiang
2013-07-29 9:33 ` [PATCH 0/9] Add namespace support for syslog v2 Gu Zheng
2013-07-29 18:58 ` Eric W. Biederman
2013-07-30 2:11 ` Rui Xiang
2013-07-30 6:05 ` Bruno Prémont
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=51F73555.1020204@huawei.com \
--to=rui.xiang@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=containers@lists.linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=gaofeng@cn.fujitsu.com \
--cc=guz.fnst@cn.fujitsu.com \
--cc=libo.chen@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=serge.hallyn@ubuntu.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