From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by passt.top (Postfix) with ESMTP id 868415A0262 for ; Mon, 27 Mar 2023 15:02:44 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1679922163; 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: in-reply-to:in-reply-to:references:references; bh=nIHLyxDnlcPLqb5mRfVSKR4E0YVUNSWuYkClneM7zxY=; b=ScD3fi/uX8x4Xz6fqIpgvGcNctX58km1lcEUEt7J1rQ2g3JcYjvM2ODwRAbvWfNTG8WjfW GHwJISDyGpSlNujeJiThPy+b6bKT+oj/8us4URJZt6HxfP83mjHufW3UD/jjNoBh/nQ0qT fI82zdvg2mwcYN0DQoXCf/cgOX3M+30= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-641-5c-mGGKuMCSwFeJLXbNRyQ-1; Mon, 27 Mar 2023 09:02:42 -0400 X-MC-Unique: 5c-mGGKuMCSwFeJLXbNRyQ-1 Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.rdu2.redhat.com [10.11.54.8]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id B5C148556F6; Mon, 27 Mar 2023 13:02:41 +0000 (UTC) Received: from maya.cloud.tilaa.com (unknown [10.33.32.23]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 97350C15BA0; Mon, 27 Mar 2023 13:02:41 +0000 (UTC) Date: Mon, 27 Mar 2023 15:02:32 +0200 From: Stefano Brivio To: "Gianluca Stivan" Subject: Re: Failed to open tun socket in namespace Message-ID: <20230327150232.0cbc1ecc@elisabeth> In-Reply-To: References: <8a314e36-9459-4078-9e6c-db9b8c19464a@app.fastmail.com> <20230327114729.4f7a5c7d@elisabeth> Organization: Red Hat MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.1 on 10.11.54.8 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-ID-Hash: ZHSK7EJ2IMMLHIXJG7SBB7TXZEEL7S3G X-Message-ID-Hash: ZHSK7EJ2IMMLHIXJG7SBB7TXZEEL7S3G X-MailFrom: sbrivio@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: passt-user@passt.top X-Mailman-Version: 3.3.8 Precedence: list List-Id: "For users: support, questions and answers" Archived-At: Archived-At: List-Archive: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: On Mon, 27 Mar 2023 13:22:12 +0100 "Gianluca Stivan" wrote: > Thanks for the reply! > > Here is the ending of the log file: > > ... > > 3944.3562: TCP: index 19, timer expires in 2.000s > 3944.3563: TCP: index 19, timer expires in 2.000s > 3944.3566: TCP: index 19: STALLED > 3944.3578: TCP: index 7: STALLED dropped > 3944.3579: TCP: index 7, timer expires in 2.000s > 3944.3584: TCP: index 7: STALLED > 3944.3586: TCP: index 7: STALLED dropped > 3944.3587: TCP: index 7: ACK_FROM_TAP_DUE dropped > 3944.3588: TCP: index 7: ACK_FROM_TAP_DUE > 3944.3588: TCP: index 7, timer expires in 2.000s > 3944.3589: TCP: index 12: STALLED dropped > 3944.3590: TCP: index 12, timer expires in 2.000s > 3944.3620: tap write: No buffer space available > 3944.3620: TCP: index 17: STALLED dropped > 3944.3620: TCP: index 17: ACK_FROM_TAP_DUE dropped > 3944.4420: ERROR: Failed to open tun socket in namespace > > No buffer space available seems interesting? Interesting, I had never seen ENOBUFS from a tap file descriptor. Let me find out where it might come from (and how pasta should react to it), it might take a bit. What kernel version are you using by the way? I mean, maybe we just have to try again (as if we received EAGAIN): diff --git a/tap.c b/tap.c index 68ef480..21a786d 100644 --- a/tap.c +++ b/tap.c @@ -323,7 +323,8 @@ static size_t tap_send_frames_pasta(struct ctx *c, if (write(c->fd_tap, (char *)iov[i].iov_base, iov[i].iov_len) < 0) { debug("tap write: %s", strerror(errno)); - if (errno != EAGAIN && errno != EWOULDBLOCK) + if (errno != EAGAIN && errno != EWOULDBLOCK && + errno != ENOBUFS) tap_handler(c, c->fd_tap, EPOLLERR, NULL); i--; } but I'm not sure it's correct. You could probably try that as a workaround meanwhile. > PS: let me know if you'd like the full file! No no, thank you, that was enough! About issue number 2. (the fact that we can't actually close and reopen the tap file descriptor after this failure), I'll check if I can easily reproduce that in a Podman setting. -- Stefano