Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751444AbWHYKyI (ORCPT ); Fri, 25 Aug 2006 06:54:08 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751441AbWHYKyH (ORCPT ); Fri, 25 Aug 2006 06:54:07 -0400 Received: from mailhub.sw.ru ([195.214.233.200]:8350 "EHLO relay.sw.ru") by vger.kernel.org with ESMTP id S932418AbWHYKyE (ORCPT ); Fri, 25 Aug 2006 06:54:04 -0400 Message-ID: <44EED77A.20801@sw.ru> Date: Fri, 25 Aug 2006 14:56:58 +0400 From: Kirill Korotaev User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.13) Gecko/20060417 X-Accept-Language: en-us, en, ru MIME-Version: 1.0 To: Alexey Dobriyan CC: Alan Cox , Andrew Morton , Linux Kernel Mailing List , Christoph Hellwig , Pavel Emelianov , Andrey Savochkin , devel@openvz.org, Rik van Riel , Andi Kleen , Greg KH , Oleg Nesterov , Matt Helsley , Rohit Seth , Chandra Seetharaman Subject: Re: [PATCH 4/6] BC: user interface (syscalls) References: <44EC31FB.2050002@sw.ru> <44EC369D.9050303@sw.ru> <44EC5B74.2040104@sw.ru> <20060823095031.cb14cc52.akpm@osdl.org> <1156354182.3007.37.camel@localhost.localdomain> <20060823213512.88f4344d.akpm@osdl.org> <1156417456.3007.72.camel@localhost.localdomain> <20060824130822.GA5205@martell.zuzino.mipt.ru> In-Reply-To: <20060824130822.GA5205@martell.zuzino.mipt.ru> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1493 Lines: 39 Alexey Dobriyan wrote: > On Thu, Aug 24, 2006 at 12:04:16PM +0100, Alan Cox wrote: > >>Ar Mer, 2006-08-23 am 21:35 -0700, ysgrifennodd Andrew Morton: >> >>>>Its a uid_t because of setluid() and twenty odd years of existing unix >>>>practice. >>>> >>> >>>I don't understand. This number is an identifier for an accounting >>>container, which was somehow dreamed up by userspace. >> >>Which happens to be a uid_t. It could easily be anyother_t of itself and >>you can create a container_id_t or whatever. It is just a number. >> >>The ancient Unix implementations of this kind of resource management and >>security are built around setluid() which sets a uid value that cannot >>be changed again and is normally used for security purposes. That >>happened to be a uid_t and in simple setups at login uid = luid = euid >>would be the norm. >> >>Thus the Linux one happens to be a uid_t. It could be something else but >>for the "container per user" model whatever a container is must be able >>to hold all possible uid_t values. So we can certainly do something like >> >>typedef uid_t container_id_t; > > > What about cid_t? Google mentions cid_t was used in HP-UX specific IPC (only if > _INCLUDE_HPUX_SOURCE is defined). bcid_t? Thanks, Kirill - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/