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: Fri, 3 Jun 2022 13:09:32 +0000 From: David Laight <David.Laight@...LAB.COM> To: 'Frederik Deweerdt' <frederik.deweerdt@...il.com>, Willem de Bruijn <willemdebruijn.kernel@...il.com> CC: "netdev@...r.kernel.org" <netdev@...r.kernel.org> Subject: RE: [PATCH] [doc] msg_zerocopy.rst: clarify the TCP shutdown scenario From: Frederik Deweerdt <frederik.deweerdt@...il.com> > Sent: 02 June 2022 00:01 > > > > A socket must not be closed until all completion notifications have > > been received. > > > > Calling shutdown is an optional step. It may be sufficient to simply > > delay close. What happens if the process gets killed - eg by SIGSEGV? David - Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK Registration No: 1397386 (Wales)
Powered by blists - more mailing lists