linux-kernel - Re: recv() hangs until SIGCHLD ?

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Mon, 13 Oct 2008 17:02:41 +0200
From:	Nicolas Cannasse <ncannasse@...ion-twin.com>
To:	Stephen Hemminger <shemminger@...tta.com>
CC:	linux-net@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: recv() hangs until SIGCHLD ?

Nicolas Cannasse a écrit :
>>> If there is data and the thread didn't wake up then that is a libc or 
>>> kernel problem;
>>> but if there is no data, then look for cases where earlier 
>>> interrupted io actually
>>> consumed the data already or blame the sending process not the receiver.
>>> Also are the sockets blocking or non-blocking?

One other thing :

We tried to use a poll(POLLIN) on the socket before entering the recv(). 
The poll() does exit (and we are looping in case of EINTR result) but 
after that recv() blocks infinitely.

Hope that helps,

Nicolas

--
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/