On Sun, 14 Nov 2010 21:24:46 +0100 NÃmeth MÃrton <nm127@xxxxxxxxxxx> wrote: > >> (a) the transfered size equals to 800+800+800+800+800+170=4170 bytes, so the > >> iso desc 0...4 are fully transfered and the useful data from isodesc 5 > >> > >> (b) the transfered size equals to 800+800+800+800+800+800=4800 bytes, so the > >> iso desc 0...5 are fully transfered > >> > >> (c) the transfered size equals to maximum possible size always, in this case > >> 24*800=19200 bytes > > > > I see you went for (a). I leaned towards (c), just for simplicity. > > The (c) solution would work also, it has the drawback that in that way > the kernel gives away the most uninitialized buffer content. Normally > it only contains remaining bytes from the previous URB data and not > leaking out any sensitive information. I do not think the leakage in this case is a particular concern, because any program that can do mmap() can scan the whole buffer. The reported offsets are purely advisory. Moreover, the program that merely reads can read your keyboard input. Therefore, leaking a bit more is no worse than before. Access to usbmon must always be protected by permissions in /dev. -- Pete -- 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
