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
| ||
|
Message-ID: <561B1BB6.2060208@oracle.com> Date: Sun, 11 Oct 2015 19:32:22 -0700 From: "santosh.shilimkar@...cle.com" <santosh.shilimkar@...cle.com> To: Sowmini Varadhan <sowmini.varadhan@...cle.com>, netdev@...r.kernel.org, linux-kernel@...r.kernel.org Cc: davem@...emloft.net, rds-devel@....oracle.com, ajaykumar.hotchandani@...cle.com, igor.maximov@...cle.com Subject: Re: [PATCH net-next] RDS-TCP: Reset tcp callbacks if re-using an outgoing socket in rds_tcp_accept_one() On 10/11/15 1:49 PM, Sowmini Varadhan wrote: > > Consider the following "duelling syn" sequence between two peers A and B: > A B > SYN1 --> > <-- SYN2 > SYN2ACK --> > > Note that the SYN/ACK has already been sent out by TCP before > rds_tcp_accept_one() gets invoked as part of callbacks. > > If the inet_addr(A) is numerically less than inet_addr(B), > the arbitration scheme in rds_tcp_accept_one() will prefer the > TCP connection triggered by SYN1, and will send a CLOSE for the > SYN2 (just after the SYN2ACK was sent). > > Since B also follows the same arbitration scheme, it will send the SYN-ACK > for SYN1 that will set up a healthy ESTABLISHED connection on both sides. > B will also get a CLOSE for SYN2, which should result in the cleanup > of the TCP state machine for SYN2, but it should not trigger any > stale RDS-TCP callbacks (such as ->writespace, ->state_change etc), > that would disrupt the progress of the SYN2 based RDS-TCP connection. > > Thus the arbitration scheme in rds_tcp_accept_one() should restore > rds_tcp callbacks for the winner before setting them up for the > new accept socket, and also make sure that conn->c_outgoing > is set to 0 so that we do not trigger any reconnect attempts on the > passive side of the tcp socket in the future, in conformance with > commit c82ac7e69efe ("net/rds: RDS-TCP: only initiate reconnect attempt > on outgoing TCP socket.") > > Signed-off-by: Sowmini Varadhan <sowmini.varadhan@...cle.com> > --- Looks fine to me. Acked-by: Santosh Shilimkar <santosh.shilimkar@...cle.com> -- 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