On Sun, Dec 28, 2008 at 11:41 PM, Alan Stern <stern@xxxxxxxxxxxxxxxxxxx> wrote: > On Sun, 28 Dec 2008, Erik Ekman wrote: >> >> I have now uploaded two usbmon logs. > > These logs show you running the program twice? The time gap between > the two runs is no longer than 2 ms! That's certainly not what I would > expect. Have you tried something more reasonable, like a second or > longer? I should explain what the tf-tool does. I ran it with option --acquire which means you swipe three times and it produces a file which is the recorded fingerprint. I dont know what interval is 2 ms, I sure didnt run it that way. > > There's no difference between the logs corresponding to the behavior > you described. The interaction between the program and the device in > the short log is the same as in the long log, right up until the time > the short log ends. > > In more detail: The two logs begin the same. The first program run > ends with a 64-byte bulk-IN transfer from the device. After that the > "reverted" log shows a Set-Interface request; the vanilla log doesn't > include this request because the commit prevents it from being sent. > But this is invisible to the program, since it occurs after the first > run and before the second run. > > Then the program was started again (after a _very_ short delay) and > both logs show a Set-Config request followed by a 1-byte > Vendor-specific control-OUT transfer. This same pair of requests also > occurs at the beginning of both logs, which confirms that it marks a > new start of the program. Both the Set-Config and the control-OUT > succeeded. > > Then the "reverted" log shows the program going on to send a bulk-IN > request and do more bulk transfers, whereas the "vanilla" log shows no > more activity. Clearly this has nothing to do with the presence or > absence of the Set-Interface request; the program has no way to know > whether or not that request was sent because it receives the same > information from the device in either case. The "reverted" log shows a full fingerprint acquire with three swipes, all in the same run of tf-tool. The shorter log shows an attempt to do it, but tf-tool stopped with an error before I could swipe anything. > > In short, the "vanilla" log shows the second program run stopping short > for no apparent reason. There is no evident connection with the commit > you identified. I agree, but I am the second one who independently bisected and found this exact commit. > > Alan Stern > > I have now done a second round of usbmon captures, and I will upload them shortly. This time I have added pam_thinkfinger.so as sufficient for system login, and have recorded login attempts with and without the specific commit in the kernel. Stock 2.6.28 did not log me in, I had to write a password. dmesg shows: input: Virtual ThinkFinger Keyboard as /class/input/input8 usb 5-2: usbfs: process 5539 (login) did not claim interface 0 before use usb 5-2: usbfs: process 5539 (login) did not claim interface 0 before use usb 5-2: usbfs: process 5539 (login) did not claim interface 0 before use usb 5-2: usbfs: process 5539 (login) did not claim interface 0 before use usb 5-2: usbfs: process 5539 (login) did not claim interface 0 before use usb 5-2: usbfs: process 5539 (login) did not claim interface 0 before use usb 5-2: usbfs: process 5539 (login) did not claim interface 0 before use usb 5-2: usbfs: process 5539 (login) did not claim interface 0 before use usb 5-2: usbfs: process 5539 (login) did not claim interface 0 before use usb 5-2: usbfs: process 5539 (login) did not claim interface 0 before use usb 5-2: usbfs: process 5539 (login) did not claim interface 0 before use usb 5-2: usbfs: process 5539 (login) did not claim interface 0 before use usb 5-2: usbfs: process 5539 (login) did not claim interface 0 before use usb 5-2: usbfs: process 5539 (login) did not claim interface 0 before use usb 5-2: usbfs: process 5539 (login) did not claim interface 0 before use usb 5-2: usbfs: process 5539 (login) did not claim interface 0 before use usb 5-2: usbfs: process 5539 (login) did not claim interface 0 before use usb 5-2: usbfs: process 5539 (login) did not claim interface 0 before use usb 5-2: usbfs: process 5539 (login) did not claim interface 0 before use usb 5-2: usbfs: process 5538 (login) did not claim interface 0 before use Bus 5, device 2 is my reader: Bus 005 Device 002: ID 0483:2016 SGS Thomson Microelectronics Fingerprint Reader 2.6.28 minus the commit lets me in when I swipe, and dmesg only shows: input: Virtual ThinkFinger Keyboard as /class/input/input8 /Erik -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
