| 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: Sun, 11 Jan 2009 23:45:43 +0100 From: bert hubert <bert.hubert@...herlabs.nl> To: "H. Willstrand" <h.willstrand@...il.com> Cc: netdev@...r.kernel.org Subject: sendfile()? Re: SO_LINGER dead: I get an immediate RST on 2.6.24? On Sun, Jan 11, 2009 at 11:08:16PM +0100, H. Willstrand wrote: > > Is SO_LINGER a NOOP? Does it still do anything? > This is the correct behavior according to RFC 2525, see section 2.17 > (there are an example). Ah - very good, thank you. I'm trying to gather as much information as I can before writing this all up. This should save netdev & the linux kernel community a lot of email! Is there any way to make sure there is no pending output data, so one can safely call close(), and not get an RST-situation? Let me put it more succinctly. What I would very much like to have is what Linux sendfile() offers in practice. It appears that if one asks sendfile() to transmit a million bytes, it will only return when the ACK for the millionth byte is in. I know that TCP will never be fully fully reliable, but I would love to have a way to know that the millionth byte was ACKed, or alternatively, that an error prevented that. >From what I've read so far, I think the POSIX functions don't offer this. But does Linux? sendfile appears to get it right.. Thanks. -- http://www.PowerDNS.com Open source, database driven DNS Software http://netherlabs.nl Open and Closed source services -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists