| 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
| ||
|
Date: Wed, 30 May 2007 10:14:31 +0100 From: "Renato Golin" <rengolin@...il.com> To: "Jiri Kosina" <jkosina@...e.cz> Cc: linux-kernel@...r.kernel.org, "Dmitry Torokhov" <dtor@...ightbb.com> Subject: Re: joydev.c and saitek cyborg evo force On 30/05/07, Jiri Kosina <jkosina@...e.cz> wrote: > well I have changed the overall HID code design in 2.6.21 a little bit. > Anyway, just hardcoding '#define DEBUG' and '#define DEBUG_DATA' (that's > also important) in 2.6.20-and-older kernels should have similar result as > CONFIG_HID_DEBUG in post-2.6.21. > > In your particular case, the DEBUG_DATA might really be more interesting. Yup, did both on all drivers/hid/*.c and drivers/usb/input/hid*.c recompiled and reloaded all modules (hid.ko, usbhid.ko and joydev.ko) But it's pathetic the fact that ubuntu's kernel have an option USB_DEBUG and on Makefile is says "if USB_DEBUG; aditional_opt= -DDEBUG" but inside the files all DEBUG flags are hardcoded undefined. Also, to turn on KERN_DEBUG messages I saw on kernel hacking webpages: $ echo 15 15 15 15 > /proc/sys/kernel/printk $ echo 8 > /proc/sys/kernel/printk I did it and monitored mesasges and syslog and both shows the same data... I guess that dump after mouse detection is DEBUG_DATA in place. cheers, --renato Reclaim your digital rights, eliminate DRM, learn more at http://www.defectivebydesign.org/what_is_drm - 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