Received: by 2002:a05:6602:2086:0:0:0:0 with SMTP id a6csp4449324ioa; Wed, 27 Apr 2022 04:14:37 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwghxE42vFhLpumBQXxemzlhi9WE9p8N8MhdVdm7YEgb9C15SCY88eZpisRHMd83OI8YCD/ X-Received: by 2002:a63:b40a:0:b0:35e:d274:5f54 with SMTP id s10-20020a63b40a000000b0035ed2745f54mr22906914pgf.200.1651058077146; Wed, 27 Apr 2022 04:14:37 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1651058077; cv=none; d=google.com; s=arc-20160816; b=TLXNvTWKz602cOyZ66fsGQPunHk72oJFj5N5+rR1AWDyRBhk5r2EAmaZz0XEQs9mZj qESL7o2hvPVDf6X5ERN5B18ECzoU1DdWUD1Ue5AQP6q38dR8jBybgOXszNUSrAG5Zvke Gbo2oQbaD721cJckUjfq21LktQzoR/W7oTSWoTXTkF0KIG1v52n4s5jUYGBhZtjSm8FY zw7PXe/1tDoE1k7EJyZEg2719l5BxLW9ipF4XkWW3lJzmHZufa1eDGkBbfMFYbLJNxt3 G17qD81kY+kB3TuFU6/GX8qAxdgi6HmJX1J43mh6kOfAf2fTaua8At75QS6f/Z21KqFa N/6Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:subject:cc:to:from:date :dkim-signature; bh=3c6A+trUSQjUgo5tCyMKw7QZNtfISA5VnZsFVftfyAQ=; b=X7U0g8j2HKGq3CYJQo0GGjWyEqPiWs3VA6W+vKVBj70rbFLznBdrM/7h3YkaJ6GdHN YKoLUmGCIbDdVjy2bwyZX2tJNR+VHHE+W7zmlnjBV43lib7YOlmdOIw/tNoHlxcVmQ93 7a//dfR8tEzqHmfZFdbZjbxYAZkKEVE2LB0h3+z0HBCS4ccYIoPTp1ndKUopcyNFz+83 +LzfmeGXb20G77pB46B6Zro4H5pP4p7Ycy8jt3O8gIGaKCMSE8710ZIWF96geonvOsQE xgjMiWALSgb6yuBJmIKbklWgL8Sw/JsFF5Dv6whHDYOEGMeEaWD3Q88H5eRyEs91AVVy 5/FA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=Fq9hilMC; spf=softfail (google.com: domain of transitioning linux-nfs-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) smtp.mailfrom=linux-nfs-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from lindbergh.monkeyblade.net (lindbergh.monkeyblade.net. [23.128.96.19]) by mx.google.com with ESMTPS id n9-20020a170903110900b00158e03cfca2si1492501plh.255.2022.04.27.04.14.36 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 27 Apr 2022 04:14:37 -0700 (PDT) Received-SPF: softfail (google.com: domain of transitioning linux-nfs-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) client-ip=23.128.96.19; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=Fq9hilMC; spf=softfail (google.com: domain of transitioning linux-nfs-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) smtp.mailfrom=linux-nfs-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id B9048257465; Wed, 27 Apr 2022 03:08:29 -0700 (PDT) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1351793AbiDZO6N (ORCPT + 99 others); Tue, 26 Apr 2022 10:58:13 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56658 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1351791AbiDZO6L (ORCPT ); Tue, 26 Apr 2022 10:58:11 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id DF38E1409E; Tue, 26 Apr 2022 07:55:02 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 78F0A614ED; Tue, 26 Apr 2022 14:55:02 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 79D7BC385AA; Tue, 26 Apr 2022 14:55:01 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1650984901; bh=me9iCcOuTJq+2PqZc4Jh4npbdVCsacbBRf9z6+gdqqk=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=Fq9hilMCAJ9Rwa8FPT5daWcr97ssuASl+lSc8iGSkdyweVTInpfT9bvtS2m6xq7PW TC8nluVb3QnvFByfp4Ei8BJqnJSBrKDSETcw6YDJ/CKnRVkYlh0RZJ9kGxojrzN4Rz fkrMJd5qGeG/yU3l7kmqOHAMSnlGCKcwsXGm1Mj4eRXiiQp5yfQOXWphT95sbPJ86e KZNRiIZsBq+RgD5cpH6RL3HE85LRrRKAkdsrw5yUuNJ20N9e2EREBy4VjA4LyTNdJA /vpiDNG8S4KLXVAb29UdlnQ3wUurVw+vPZ+0z+xj7P5OBB+HEGSMgcoLrZlf4oPey3 KMCPwev+alVJg== Date: Tue, 26 Apr 2022 07:55:00 -0700 From: Jakub Kicinski To: Hannes Reinecke Cc: Chuck Lever , netdev@vger.kernel.org, linux-nfs@vger.kernel.org, linux-nvme@lists.infradead.org, linux-cifs@vger.kernel.org, linux-fsdevel@vger.kernel.org, ak@tempesta-tech.com, borisp@nvidia.com, simo@redhat.com Subject: Re: [PATCH RFC 4/5] net/tls: Add support for PF_TLSH (a TLS handshake listener) Message-ID: <20220426075500.34776cd5@kernel.org> In-Reply-To: <66077b73-c1a4-d2ae-c8e4-3e19e9053171@suse.de> References: <165030051838.5073.8699008789153780301.stgit@oracle-102.nfsv4.dev> <165030059051.5073.16723746870370826608.stgit@oracle-102.nfsv4.dev> <20220425101459.15484d17@kernel.org> <66077b73-c1a4-d2ae-c8e4-3e19e9053171@suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.9 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,MAILING_LIST_MULTI, RDNS_NONE,SPF_HELO_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-nfs@vger.kernel.org On Tue, 26 Apr 2022 11:43:37 +0200 Hannes Reinecke wrote: > > Create the socket in user space, do all the handshakes you need there > > and then pass it to the kernel. This is how NBD + TLS works. Scales > > better and requires much less kernel code. > > > But we can't, as the existing mechanisms (at least for NVMe) creates the > socket in-kernel. > Having to create the socket in userspace would require a completely new > interface for nvme and will not be backwards compatible. > Not to mention having to rework the nvme driver to accept sockets from > userspace instead of creating them internally. > > With this approach we can keep existing infrastructure, and can get a > common implementation for either transport. You add 1.5kLoC and require running a user space agent, surely you're adding new interfaces and are not backward-compatible already. I don't understand your argument, maybe you could rephrase / dumb it down for me?