Received: by 2002:a05:6358:3188:b0:123:57c1:9b43 with SMTP id q8csp27466269rwd; Tue, 4 Jul 2023 03:26:26 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ47JlXBeVIZYxz2z6EZQXmVeTF1PmNbYyh12NGvrHAUxbuDxKQwHvNMeo1Km936GpU74V9z X-Received: by 2002:a05:6a20:8f03:b0:116:696f:1dd1 with SMTP id b3-20020a056a208f0300b00116696f1dd1mr19380518pzk.4.1688466386391; Tue, 04 Jul 2023 03:26:26 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1688466386; cv=none; d=google.com; s=arc-20160816; b=g78Vr6nM6HVyCYq0v9e0hsgbl/318J14+MbwtbKFRGv1hpovs4PPkWYHFfq/FCJwMb KWkw/irQuVwIRh2f5nXql+PHtRpIOsLd+zflwEtvx0kOLxay0nz5O60KOfLDbXbhMaE4 M7uqnmzslDx+O1U9BRysxaA2omQa5DxldLWE78+YV0bmEakVfNblCdQF9mvOf8c9wKdc h4XP4JE2mIpwAL+ypNNcvN0SM6Y3wAzEzofkiCacFI04S0CMfFtQKkoQctcXJ/H2QF/M 1ED/sWW2f1MQfrldVGIFeKU9QatlCwl6W0iThV/mqCwpO6yugK3pYna1tMYOWkGs8aOT 1akA== 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=zLSEosjlinrCxKCLRBdlkkdM07HJXUp3DKjWoDpchWo=; fh=Lgj7/4YCMzpbxEkOSqHXF/brFvxy9psJMb1UFJmdkQU=; b=PMxAA1ucAk9BNftBAizgCinOjIf6x+lNoKf2LxnZ6R2bENOMPUWHI271CgNpC4xpUI goI1EjBPFsud9YLfo2kqFb/hBGuO8gsKiF7qFsEtG5AywDTezwFK/WKBWfeOWeTwx6m7 5WPMYpZo76BIatwmmqo7Ai94dVCcF3T2oPI+Gn8XgNo0hreykzr6HlceiMlX8E5zWNGt 402TD86JGe3Ni5rRMwEkGp/H/8Yun1bM1Ym1QX8+UM0qMHevUpCGFps5k6Nh+sNBnSpt kMs7sTCzmrYZl88v0EHHLPolEDhbpvLFR1ER+ZfeAr9c8e7YcHOZNOrPwpmXVHUkwW0u AhAA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=BmO1hTry; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-crypto-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 ik12-20020a170902ab0c00b001b88c2ee5a8si5743181plb.628.2023.07.04.03.26.10; Tue, 04 Jul 2023 03:26:26 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-crypto-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=BmO1hTry; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-crypto-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 S231904AbjGDJn7 (ORCPT + 99 others); Tue, 4 Jul 2023 05:43:59 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56294 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230335AbjGDJne (ORCPT ); Tue, 4 Jul 2023 05:43:34 -0400 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B6A12138 for ; Tue, 4 Jul 2023 02:41:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1688463710; 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=zLSEosjlinrCxKCLRBdlkkdM07HJXUp3DKjWoDpchWo=; b=BmO1hTry8LXUZPn1AsPPS4fXe/hWf5iyfG4fi5WyyP2JJZguAV/tx2c8orHqTZNiu4Vsqx D5zdtbnOdq3ggEt/3KiEKSzVexY7fYs395FC0ByCunJviH4TH5JtmGvOHLpoot8xnPih/F npCk56EuajAvTLFm+/zhz/CY24kQi2o= 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-447-UDuYkHNINm63hneICkQI6g-1; Tue, 04 Jul 2023 05:41:47 -0400 X-MC-Unique: UDuYkHNINm63hneICkQI6g-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 6201C3814950; Tue, 4 Jul 2023 09:41:47 +0000 (UTC) Received: from warthog.procyon.org.uk (unknown [10.42.28.195]) by smtp.corp.redhat.com (Postfix) with ESMTP id 81309492C13; Tue, 4 Jul 2023 09:41:46 +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: <1357760.1688460637@warthog.procyon.org.uk> To: Herbert Xu Cc: dhowells@redhat.com, Ondrej Mosnacek , Linux Crypto Mailing List , Paolo Abeni , netdev@vger.kernel.org, Linux Kernel Mailing List , regressions@lists.linux.dev Subject: Re: Regression bisected to "crypto: af_alg: Convert af_alg_sendpage() to use MSG_SPLICE_PAGES" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1361503.1688463705.1@warthog.procyon.org.uk> Date: Tue, 04 Jul 2023 10:41:45 +0100 Message-ID: <1361504.1688463705@warthog.procyon.org.uk> X-Scanned-By: MIMEDefang 3.1 on 10.11.54.10 X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H4,RCVD_IN_MSPIKE_WL,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-crypto@vger.kernel.org Herbert Xu wrote: > All it's saying is that if you modify the data after sending it off > via splice then the data that will be on the wire is undefined. Er, no. It can literally remove the page from the process's VM and paste it somewhere else - though in this case, that shouldn't happen. However, the buffer passed to SPLICE_F_GIFT should also be page-aligned, which it might not be because they used calloc(). There's no reason to use SPLICE_F_GIFT here. vmsplice() still attaches the > There is no reason why this should crash. Agreed. I'm still looking at it. Interestingly, the output comes out the same, no matter whether vmsplice(), vmsplice() + SPLICE_F_GIFT or writev(), so it looks like the buffers get to > If we can't fix this the patches should be reverted. I didn't change vmsplice() or the way pages are stored in the pipe. And, note, there are also a bunch of GUP changes that could have an effect. David