NÃmeth MÃrton wrote: > I'm working with usbip and I sometimes see a stall when I run > the "lsusb" command from the userspace. I added some debug messages > and it seems that the kernel_recvmsg() in > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=drivers/staging/usbip/usbip_common.c;h=210ef16bab8d271a52e5d36cd1994aad57ad99e1;hb=HEAD > > This is the only place I could find where the TCP messages are arriving in > the usbip code. > > What happens if a message does not arrive? Does it stall forever? If > yes, how can the kernel_recvmsg() call changed to handle some timeout? I found that the userspace manpage of recvmsg(2) ("man recvmsg") contains description of the "flags" parameter. I suppose the parameters and behaviour of the userspace recvmsg() is the same as the kernelspace kernel_recvmsg(). MÃrton NÃmeth _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/devel
