From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: passt.top; dmarc=pass (p=quarantine dis=none) header.from=redhat.com Authentication-Results: passt.top; dkim=pass (1024-bit key; unprotected) header.d=redhat.com header.i=@redhat.com header.a=rsa-sha256 header.s=mimecast20190719 header.b=HbK2jGnj; dkim-atps=neutral Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by passt.top (Postfix) with ESMTPS id 903425A0271 for ; Sun, 28 Sep 2025 09:30:20 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1759044619; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=hFSpKlN74jguGmsQz7hxhnpOiXv00tydVgf7mcjOOCs=; b=HbK2jGnjZLvuj/oNmD68QjrxtHP06GdPl1W1qDcfueFFCltvGV8w8/khqYM5jJrT71Vfbc LpIhnjoq2c0FYH6/+q/XBQn5joA5ROa6IFdu+HEI0CAaQ+pjoNnlhjAm9F+m5KTx1bf9DY KovEJPtqKKrKRXxqKUF5ugXR9RlnG8c= Received: from mx-prod-mc-05.mail-002.prod.us-west-2.aws.redhat.com (ec2-54-186-198-63.us-west-2.compute.amazonaws.com [54.186.198.63]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-665-debWDqZ5Oa6tv8YtinKLIg-1; Sun, 28 Sep 2025 03:30:15 -0400 X-MC-Unique: debWDqZ5Oa6tv8YtinKLIg-1 X-Mimecast-MFC-AGG-ID: debWDqZ5Oa6tv8YtinKLIg_1759044615 Received: from mx-prod-int-03.mail-002.prod.us-west-2.aws.redhat.com (mx-prod-int-03.mail-002.prod.us-west-2.aws.redhat.com [10.30.177.12]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx-prod-mc-05.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id 305B719774D9; Sun, 28 Sep 2025 07:30:14 +0000 (UTC) Received: from fedora.redhat.com (unknown [10.72.112.39]) by mx-prod-int-03.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTP id 5BB7619560A2; Sun, 28 Sep 2025 07:30:10 +0000 (UTC) From: Yumei Huang To: passt-dev@passt.top, sbrivio@redhat.com Subject: [PATCH 0/2] Retry SYNs for inbound connections Date: Sun, 28 Sep 2025 15:29:44 +0800 Message-ID: <20250928072946.15284-1-yuhuang@redhat.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.0 on 10.30.177.12 X-Mimecast-Spam-Score: 0 X-Mimecast-MFC-PROC-ID: EgFxmYeN0B14J3OuxQI5K6edY9g0--BXf4EnVNrJFs4_1759044615 X-Mimecast-Originator: redhat.com Content-Transfer-Encoding: 8bit content-type: text/plain; charset="US-ASCII"; x-default=true Message-ID-Hash: 6HREY7NMICIZNWPVACTINGPJ7UETB7NT X-Message-ID-Hash: 6HREY7NMICIZNWPVACTINGPJ7UETB7NT X-MailFrom: yuhuang@redhat.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: david@gibson.dropbear.id.au, yuhuang@redhat.com X-Mailman-Version: 3.3.8 Precedence: list List-Id: Development discussion and patches for passt Archived-At: Archived-At: List-Archive: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: When a client connects, SYN would be sent to guest only once. If the guest is not connected or ready at that time, the connection will be reset in 10s. These patches introduce the SYN retry mechanism similar to retransmits. Tested two scenarios: 1) A guest is connected in a few seconds, the client connects to the guest successfully. 2) No guest connects at all, the client gets "Connection reset" in 80s. Also ran the testsuits, no regression issue introduced. Yumei Huang (2): tcp: Rename "retrans" of struct tcp_tap_conn and tcp_tap_transfer tcp: Resend SYN for inbound connections tcp.c | 21 ++++++++++++++------- tcp_conn.h | 8 ++++---- 2 files changed, 18 insertions(+), 11 deletions(-) -- 2.47.0