usbip bind writes commands followed by random string when writing to
match_busid attribute in sysfs, caused by using full variable size
instead of string length.
Signed-off-by: Juan Zea <juan@qindel.com>
---
tools/usb/usbip/src/utils.c | 9 ++---
1 file changed, 6 insertions
> Why not use the return value from snprintf() for length, instead of calling
strlen(command)?
Yes, that makes sense. Something like this?
diff --git a/tools/usb/usbip/src/utils.c b/tools/usb/usbip/src/utils.c
index 2b3d6d2..3d7b42e 100644
--- a/tools/usb/usbip/src/utils.c
+++
usbip bind writes commands followed by random string when writing to
match_busid attribute in sysfs, caused by using full variable size
instead of string length.
Signed-off-by: Juan Zea <juan@qindel.com>
---
tools/usb/usbip/src/utils.c | 2 +-
1 file changed, 1 insertion(+), 1 de
usbip bind writes commands followed by random string when writing to
match_busid attribute in sysfs, caused by using full variable size
instead of string length.
Signed-off-by: Juan Zea <juan@qindel.com>
---
tools/usb/usbip/src/utils.c | 2 +-
1 file changed, 1 insertion(+), 1 de
attribute(match_busid_attr_path, command,
- sizeof(command));
+ strlen(command));
if (rc < 0) {
dbg("failed to write match_busid: %s", strerror(errno));
return -1;
Regards,
Juan Z
>On 11/29/2017 07:25 PM, Yuyang Du wrote:
>> Hi Shuah,
>>
>> On Tue, Nov 28, 2017 at 05:09:18PM -0700, Shuah Khan wrote:
>>> On 11/28/2017 11:32 AM, Shuah Khan wrote:
>>>> On 11/26/2017 06:33 PM, Yuyang Du wrote:
>>>>> Hi Juan,
>>>
> De: "Yuyang Du" <yuyang...@linux.intel.com>
> Para: "Juan Zea" <juan@qindel.com>
> CC: "Shuah Khan" <shua...@osg.samsung.com>, sh...@kernel.org, "Bjørn Mork"
> <bj...@mork.no>, linux-usb@vger.kernel.org, "Valen
Hi Yuyang,
>
> - Mensaje original -
> De: "Yuyang Du" <yuyang...@linux.intel.com>
> Para: "Juan Zea" <juan@qindel.com>
> CC: "Shuah Khan" <shua...@osg.samsung.com>, sh...@kernel.org, "Bjørn Mork"
> <
> - Mensaje original -
> De: "Yuyang Du" <yuyang...@linux.intel.com>
> Para: "Shuah Khan" <shua...@osg.samsung.com>
> CC: "Juan Zea" <juan@qindel.com>, sh...@kernel.org, "Bjørn Mork"
> <bj...@mork.no>
>>Also, will you be able to revert the usb3 commit
>>1c9de5bf428612458427943b724bea51abde520a
>>
>>and see if any of the problems go away.
>>
>>thanks,
>>-- Shuah
>>
>I'm on it and will send results later.
>Thanks,
>Juan
Ok, I'm back. The revert was quite complex, with several conflicts I
>On 11/14/2017 09:25 AM, Juan Zea wrote:
>> Hi,
>>
>> I've been working on the issue. This is what I found about multi-controller
>> setup:
>>
>> The problem comes from the usbip tool trying to connect usb2 devices to usb3
>> ports, like this:
toría | Qindel Group
E: juan@qindel.com
T: +34 91 766 24 21
M: +34 637 74 63 09
W: qindel.com
- Mensaje original -
De: "Bjørn Mork" <bj...@mork.no>
Para: "Juan Zea" <juan@qindel.com>
CC: linux-usb@vger.kernel.org, "Valentina Manea" <val
Hi,
My name is Juan, and I work for Qindel, a small IT company based in Spain. I'm
currently trying to do some development for our main product QVD. Specifically,
I'm trying to get usbip to work with a great number of LXC containers. Due to
the nature of LXC, all usbip ports are shared among
13 matches
Mail list logo
