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 F37425A026F for ; Fri, 10 Nov 2023 14:51:56 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1699624315; 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=zt96518PzuqvcPZAv25EnDXhfeOUJD8NFIFElIReVlM=; b=PCa56l47KBbPM0PcrVJZaZ6qYTGpODpWBDfaH0IyIUCl9hSIdH9227MS6dm0IL2t7ZtLcq TW4sl+PsgF43g02/u77pWbcW58JJhLamxZgaU1SDDE400nybC1xCoh27oV33kVAXosRNp/ iIEAMt9/N9JpaAMfBpM7vQqcegpLkCU= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-223-i7_VRpm4PBifPik82cK6mA-1; Fri, 10 Nov 2023 08:51:54 -0500 X-MC-Unique: i7_VRpm4PBifPik82cK6mA-1 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.rdu2.redhat.com [10.11.54.7]) (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 mimecast-mx02.redhat.com (Postfix) with ESMTPS id 89F42101A529; Fri, 10 Nov 2023 13:51:54 +0000 (UTC) Received: from elisabeth (unknown [10.39.208.5]) by smtp.corp.redhat.com (Postfix) with ESMTPS id C33F31C060AE; Fri, 10 Nov 2023 13:51:53 +0000 (UTC) Date: Fri, 10 Nov 2023 14:51:51 +0100 From: Stefano Brivio To: David Gibson Subject: Re: [PATCH 0/2] Handle incomplete tap writes for pasta Message-ID: <20231110145151.3877ba6a@elisabeth> In-Reply-To: <20231108031754.2670078-1-david@gibson.dropbear.id.au> References: <20231108031754.2670078-1-david@gibson.dropbear.id.au> Organization: Red Hat MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.4.1 on 10.11.54.7 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-ID-Hash: 7UG3LDIHFVK5PJMWVG34LTO5O7STGAMH X-Message-ID-Hash: 7UG3LDIHFVK5PJMWVG34LTO5O7STGAMH 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-dev@passt.top 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: On Wed, 8 Nov 2023 14:17:52 +1100 David Gibson wrote: > passt can handle various cases where we're unable to write all the > data we want to to the tap side. The same logic would make sense for > pasta, however right now we don't properly report incomplete writes > with the tuntap device of pasta, rather than the qemu socket of passt. > > I come across these as possible issues with the various stall bugs > we've been investigating. It doesn't look like they're relevant there > after all, but they should be correct changes nonetheless. > > David Gibson (2): > tap, pasta: Handle incomplete tap sends for pasta too > tap, pasta: Handle short writes to /dev/tap Applied. -- Stefano