All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@transmeta.com>
To: ultralinux@vger.kernel.org
Subject: Re: 2.1.126 still no sparc64 autofsu
Date: Mon, 16 Nov 1998 06:47:44 +0000	[thread overview]
Message-ID: <marc-linux-ultrasparc-91122307331803@msgid-missing> (raw)
In-Reply-To: <marc-linux-ultrasparc-91107863319189@msgid-missing>

> > Problem is that autofs passes an "unsigned long" in the ioctl()
> > *argument*, not in a structure; 
> 
> That's no problem. In fact, 32bit syscall entry code zero extends already in
> assembly, so handling this is really a nop.

Except when the value isn't zero in the high dword... then you have no
way to pass the value down.

> > also it passes data to the daemon via
> > a packetized protocol on a pipe.
> 
> That's the only problem I'd have with autofs and that's why it was not
> working. I was thinking about overriding the f_ops of the pipe file
> descriptor, so that it points to a special write method which would do the
> conversion of the structure before sending it over the pipe, but your
> autofs_wqt_t patch is of course much better, as it does not need additional 
> code and complexity. Thanks.

Does it work?  If so, then I can send it to Linus.

	-hpa

  parent reply	other threads:[~1998-11-16  6:47 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
1998-11-16  6:47 ` H. Peter Anvin [this message]
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-91122307331803@msgid-missing \
    --to=hpa@transmeta.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.