From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jamie Lokier Subject: Question about current->namespace and check_mnt() Date: Fri, 29 Apr 2005 15:50:42 +0100 Message-ID: <20050429145042.GC17263@mail.shareable.org> References: <20050425190734.GB28294@mail.shareable.org> <20050426092924.GA4175@elf.ucw.cz> <20050426140715.GA10833@mail.shareable.org> <20050428192048.GA2895@mail.shareable.org> <1114717183.4180.718.camel@localhost> <20050428220839.GA5183@mail.shareable.org> <1114761430.4180.1566.camel@localhost> <20050429144252.GA17263@mail.shareable.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Miklos Szeredi , linuxram@us.ibm.com, ericvh@gmail.com, pavel@ucw.cz, hch@infradead.org, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, akpm@osdl.org Return-path: Received: from mail.shareable.org ([81.29.64.88]:10411 "EHLO mail.shareable.org") by vger.kernel.org with ESMTP id S262755AbVD2OvD (ORCPT ); Fri, 29 Apr 2005 10:51:03 -0400 To: viro@parcelfarce.linux.theplanet.co.uk Content-Disposition: inline In-Reply-To: <20050429144252.GA17263@mail.shareable.org> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org Hi Al, I have a specific namespace.c question: I really like to know what the purpose of check_mnt() is in namespace.c. In standard kernels you can't enter another process' namespace so I don't see how check_mnt() can _ever_ fail. Can it fail, or in other words, what is the purpose of that check? And if it can't fail, is there really a need for current->namespace, or can it just be removed? Also, I would think the current process' rootmnt->mnt_namespace would adequately define the "current process namespace", so making current->namespace redundant in that way. Is that right? Thanks, -- Jamie