Received: by 2002:a05:6358:3188:b0:123:57c1:9b43 with SMTP id q8csp2740508rwd; Fri, 2 Jun 2023 14:05:19 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ7i3LHURhpqR9D6AiNHOtiwElTtz5pA5LhsrmK9UmiCbrBijO91EZ3GgADHxzBSO1Y0noGX X-Received: by 2002:a17:90a:290a:b0:255:d86c:baec with SMTP id g10-20020a17090a290a00b00255d86cbaecmr941951pjd.46.1685739919432; Fri, 02 Jun 2023 14:05:19 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1685739919; cv=none; d=google.com; s=arc-20160816; b=H3KzL6OHA3FQUguKxU6LQ6RrrwOI3vII4HS8SI6qt017Tc8W5R710vDVQ7eSKzV/bP fLmQrBBGYqSQSL83f6mRLQ5V2/tZRSmfaMvFTiKxhCe9atXt4GN+/h1aTvrRoHJtcqQr gJ7xQo4skJfwfOVjrr+EMiA+OLLCqrYrm0IB+XISqDxnV1Jq1AY5Yf+Cb2rVbOxNTO1O uq7xcdWVK/fRDGMcPUejVZhfaMfI0EgJx6KAOFGoi1sNodyOkMbLJVj6PM/2j0v3LiBZ 9rs+fdIwZGDgsfHMFQ3OOakGNP/7f1ds+LYQoVY5GG/tspgZRFsr1/e1z3lyY22odb1i zdYQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:message-id:date:content-id:mime-version:subject :cc:to:references:in-reply-to:from:organization:dkim-signature; bh=kDXag6ERXSwL7GTlshgGFCN28zZ5vFNYvwGpuwj8Ui0=; b=t+HC4lwMQaTQhO3dxWCSn4jHLesQpbPNlmSZcJf7u39sVs9w081851XS2boEUm5xjQ IrKFzqLtNjBMEqZpt/KfjJG9jua9CxXLPw7vYE6IFZ06dOMb2ZsE/45SIsh+nyW8ppUh SiZuK245zM1yLdSrbT+/JOK/SKqLLz5b1RYGonAdd3CsD+El90PVyJhPyNOozLqkHDZw 6j+/leOIx31IT0QqkVkw2zeiVXzHfIk2/Y5lz5ZJq+BlKcJ5I2Heh8PqgyKErmgnEFZQ Si8gaNEbK9//YJN1SBANBZpKhRV/K1KOeZu2atirJFgVu47S00dPaI3pMcmX8ntWnNuf UfKg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=gqWuXTcN; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id ng13-20020a17090b1a8d00b0025026c97f40si3461198pjb.145.2023.06.02.14.05.04; Fri, 02 Jun 2023 14:05:19 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=gqWuXTcN; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236162AbjFBUvI (ORCPT + 99 others); Fri, 2 Jun 2023 16:51:08 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:59804 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235596AbjFBUvH (ORCPT ); Fri, 2 Jun 2023 16:51:07 -0400 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D1F6CE43 for ; Fri, 2 Jun 2023 13:50:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1685739016; 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: in-reply-to:in-reply-to:references:references; bh=kDXag6ERXSwL7GTlshgGFCN28zZ5vFNYvwGpuwj8Ui0=; b=gqWuXTcNqlGMrQ1fJ8dATrOs8ZIB9SwcsvTPXfef2b9qnj1teQ5ybuN1y4Mea1XztPLYCg 9McNwwlOyRmouqjlFyOLMdmjvNZ4KOL/JpAygn9R5ZlU7a7731202S1sHHPAgCIFkqaf9X /PAdUlIsjKxY1Mt87Krq6Z6JeOcQ368= Received: from mimecast-mx02.redhat.com (mx3-rdu2.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-14-Gnf_G1T2M7aFa0DgVEYz3w-1; Fri, 02 Jun 2023 16:50:11 -0400 X-MC-Unique: Gnf_G1T2M7aFa0DgVEYz3w-1 Received: from smtp.corp.redhat.com (int-mx10.intmail.prod.int.rdu2.redhat.com [10.11.54.10]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 5B9CB29AA3B7; Fri, 2 Jun 2023 20:50:10 +0000 (UTC) Received: from warthog.procyon.org.uk (unknown [10.42.28.182]) by smtp.corp.redhat.com (Postfix) with ESMTP id 27D9D492B0A; Fri, 2 Jun 2023 20:50:08 +0000 (UTC) Organization: Red Hat UK Ltd. Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SI4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 3798903 From: David Howells In-Reply-To: References: <20230524153311.3625329-1-dhowells@redhat.com> <20230524153311.3625329-10-dhowells@redhat.com> <20230526180844.73745d78@kernel.org> <499791.1685485603@warthog.procyon.org.uk> <832277.1685630048@warthog.procyon.org.uk> <909595.1685639680@warthog.procyon.org.uk> <20230601212043.720f85c2@kernel.org> <952877.1685694220@warthog.procyon.org.uk> <1227123.1685706296@warthog.procyon.org.uk> <20230602093929.29fd447d@kernel.org> To: Linus Torvalds Cc: dhowells@redhat.com, Jakub Kicinski , netdev@vger.kernel.org, "David S. Miller" , Eric Dumazet , Paolo Abeni , Willem de Bruijn , David Ahern , Matthew Wilcox , Jens Axboe , linux-mm@kvack.org, linux-kernel@vger.kernel.org, Chuck Lever , Boris Pismenny , John Fastabend , Christoph Hellwig Subject: Re: Bug in short splice to socket? MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1380698.1685739007.1@warthog.procyon.org.uk> Date: Fri, 02 Jun 2023 21:50:07 +0100 Message-ID: <1380699.1685739007@warthog.procyon.org.uk> X-Scanned-By: MIMEDefang 3.1 on 10.11.54.10 X-Spam-Status: No, score=-2.3 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_NONE,T_SCC_BODY_TEXT_LINE autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Linus Torvalds wrote: > BUT with the small new 'splice_eof()' rule that: > > - if the user did *not* set SPLICE_F_MORE *and* we didn't hit that > "use all of len" case that cleared SPLICE_F_MORE, *and* we did a > "->splice_in()" that returned EOF (ie zero), *then* we will also do > that ->splice_eof() call. But not if we didn't splice anything at all yet? David