| 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: Sun, 10 Dec 2006 16:37:43 +0100 From: Clemens Koller <clemens.koller@...gramm.de> To: unlisted-recipients:; (no To-header on input) CC: linux-kernel@...r.kernel.org Subject: Re: single bit errors on files stored on USB-HDDs via USB2/usb_storage Hi There! > Now, I can imagine a USB slave controller so cheap and/or buggy that it > doesn't check the CRC, but I'd think that most would. Checking a CRC > is hardly a novel challenge. Do we have any counters in the USB Stack and the drivers which count the USB transaction errors? According to some datasheets (i.e. NXP ISP1563) there are bits called USB Error and USB Error Interrupt" etc. Are those should be implemented / counted in the driver stack somewhere? Okay, simple question... A quick look into ehci.h tells me that the bit inside of the kernel is propably called STS_ERR and is used i.e. in ehci_dbg.c 's and printed through dbg_status_buf() and dbg_intr.buf(). Maybe it's sufficient to turn on debugging and turn the error flag into an error counter just to get an idea if it cumulates? Just my five cents, Clemens Koller _______________________________ R&D Imaging Devices Anagramm GmbH Rupert-Mayer-Str. 45/1 81379 Muenchen Germany http://www.anagramm-technology.com Phone: +49-89-741518-50 Fax: +49-89-741518-19 - 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