linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ian Kent <raven@themaw.net>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	autofs@linux.kernel.org
Subject: Re: [RFC:PATCH 4/4] autofs4 - add new packet type for v5 communications
Date: Fri, 17 Feb 2006 17:09:46 +0800 (WST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0602171703590.4109@eagle.themaw.net> (raw)
In-Reply-To: <20060217005134.6842f0ca.akpm@osdl.org>

On Fri, 17 Feb 2006, Andrew Morton wrote:

> Ian Kent <raven@themaw.net> 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



  reply	other threads:[~2006-02-17  9:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-17  7:01 [RFC:PATCH 4/4] autofs4 - add new packet type for v5 communications Ian Kent
2006-02-17  8:51 ` Andrew Morton
2006-02-17  9:09   ` Ian Kent [this message]
2006-02-17  9:17     ` Andrew Morton
2006-02-17 11:03       ` Ian Kent
2006-02-17  9:21     ` Ian Kent
  -- strict thread matches above, loose matches on Subject: below --
2006-02-12 13:40 Ian Kent

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.64.0602171703590.4109@eagle.themaw.net \
    --to=raven@themaw.net \
    --cc=akpm@osdl.org \
    --cc=autofs@linux.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).