| 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
| ||
|
Message-ID: <F7F9B0BE3E9BD449B110D0B1CEF6CAEF03FA5863@ABGEX01E.abg.fsc.net> Date: Mon, 27 Nov 2006 09:24:24 +0100 From: "Cestonaro, Thilo \(external\)" <Thilo.Cestonaro.external@...itsu-siemens.com> To: <linux-kernel@...r.kernel.org> Subject: Weird wasting of time between ioctl() and ioctl dispatcher Hey, I'm a developer for Fujitsu Siemens Computers, working on a program which has it's own kernel modules and userland components. Now cause the program should be released we have done some testing and during this testphase a wierd wasting of time occured during the call of the ioctl() in the userland component and the actuall entering of the dispatcher function in the module. It takes 3 min. until the call at last enters my dispatcher. (Debugging output with printf on line before ioctl() and printk as first line in the dispatch function points that out). The dispatch function is the ioctl part of the fileoperations struct which defines the module stuff. The kernel I'm running is the 2.6.16.21-0.8-default of SLED10 (32Bit), but installed on a 64Bit machine. Can anyone point me to, where I can have a look where the waste of time comes from? The ioctl itself works fine afterwards, but the whole process is time-critical so the 3 min. do hurt :(. Ciao Thilo - 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/
Powered by blists - more mailing lists