Received: by 2002:a05:6358:d09b:b0:dc:cd0c:909e with SMTP id jc27csp558929rwb; Wed, 16 Nov 2022 04:48:51 -0800 (PST) X-Google-Smtp-Source: AA0mqf7gl+R72A49I54o7eOn7tmip/rFA7JjUov9ju/ZX8iDD/weVOMJ/m/n82124IO0/2PG3wE/ X-Received: by 2002:a17:907:1749:b0:78d:4f05:6ba7 with SMTP id lf9-20020a170907174900b0078d4f056ba7mr17703501ejc.590.1668602931100; Wed, 16 Nov 2022 04:48:51 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1668602931; cv=none; d=google.com; s=arc-20160816; b=IDju1D2MIIPm7GZIj8rmts2UVe3X+aqdMcNFjAUKxdslKHHfppsuLXkTARfv4cGmeb H09RiyMsaPOUFwtD/Ax5tcZvIJOOjmhVMmQUmPXjXioXf8ugrptxUau2wEWehkOoSAzk DbwghOZtYEtSUKPImzeNk9H7YBl5fPhLzmXAEvue0qKlC2pSy4/RQYIN70rc+1fiJHYV 4HJ6FvITDsfb6FLuNxUwz9QyosknWMv1LJchEsCYN4QGDjoAov4ocfm0nF1+3G6LqXiP W7hoM8zOUcTsbNjYYVQSPBOBBSq5Vd4Fk3PKJTDpikqRbV+aievzM9znZd/ps+PB8E0n Zt/Q== 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-transfer-encoding :content-id:mime-version:subject:cc:to:references:in-reply-to:from :organization:dkim-signature; bh=M5xy5cnF/duk7VrcsTyDcdzn9i/3nmmpMTSFAVYO+a0=; b=Iul4m3sCZk+FauASd1tptU8iDeVT5JjmgYj5sx1WZkHmJI6fynf7idm+MCKEuCrDff HWutxML6qQPBLAWCWr0eSRx7kSNT0ghEsUjVJ87KgRiCmcaVifOWjheyu1uRxDeOJ7E9 fYQISgVnP3pwhvbDSiG8qLNeQWN7M10EsytkYWo7Ttu13XRIqaVJbak/gaqn3PXNass5 tGYiD4nVrtnYzTQpWHSSRWKGkNiS6hqiuyNWm4d5fARl0nP8uSKOFqoF4Gtdx4H5wztR lZrS6Ow5Zsx/JYHFGnpVZ0jk4622CL9uU+4xO+ydoQbmIL5h1xXktn3C+L2CWi3zssJj tzBA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=GTQgBm0R; 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 qf29-20020a1709077f1d00b0078e27ef9501si15112059ejc.750.2022.11.16.04.48.28; Wed, 16 Nov 2022 04:48:51 -0800 (PST) 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=GTQgBm0R; 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 S232590AbiKPMUS (ORCPT + 91 others); Wed, 16 Nov 2022 07:20:18 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:35256 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233610AbiKPMTN (ORCPT ); Wed, 16 Nov 2022 07:19:13 -0500 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 D20E824D for ; Wed, 16 Nov 2022 04:15:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1668600903; 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=M5xy5cnF/duk7VrcsTyDcdzn9i/3nmmpMTSFAVYO+a0=; b=GTQgBm0RcHOLa/XzfqYnbEwOPd0Qk9ddL8iPTYLi7PDeHyKlcCR5uRbJXTY4qoMZIcE0zh 0JH98b0Cc3Wc1wXDYcm+ygI3A4e7IO89JGQXoS33S6cxrckBXvZ9JziJul2b5T0pkjYahu iuTdmP2kWIjsXx+LIoxIcyfy4+5b9gk= 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-563-Di9W9ovmOXC8d3Aj66WJ7Q-1; Wed, 16 Nov 2022 07:14:56 -0500 X-MC-Unique: Di9W9ovmOXC8d3Aj66WJ7Q-1 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.rdu2.redhat.com [10.11.54.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 09E9D2999B45; Wed, 16 Nov 2022 12:14:56 +0000 (UTC) Received: from warthog.procyon.org.uk (unknown [10.33.36.24]) by smtp.corp.redhat.com (Postfix) with ESMTP id D40E12166B29; Wed, 16 Nov 2022 12:14:54 +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: <88b441af-d6ae-4d46-aae5-0b649e76031d@samba.org> References: <88b441af-d6ae-4d46-aae5-0b649e76031d@samba.org> <3609b064-175c-fc18-cd1a-e177d0349c58@samba.org> <166855224228.1998592.2212551359609792175.stgit@warthog.procyon.org.uk> <2147870.1668582019@warthog.procyon.org.uk> To: Stefan Metzmacher Cc: dhowells@redhat.com, smfrench@gmail.com, tom@talpey.com, Long Li , Namjae Jeon , linux-cifs@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] cifs: Fix problem with encrypted RDMA data read MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2780585.1668600891.1@warthog.procyon.org.uk> Content-Transfer-Encoding: quoted-printable Date: Wed, 16 Nov 2022 12:14:51 +0000 Message-ID: <2780586.1668600891@warthog.procyon.org.uk> X-Scanned-By: MIMEDefang 3.1 on 10.11.54.6 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_H2,SPF_HELO_NONE,SPF_NONE 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 Stefan Metzmacher wrote: > > Stefan Metzmacher wrote: > > = > >> I'm not sure I understand why this would fix anything when encryption= is > >> enabled. > >> > >> Is the payload still be offloaded as plaintext? Otherwise we wouldn't= have > >> use_rdma_mr... So this rather looks like a fix for the non encrypted= case. > > The "inline"[*] PDUs are encrypted, but the direct RDMA data transmiss= ion is > > not. I'm not sure if this is a bug in ksmbd. > = > It's a bug in the client! Well, if you can fix it the right way, I can test the patch. I'm not sure what that would be if not what I suggested. David