From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.9 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 84773C43381 for ; Sun, 24 Feb 2019 06:05:13 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 45AA620663 for ; Sun, 24 Feb 2019 06:05:13 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="bGOLSiA2" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726188AbfBXF76 (ORCPT ); Sun, 24 Feb 2019 00:59:58 -0500 Received: from mail-pg1-f196.google.com ([209.85.215.196]:39952 "EHLO mail-pg1-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725928AbfBXF75 (ORCPT ); Sun, 24 Feb 2019 00:59:57 -0500 Received: by mail-pg1-f196.google.com with SMTP id u9so2986474pgo.7 for ; Sat, 23 Feb 2019 21:59:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=pYd1NOJb6pdiyq9s1DCw1YBhYv8VwkckCStnYgps/1w=; b=bGOLSiA2q4ionAxtT3aYMtjjOsWf/gq8+VsVKJCcwzLcKYH3xydKdBuv5UzycjfpqS kezBoMVU6yy3vU5cNv6fmpFXEDlNh0+oFfEvNuOv2HJeQNb/lwKV0L64wgZ0jmwBPAFB /zJO41nJ19xfAKQ/nqM2tIjCjPBlUTuapY/5e1p4CHmRyzikplX7m4+nbFHpxDKPQYNJ anrLKv/ooYGZBYcs31uKOkBaCaxFSknsminSXIAm+Upqd7ILsWKDQ5burTnyOzJ48teS Gh3ZH7ZQIrFuL0vZm8M+U3EDkJJ0826qOjyyiDxYPkyfuidnbNIiTiXgbEoKGjPMeaFs DoKA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=pYd1NOJb6pdiyq9s1DCw1YBhYv8VwkckCStnYgps/1w=; b=tDdOLUPrYAZ6P0RSTFqQuJLzHq07OzV/a9s5PEm30N2XE7yMRLi5Kxrw8NlmuOAQK/ 6TFClgAG2hoYrTb3FkLAhK1XpvZHmAcjADTXiLER4UxMkLxiLR19QbfOU0c328gybA3Z 6iq+qqDT0sH2pqvDZmdSaTHlS5ZynYBpecwmdc6aHd71I48hX5MvbPa1xK6XDWYMjASj 11M+LYQmMAxBfn9P1mNxtMQMbjI0NXySQBl1rfh2CAt2p5AIPY1OO53Q5NOpxT8BwsFb 0k1lEXc0nZEAMk87xpeIEvoXZUn/aqJmxNqkhkLzrj8VNXczHmuBfIELzVN25WY4Xkt3 1yNw== X-Gm-Message-State: AHQUAuae3sUT32XXew+h3/OfC2bXTN1Us6uzhcaEw/G87eZEFpTEfrwP WmWiTwW9MNSpyQw8VsqPtKN2owG0 X-Google-Smtp-Source: AHgI3IYbsMvSknkktr7X77DcXPEcCP2VURTqZI+gblpdncYlZ3C4uSsMs2/YNlcqqYhmbWgrT8oaHA== X-Received: by 2002:a63:ed0b:: with SMTP id d11mr11705210pgi.435.1550987996764; Sat, 23 Feb 2019 21:59:56 -0800 (PST) Received: from ?IPv6:240d:1a:84a:4000:4183:63ac:dbc7:944? ([240d:1a:84a:4000:4183:63ac:dbc7:944]) by smtp.gmail.com with ESMTPSA id y22sm6550733pfn.136.2019.02.23.21.59.55 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 23 Feb 2019 21:59:56 -0800 (PST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 12.1 \(3445.101.1\)) Subject: Re: kTLS getsockopt TLS_RX support From: Hayakawa Yutaro In-Reply-To: Date: Sun, 24 Feb 2019 14:59:52 +0900 Cc: "netdev@vger.kernel.org" Content-Transfer-Encoding: quoted-printable Message-Id: <52896DE7-B684-4F2E-AD45-DF34126C841B@gmail.com> References: <7889DA1D-7671-4012-81E4-FB626F06B20F@gmail.com> <8989A671-47DB-4910-AFE8-8A6E6E30A827@gmail.com> To: Vakul Garg X-Mailer: Apple Mail (2.3445.101.1) Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org > 2019/02/24 14:33=E3=80=81Vakul Garg =E3=81=AE=E3=83=A1= =E3=83=BC=E3=83=AB: >=20 >=20 >=20 >> -----Original Message----- >> From: Hayakawa Yutaro >> Sent: Sunday, February 24, 2019 11:01 AM >> To: Vakul Garg >> Cc: netdev@vger.kernel.org >> Subject: Re: kTLS getsockopt TLS_RX support >>=20 >>=20 >>> 2019/02/24 10:50=E3=80=81Vakul Garg = =E3=81=AE=E3=83=A1=E3=83=BC=E3=83=AB: >>>=20 >>>=20 >>>=20 >>>> -----Original Message----- >>>> From: netdev-owner@vger.kernel.org >> On >>>> Behalf Of Hayakawa Yutaro >>>> Sent: Saturday, February 23, 2019 10:59 PM >>>> To: netdev@vger.kernel.org >>>> Subject: kTLS getsockopt TLS_RX support >>>>=20 >>>> Hello, >>>>=20 >>>> While trying the kTLS, I found out that currently, there is no >>>> support for kTLS getsockopt TLS_RX which extracts receive side = crypto >>>> information from kTLS socket. Since setting crypto information for = RX >>>> side is supported, I felt wonder why it is not supported. >>>>=20 >>>> Is there any particular reason for it? >>>=20 >>> What use case do you have in mind? >>> Why give back state of record layer which also contains (record = sequence >> number) to user space? >>=20 >> I=E2=80=99d like to checkpoint/restore the TLS session in conjunction = with >> TCP_REPAIR. >>=20 >> When we checkpoint the kTLS session, we need to pick the record = sequence >> number or any other session information from kernel. For TX side, it = is >> already supported (getsockopt TLS_TX), so I=E2=80=99m wondering why = RX side is >> missing. >>=20 >> Is there any technical difficulty or it will never supported in = future? >=20 > Don't think so.=20 > Will you submit a patch? Since I am one of the beginner user of kTLS, I don=E2=80=99t have much = knowledge about the internal, but I have my own patch. I can test and submit it to here. Yutaro >=20 >> Regards, >> Yutaro >>=20 >>>=20 >>>>=20 >>>> Regards, >>>> Yutaro