From: Arnd Bergmann <arnd@arndb.de>
To: Pavel Machek <pavel@ucw.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ioctl cleanups: enable sg_io and serial stuff to be shared
Date: Wed, 7 May 2003 17:46:15 +0200 [thread overview]
Message-ID: <200305071746.15908.arnd@arndb.de> (raw)
In-Reply-To: <20030507151613.GB412@elf.ucw.cz>
On Wednesday 07 May 2003 17:16, Pavel Machek wrote:
> > Has anyone solved the register_ioctl32_conversion() from module problem
> > yet? The patch will break if you build scsi as a module because you
> > never unregister the conversion helper on unload.
> > Even if you do the unregister from a module_exit() function, there
> > will still be a small race against running ioctl handlers. I suppose
> > we have to add an 'owner' field to struct ioctl_trans in order to
> > get it right.
>
> Its in drivers/block/scsi_ioctl.c. AFAICS, its always compiled in, so
> I'm not hitting that problem *yet*.
No, it has indeed been possible to build scsi as a module for a long
time and in that case, scsi_ioctl becomes part of that module. The same
problem also exists for any user of register_ioctl32_conversion(), e.g.
ieee1394.
> > > + ss.iomem_base = (void *)((unsigned long)ss.iomem_base & 0xffffffff);
> >
> > you need compat_ptr() for iomem_base as well
>
> Its not pointer, AFAICS (at least it can not be dereferenced by
> userspace).
Right, it appears to be a physical address, which therefore would require
a new mapping macro to be really correct. If this were used on s390, that
macro would be the same as compat_ptr(), the other architectures probably
need a simple cast (again, like compat_ptr()). Either of 1. new macro, 2.
compat_ptr() or 3. the existing code works correctly here, so just do
whichever you prefer. Maybe somebody else has a strong opinion on it.
Arnd <><
next prev parent reply other threads:[~2003-05-07 15:39 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030507104008$12ba@gated-at.bofh.it>
2003-05-07 11:51 ` ioctl cleanups: enable sg_io and serial stuff to be shared Arnd Bergmann
2003-05-07 12:41 ` Pavel Machek
2003-05-07 12:56 ` Christoph Hellwig
2003-05-07 14:39 ` David S. Miller
2003-05-07 15:12 ` Jeff Garzik
2003-05-07 14:07 ` David S. Miller
2003-05-08 10:46 ` Gerd Knorr
2003-05-08 15:16 ` Ben Collins
2003-05-08 15:51 ` Christoph Hellwig
2003-05-08 15:37 ` Ben Collins
2003-05-08 19:34 ` Pavel Machek
2003-05-08 19:27 ` Ben Collins
2003-05-08 20:06 ` Pavel Machek
2003-05-08 19:47 ` Ben Collins
2003-05-08 20:09 ` David S. Miller
2003-05-08 20:26 ` David Mosberger
2003-05-08 20:33 ` Arjan van de Ven
2003-05-08 21:11 ` David Mosberger
2003-05-08 15:23 ` Arnd Bergmann
2003-05-07 15:28 ` Pavel Machek
2003-05-07 16:04 ` David S. Miller
2003-05-07 19:13 ` Arnd Bergmann
2003-05-07 18:12 ` David S. Miller
2003-05-07 23:50 ` Arnd Bergmann
2003-05-08 10:35 ` David S. Miller
2003-05-07 22:20 ` Alan Cox
2003-05-08 20:33 ` Pavel Machek
2003-05-08 20:43 ` David S. Miller
2003-05-08 23:03 ` Pavel Machek
2003-05-08 23:35 ` Arnd Bergmann
2003-05-08 22:48 ` Arnd Bergmann
2003-05-08 23:22 ` Pavel Machek
2003-05-07 13:18 ` Arnd Bergmann
2003-05-07 14:01 ` Carl-Daniel Hailfinger
2003-05-07 15:16 ` Pavel Machek
2003-05-07 15:46 ` Arnd Bergmann [this message]
2003-05-07 16:07 ` Jens Axboe
2003-05-07 16:20 ` Arnd Bergmann
2003-05-07 10:27 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=200305071746.15908.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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