From: Christoph Hellwig <hch@lst.de>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] make vt_ioctl ix86isms explicit
Date: Sat, 24 May 2003 20:03:17 +0200 [thread overview]
Message-ID: <20030524180317.GA5383@lst.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0305241046590.10806-100000@home.transmeta.com>
On Sat, May 24, 2003 at 10:55:41AM -0700, Linus Torvalds wrote:
> They were added because this was how the X server got IO permissions a
> million years ago. It comes from some random old UNIX/386 thing, it
> predates Linux itself as far as I know.
>
> I'm fairly certain that X itself no longer uses it at all, but there may
> be other programs that still do (unlikely). Your patch looks sane,
> although it might be equally sane to just remove the code altogether.
What about this one instead? If no one sees this messages we can just
rip it out in 2.7.<early>
--- 1.23/drivers/char/vt_ioctl.c Mon May 12 16:12:47 2003
+++ edited/drivers/char/vt_ioctl.c Fri May 23 22:13:19 2003
@@ -59,7 +59,7 @@
*/
unsigned char keyboard_type = KB_101;
-#if !defined(__alpha__) && !defined(__ia64__) && !defined(__mips__) && !defined(__arm__) && !defined(__sh__)
+#ifdef CONFIG_X86
asmlinkage long sys_ioperm(unsigned long from, unsigned long num, int on);
#endif
@@ -424,23 +424,29 @@
ucval = keyboard_type;
goto setchar;
-#if !defined(__alpha__) && !defined(__ia64__) && !defined(__mips__) && !defined(__arm__) && !defined(__sh__)
/*
* These cannot be implemented on any machine that implements
- * ioperm() in user level (such as Alpha PCs).
+ * ioperm() in user level (such as Alpha PCs) or not at all.
+ *
+ * XXX: you should never use these, just call ioperm directly..
*/
+#ifdef CONFIG_X86
case KDADDIO:
case KDDELIO:
/*
* KDADDIO and KDDELIO may be able to add ports beyond what
* we reject here, but to be safe...
*/
+ printk(KERN_INFO "[%s]: using obsolete KDADDIO/KDDELIO ioctl\n",
+ current->comm);
if (arg < GPFIRST || arg > GPLAST)
return -EINVAL;
return sys_ioperm(arg, 1, (cmd == KDADDIO)) ? -ENXIO : 0;
case KDENABIO:
case KDDISABIO:
+ printk(KERN_INFO "[%s]: using obsolete KDENABIO/KDDISABIO ioctl\n",
+ current->comm);
return sys_ioperm(GPFIRST, GPNUM,
(cmd == KDENABIO)) ? -ENXIO : 0;
#endif
next prev parent reply other threads:[~2003-05-24 17:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-24 17:37 [PATCH] make vt_ioctl ix86isms explicit Christoph Hellwig
2003-05-24 17:55 ` Linus Torvalds
2003-05-24 18:03 ` Christoph Hellwig [this message]
2003-05-24 22:16 ` Andries Brouwer
2003-05-24 18:03 ` James Simmons
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=20030524180317.GA5383@lst.de \
--to=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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 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.