From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Kent Subject: Re: [RFC:PATCH 4/4] autofs4 - add new packet type for v5 communications Date: Fri, 17 Feb 2006 17:09:46 +0800 (WST) Message-ID: References: <200602170701.k1H71Irp004035@eagle.themaw.net> <20060217005134.6842f0ca.akpm@osdl.org> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, autofs@linux.kernel.org Return-path: Received: from wombat.indigo.net.au ([202.0.185.19]:21006 "EHLO wombat.indigo.net.au") by vger.kernel.org with ESMTP id S932354AbWBQJKr (ORCPT ); Fri, 17 Feb 2006 04:10:47 -0500 To: Andrew Morton In-Reply-To: <20060217005134.6842f0ca.akpm@osdl.org> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Fri, 17 Feb 2006, Andrew Morton wrote: > Ian Kent wrote: > > > > +/* autofs v5 common packet struct */ > > +struct autofs_v5_packet { > > + struct autofs_packet_hdr hdr; > > + autofs_wqt_t wait_queue_token; > > + __u32 dev; > > + __u64 ino; > > + uid_t uid; > > + gid_t gid; > > + pid_t pid; > > + pid_t tgid; > > + int len; > > + char name[NAME_MAX+1]; > > +}; > > Is this known to work with 32-bit userspace on 64-bit kernels? > > In particular, perhaps the ?id_t's should become a type of known size and > alignment (u32 or u64)? > Yes. I take your point. I used this for some time on my Ultra 2, which has this type of arch, without problem. I increased the ino field from 32 to 64 bits since that time and haven't since tested it. I'm happy to change them to 64 bit if you believe it will avoid potential problems? Ian