linux-kernel - Re: Ultra Sparc T1 port

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-prev] [day] [month] [year] [list]

Message-Id: <0B111904-6CD0-40D4-85D7-F13CCCA06FAB@cs.otago.ac.nz>
Date:	Thu, 31 Aug 2006 09:46:00 +1200
From:	zhiyi huang <hzy@...otago.ac.nz>
To:	Mikael Pettersson <mikpe@...uu.se>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Ultra Sparc T1 port

> zhiyi huang writes:
>> Hello,
>> I am using a Ubuntu port on Ultra Sparc T1.
>> Linux version 2.6.15-21-sparc64-smp (buildd@...igas) (gcc version
>> 4.0.3 (Ubuntu 4.0.3-1ubuntu5)) #1 SMP Fri Apr 21 17:04:05 UTC 2006
>> I have installed a module in the kernel. It is a RAM device driver.
>> When my application calls ioctl on the device (/dev/dsm), I got the
>> following log message:
>>
>> Aug 29 11:13:20 info-sf-03 kernel: [    3.603348] ioctl32(manager:
>> 18821): Unknown cmd fd(3) cmd(80047f00){00} arg(fffc3934) on /dev/dsm
>>
>> I check my module and found the control has not reached my module
>> yet. I haven't got much clue why it happened and how to fix the
>> problem. It works fine on Linux 2.6.8/i386, by the way.
>> Thanks for help:)
>
> There's a separate mailing list for SPARC Linux.

Thanks. Can anyone direct me to the list address?

>
> In this case, you probably just forgot to set up a ->compat_ioctl()
> method in your device's file ops.
>

Yes, indeed. I don't have that method. Now the control is in my ioctl  
function. My new problem is that I don't know much about  
compat_ioctl. Is there any document about it? The only doc I use is  
Linux Device Driver (online version).
Thanks a lot, Mikael:)

-
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/