From: Andrew Morton <akpm@osdl.org>
To: Ian Kent <raven@themaw.net>
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 00:51:34 -0800 [thread overview]
Message-ID: <20060217005134.6842f0ca.akpm@osdl.org> (raw)
In-Reply-To: <200602170701.k1H71Irp004035@eagle.themaw.net>
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)?
next prev parent reply other threads:[~2006-02-17 8:52 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 [this message]
2006-02-17 9:09 ` Ian Kent
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=20060217005134.6842f0ca.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=autofs@linux.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=raven@themaw.net \
/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).