From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steve French Subject: filesystem client mapping of uid_t/gid_t field in lookup Date: Fri, 13 May 2005 17:50:53 -0500 Message-ID: <42852F4D.4020804@austin.rr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from ms-smtp-03.texas.rr.com ([24.93.47.42]:27824 "EHLO ms-smtp-03-eri0.texas.rr.com") by vger.kernel.org with ESMTP id S262607AbVEMWvA (ORCPT ); Fri, 13 May 2005 18:51:00 -0400 Received: from [192.168.0.6] (cpe-70-112-161-22.austin.res.rr.com [70.112.161.22]) by ms-smtp-03-eri0.texas.rr.com (8.12.10/8.12.7) with ESMTP id j4DMohRZ013712 for ; Fri, 13 May 2005 17:50:44 -0500 (CDT) To: linux-fsdevel@vger.kernel.org Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org RFC 1813 states: Using user ids and group ids implies that the client and server either share the same ID list or do local user and group ID mapping. Servers and clients must agree on the mapping from user to uid and from group to gid, for those sites that do not implement a consistent user ID and group ID space. In practice, such mapping is typically performed on the server, following a static mapping scheme or a mapping established by the user from a client at mount time. which implies that other network filesystem clients passed in a table of uid mappings at mount time. This would be extremely useful, but seems unwieldy to pass in via mount. Without adding an ioctl to set the uids for a particular mount (actually in my case it would probably be for all mounts on the client to the same sharename (export) and/or a particular server), would this be better to pass in via proc (which also seems awkward due to size of proc writes presumably getting bigger than 4K if there were a lot of mappings).