From: Yoav Artzi <yoavar@checkpoint.com>
To: linux-kernel@vger.kernel.org
Subject: Sending IOCTLs from 32-bit userland to 64-bit Kernel module
Date: Tue, 29 Jan 2008 15:08:19 +0200 [thread overview]
Message-ID: <479F2543.40705@checkpoint.com> (raw)
Hi,
I have a 32-bit user land application which sends an IOCTL to a 64-bit
Kernel module. I have a few different cmd codes that I can send through
the IOCTL. For some reason I seem to always get the same IOCTL cmd from
user land, no matter what the ioctl() call is given. This cmd code that
I get has some bytes (W/R and the module code) that are OK, but the rest
is just garbage or zeros. This was originally a 32-bit system, and we
are no converting the Kernel module to 64-bit, so maybe there's
something special for 32-64 communication that miss.
I am working on Linux Kernel v2.6.18.
Thanks
next reply other threads:[~2008-01-29 13:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-29 13:08 Yoav Artzi [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-01-29 13:18 Sending IOCTLs from 32-bit userland to 64-bit Kernel module Yoav Artzi
2008-01-29 15:29 ` Jiri Slaby
2008-01-29 12:13 Yoav Artzi
2008-01-29 13:05 ` Michael Tokarev
2008-01-29 13:23 ` Jiri Slaby
2008-01-29 13:23 ` Matti Aarnio
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=479F2543.40705@checkpoint.com \
--to=yoavar@checkpoint.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox