OK, I've the ideas much more clear.
Thanks for your answer.
Joaquim Duran
2014/1/6 Tim Roberts t...@probo.com
Joaquim Duran wrote:
I'm new to this e-mail list. In the current project, I would like use
a 3rd party library to monitor the IO events on file descriptors,
including libusb
I chose not to use memmove but rather read and write all buffer bytes in a loop
(not sure if memmove would optimize src==dst case). I could successfully
trigger the EFAULT and it did not cause any segfault.
patch (just for reference):
https://gist.github.com/miguelfreitas/8298825
besides i
@jwrdegoede I have read the processcompl() you mention and i agree the only
failure case is when one of the put_user or copy_to_user fails. -EFAULT is the
only error code used there.
Another raw guess: is it possible that data was corrupted during USB transfer
(this actually happens here due
Closed #136 via 314f4ff998f6ba63607ce3be6cd7193a39cd1f78.
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/pull/136--
Rapidly troubleshoot problems before they affect your
Closed #117 via b1bbea6f4f5cadc8ba2f48ae077f0c4ac339c3cc.
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/pull/117--
Rapidly troubleshoot problems before they affect your
Closed #153 via 0500232303fe706dbe538290a49869f1dadf90af.
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/pull/153--
Rapidly troubleshoot problems before they affect your
