From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760741AbaEMOjd (ORCPT ); Tue, 13 May 2014 10:39:33 -0400 Received: from mx1.redhat.com ([209.132.183.28]:41789 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754036AbaEMOjc (ORCPT ); Tue, 13 May 2014 10:39:32 -0400 Date: Tue, 13 May 2014 10:39:25 -0400 From: Richard Guy Briggs To: Eric Paris Cc: linux-audit@redhat.com, linux-kernel@vger.kernel.org, containers@lists.linux-foundation.org, arozansk@redhat.com, serge@hallyn.com, ebiederm@xmission.com, sgrubb@redhat.com Subject: Re: [PATCH V2 1/6] namespaces: assign each namespace instance a serial number Message-ID: <20140513143925.GD27560@madcap2.tricolour.ca> References: <1399734119.3558.16.camel@localhost> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1399734119.3558.16.camel@localhost> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 14/05/10, Eric Paris wrote: > On Fri, 2014-05-09 at 20:27 -0400, Richard Guy Briggs wrote: > > Generate and assign a serial number per namespace instance since boot. > > > > Use a serial number per namespace (unique across one boot of one kernel) > > instead of the inode number (which is claimed to have had the right to change > > reserved and is not necessarily unique if there is more than one proc fs) to > > uniquely identify it per kernel boot. > > > > Signed-off-by: Richard Guy Briggs > > --- > > > +/** > > + * ns_serial - compute a serial number for the namespace > > + * > > + * Compute a serial number for the namespace to uniquely identify it in > > + * audit records. > > + */ > > +unsigned long long ns_serial(void) > > +{ > > + static DEFINE_SPINLOCK(serial_lock); > > + static unsigned long long serial = 4; /* reserved for IPC, UTS, user, PID */ > > + unsigned long flags; > > + > > + spin_lock_irqsave(&serial_lock, flags); > > + ++serial; > > + spin_unlock_irqrestore(&serial_lock, flags); > > + BUG_ON(!serial); > > + > > + return serial; > > +} > > + > > static inline struct nsproxy *create_nsproxy(void) > > { > > struct nsproxy *nsproxy; > > atomic64_t instead of doing it yourself? I'm willing to switch to atomic64_*. Thanks for pointing out its existence. > and why _irqsave() ? Can we seriously create new namespaces in irq > context? If you use the atomic though, you don't have to worry about > it... Agreed. That is unlikely. - RGB -- Richard Guy Briggs Senior Software Engineer, Kernel Security, AMER ENG Base Operating Systems, Red Hat Remote, Ottawa, Canada Voice: +1.647.777.2635, Internal: (81) 32635, Alt: +1.613.693.0684x3545