From: Matthew Wilcox <matthew@wil.cx>
To: "Bagalkote, Sreenivas" <Sreenivas.Bagalkote@engenio.com>
Cc: "'Jeff Garzik'" <jgarzik@pobox.com>,
dougg@torque.net, andrew.patterson@hp.com,
Luben Tuikov <luben_tuikov@adaptec.com>,
Christoph Hellwig <hch@lst.de>,
"Moore, Eric Dean" <Eric.Moore@lsil.com>,
jejb@steeleye.com, linux-scsi@vger.kernel.org,
Linux Kernel <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@osdl.org>
Subject: Re: ioctls, etc. (was Re: [PATCH 1/4] sas: add flag for locally a ttached PHYs)
Date: Fri, 21 Oct 2005 06:40:37 -0600 [thread overview]
Message-ID: <20051021124037.GA27692@parisc-linux.org> (raw)
In-Reply-To: <0E3FA95632D6D047BA649F95DAB60E57060CD291@exa-atlanta>
On Fri, Oct 21, 2005 at 08:32:25AM -0400, Bagalkote, Sreenivas wrote:
> >Jeff Garzik wrote:
> >> Do you know where there are some clear guidelines on the use of
> >> pointers in a structure passed to an ioctl to lessen (or bypass)
> >> 32<->64 compat ioctl thunking?
> >
> >Its impossible. If you pass pointers, you need to thunk.
> >(Not even passing pointers via sysfs can avoid this.)
> >Consider running a 32-bit app (with 32-bit pointers and 32-bit
> >ABI) on a 64-bit kernel.
>
> The drivers/scsi/megaraid/megaraid_mm.c simply calls regular ioctl
> from within the compat_ioctl, though it does copy to and from the
> userland pointers. This is done by adding appropriate padding.
Yes. This is what is meant by "thunk".
prev parent reply other threads:[~2005-10-21 12:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-21 12:32 Bagalkote, Sreenivas
2005-10-21 12:40 ` Matthew Wilcox [this message]
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=20051021124037.GA27692@parisc-linux.org \
--to=matthew@wil.cx \
--cc=Eric.Moore@lsil.com \
--cc=Sreenivas.Bagalkote@engenio.com \
--cc=andrew.patterson@hp.com \
--cc=dougg@torque.net \
--cc=hch@lst.de \
--cc=jejb@steeleye.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=luben_tuikov@adaptec.com \
--cc=torvalds@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome