diff options
author | Pete Zaitcev <zaitcev@redhat.com> | 2008-11-14 11:47:41 -0500 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@kvm.kroah.org> | 2008-11-20 01:01:35 -0500 |
commit | f1c0a2a3aff53698f4855968d576464041d49b39 (patch) | |
tree | e5b247b91ce77706a1d1cdb3b7421bca6a295c32 /drivers/sh | |
parent | ff3495052af48f7a2bf7961b131dc9e161dae19c (diff) |
USB: usbmon: fix read(2)
There's a bug in the usbmon binary reader: When using read() to fetch
the packets and a packet's data is partially read, the next read call
will once again return up to len_cap bytes of data. The b_read counter
is not regarded when determining the remaining chunk size.
So, when dumping USB data with "cat /dev/usbmon0 > usbmon.trace" while
reading from a USB storage device and analyzing the dump file
afterwards it will get out of sync after a couple of packets.
Signed-off-by: Ingo van Lil <inguin@gmx.de>
Signed-off-by: Pete Zaitcev <zaitcev@redhat.com>
Cc: stable <stable@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'drivers/sh')
0 files changed, 0 insertions, 0 deletions