linux-kernel - Sending IOCTLs from 32-bit userland to 64-bit Kernel module

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <479F1866.4050007@checkpoint.com>
Date:	Tue, 29 Jan 2008 14:13:26 +0200
From:	Yoav Artzi <yoavar@...ckpoint.com>
To:	linux-kernel@...r.kernel.org
Subject: Sending IOCTLs from 32-bit userland to 64-bit Kernel module

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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/