All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@dm.cobaltmicro.com>
To: ultralinux@vger.kernel.org
Subject: Re: 2.1.126 still no sparc64 autofsu
Date: Sun, 15 Nov 1998 23:54:01 +0000	[thread overview]
Message-ID: <marc-linux-ultrasparc-91118678519518@msgid-missing> (raw)
In-Reply-To: <marc-linux-ultrasparc-91107863319189@msgid-missing>

   From: "H. Peter Anvin" <hpa@transmeta.com>
   Date: Sun, 15 Nov 1998 15:49:21 -0800 (PST)

   Problem is that autofs passes an "unsigned long" in the ioctl()
   *argument*, not in a structure; also it passes data to the daemon via
   a packetized protocol on a pipe.

Ok, we have a similar issue for rtnetlink on sparc64 running 32-bit
binaries.  That piece is so complex that I've decided to tell people
for now to wait until we have a 64-bit userland if they want to run
programs like gated :-)

I looked at this patch, and it occurs to me, why to make it an
unsigned long ever?  For one thing this wait_queue_token seems to be
set by an int counter (autofs_next_wait_queue).

Secondly, to avoid all kinds of problems in this area, the best way to
define structures which are a "protocol" over some transport (even a
pipe) is to use the available fixed typing schemes (u32, u16 etc.) the
kernel provides.  This makes issues like this never a problem because
a u32 in the kernel is the same as a u32 in userspace no matter if we
have a 32-bit binary running under emulation on a 64-bit kernel.

Do you agree? :-)

Later,
David S. Miller
davem@dm.cobaltmicro.com

  parent reply	other threads:[~1998-11-15 23:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-11-14  8:17 2.1.126 still no sparc64 autofsu H. Peter Anvin
1998-11-14 15:45 ` Rich Sahlender
1998-11-14 19:53 ` Jakub Jelinek
1998-11-15  0:52 ` David S. Miller
1998-11-15 23:49 ` H. Peter Anvin
1998-11-15 23:54 ` David S. Miller [this message]
1998-11-16  6:47 ` H. Peter Anvin
1998-11-16  6:48 ` Jakub Jelinek
1998-11-16  7:57 ` Jakub Jelinek
1998-11-16  8:37 ` H. Peter Anvin
1998-11-16 20:33 ` Rich Sahlender

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=marc-linux-ultrasparc-91118678519518@msgid-missing \
    --to=davem@dm.cobaltmicro.com \
    --cc=ultralinux@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.