lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 16 Dec 2010 08:31:34 +0100 From: Németh Márton <nm127@...email.hu> To: gregkh <gregkh@...e.de>, devel@...verdev.osuosl.org CC: LKML <linux-kernel@...r.kernel.org> Subject: Re: usbip: somtimes stalls at kernel_recvmsg() 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists