| 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: Sat, 11 Oct 2008 11:30:53 +0200 From: Samuel Thibault <samuel.thibault@...-lyon.org> To: David Schwartz <davids@...master.com> Cc: linux-kernel@...r.kernel.org Subject: Re: recv() hangs until SIGCHLD ? David Schwartz, le Fri 10 Oct 2008 21:48:45 -0700, a écrit : > > We are using the Boehm GC which uses the signals SIGXCPU and SIGPWR to > > pause+restart the threads when running a GC cycle. > > [...] > > > > However, when attaching GDB to our locked thread it seems that even > > when the GC runs, recv() does not exit (the breakpoint after it is not > > reached). > > But you've yet to explain why it should return. Was it interrupted by > a signal? See quote above. > Was data received? No > Is the socket non-blocking? No > Why isn't this expected behavior? Blocking sockets block, full stop. But using a signal is a common technique to have it getting unblocked, since SUS says « [EINTR] The recv() function was interrupted by a signal that was caught, before any data was available. » Samuel -- 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