The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Ben Collins <bcollins@debian.org>
To: "David S. Miller" <davem@redhat.com>
Cc: pavel@suse.cz, linux-kernel@vger.kernel.org,
	schwidefsky@de.ibm.com, ak@suse.de, arnd@bergmann-dalldorf.de
Subject: Re: ioctl32 consolidation -- call for testing
Date: Thu, 27 Feb 2003 15:34:40 -0500	[thread overview]
Message-ID: <20030227203440.GP21100@phunnypharm.org> (raw)
In-Reply-To: <20030227.121302.86023203.davem@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 584 bytes --]

On Thu, Feb 27, 2003 at 12:13:02PM -0800, David S. Miller wrote:
>    From: Ben Collins <bcollins@debian.org>
>    Date: Thu, 27 Feb 2003 15:27:39 -0500
>    
>    Here it is. Sparc64's macros for ioctl32's assumed that cmd was u_int
>    instead of u_long. This look ok to you, Dave?
> 
> We would love to see that patch :-)

It was real small...so small that it slipped through mutt's open() call
and never got attached :)



-- 
Debian     - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
Deqo       - http://www.deqo.com/

[-- Attachment #2: sparc64-ioctl32.diff --]
[-- Type: text/plain, Size: 1291 bytes --]

--- arch/sparc64/kernel/ioctl32.c~	2003-02-27 14:54:49.000000000 -0500
+++ arch/sparc64/kernel/ioctl32.c	2003-02-27 15:19:29.000000000 -0500
@@ -11,6 +11,7 @@
 #include <linux/config.h>
 #include <linux/types.h>
 #include <linux/compat.h>
+#include <linux/ioctl32.h>
 #include <linux/kernel.h>
 #include <linux/sched.h>
 #include <linux/smp.h>
@@ -4274,10 +4275,14 @@
 #define BNEPGETCONNLIST	_IOR('B', 210, int)
 #define BNEPGETCONNINFO	_IOR('B', 211, int)
 
-#define COMPATIBLE_IOCTL(cmd) asm volatile(".word %0, sys_ioctl, 0" : : "i" (cmd));
-#define HANDLE_IOCTL(cmd,handler) asm volatile(".word %0, %1, 0" : : "i" (cmd), "i" (handler));
-#define IOCTL_TABLE_START void ioctl32_foo(void) { asm volatile(".data\n.global ioctl_start\nioctl_start:");
-#define IOCTL_TABLE_END asm volatile("\n.global ioctl_end\nioctl_end:\n\t.previous"); }
+typedef int (* ioctl32_handler_t)(unsigned int, unsigned int, unsigned long, struct file *);
+
+#define COMPATIBLE_IOCTL(cmd)		HANDLE_IOCTL((cmd),sys_ioctl)
+#define HANDLE_IOCTL(cmd,handler)	{ (cmd), (ioctl32_handler_t)(handler), NULL },
+#define IOCTL_TABLE_START \
+	struct ioctl_trans ioctl_start[] = {
+#define IOCTL_TABLE_END \
+	}; struct ioctl_trans ioctl_end[0];
 
 IOCTL_TABLE_START
 /* List here exlicitly which ioctl's are known to have

  reply	other threads:[~2003-02-27 20:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-26 22:26 ioctl32 consolidation -- call for testing Pavel Machek
2003-02-27 19:44 ` Ben Collins
2003-02-27 19:51 ` Ben Collins
2003-02-27 20:27   ` Ben Collins
2003-02-27 20:13     ` David S. Miller
2003-02-27 20:34       ` Ben Collins [this message]
2003-02-27 20:21         ` David S. Miller
2003-02-27 20:50           ` Ben Collins
2003-02-27 20:37             ` David S. Miller
2003-02-27 21:12               ` Ben Collins
2003-02-28 13:23                 ` Pavel Machek
2003-02-28 15:49                   ` Ben Collins
2003-03-01  0:52                   ` David S. Miller
2003-02-28 13:20         ` Pavel Machek

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=20030227203440.GP21100@phunnypharm.org \
    --to=bcollins@debian.org \
    --cc=ak@suse.de \
    --cc=arnd@bergmann-dalldorf.de \
    --cc=davem@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    --cc=schwidefsky@de.ibm.com \
    /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