From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Serge E. Hallyn" Subject: Re: [PATCH RFC 0/5] Containerize syslog Date: Mon, 19 Nov 2012 14:37:03 +0000 Message-ID: <20121119143702.GB4620@mail.hallyn.com> References: <50A9EAD8.9090501@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org, "Eric W. Biederman" , netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Rui Xiang Return-path: Content-Disposition: inline In-Reply-To: <50A9EAD8.9090501-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org Errors-To: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org List-Id: netdev.vger.kernel.org Quoting Rui Xiang (leo.ruixiang-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org): > From: Xiang Rui > > In Serge's patch (http://lwn.net/Articles/525629/), syslog_namespace was tied to a user > namespace. We add syslog_ns tied to nsproxy instead, and implement ns_printk in > ip_table context. Since you say 'we', I'm just wondering, which project is this a part of? > We add syslog_namespace as a part of nsproxy, and a new flag CLONE_SYSLOG to unshare > syslog area. Thanks, looks like you save me the time of having to add some users of nsprintk :) I understand that user namespaces aren't 100% usable yet, but looking long term, is there a reason to have the syslog namespace separate from user namespace? thanks, -serge