From: Sabrina Dubroca <sd@queasysnail.net>
To: Atul Gupta <atul.gupta@chelsio.com>
Cc: davejwatson@fb.com, davem@davemloft.net,
herbert@gondor.apana.org.au, linux-crypto@vger.kernel.org,
netdev@vger.kernel.org, ganeshgr@chelsio.com
Subject: Re: [PATCH v9 crypto 01/12] tls: tls_device struct to register TLS drivers
Date: Wed, 7 Mar 2018 11:16:25 +0100 [thread overview]
Message-ID: <20180307101625.GA20949@bistromath.localdomain> (raw)
In-Reply-To: <1520350580-11796-1-git-send-email-atul.gupta@chelsio.com>
Hello Atul,
One quick note before you start replying: please fix your email
client, as you've been told before. Quoting has to add a quoting
marker (the '>' character) at the beginning of the line, otherwise
it's impossible to separate your reply from the email you're quoting.
2018-03-06, 21:06:20 +0530, Atul Gupta wrote:
> tls_device structure to register Inline TLS drivers
> with net/tls
>
> Signed-off-by: Atul Gupta <atul.gupta@chelsio.com>
> ---
> include/net/tls.h | 26 ++++++++++++++++++++++++++
> 1 file changed, 26 insertions(+)
>
> diff --git a/include/net/tls.h b/include/net/tls.h
> index 4913430..9bfb91f 100644
> --- a/include/net/tls.h
> +++ b/include/net/tls.h
> @@ -55,6 +55,28 @@
> #define TLS_RECORD_TYPE_DATA 0x17
>
> #define TLS_AAD_SPACE_SIZE 13
> +#define TLS_DEVICE_NAME_MAX 32
Why 32 characters?
> +enum {
> + TLS_BASE_TX,
> + TLS_SW_TX,
> + TLS_FULL_HW, /* TLS record processed Inline */
> + TLS_NUM_CONFIG,
> +};
> +
> +extern struct proto tls_prots[TLS_NUM_CONFIG];
Don't break bisection. The code has to compile after every
patch. These are already defined in net/tls/tls_main.c.
> +struct tls_device {
> + char name[TLS_DEVICE_NAME_MAX];
I could find only one use of it, in chtls_register_dev. Is this
actually needed?
> + struct list_head dev_list;
> +
> + /* netdev present in registered inline tls driver */
> + int (*netdev)(struct tls_device *device,
> + struct net_device *netdev);
I was trying to figure out what this did, because the name is really
not explicit, and the comment doesn't make sense, but noticed it's
never actually called.
> + int (*feature)(struct tls_device *device);
> + int (*hash)(struct tls_device *device, struct sock *sk);
> + void (*unhash)(struct tls_device *device, struct sock *sk);
I think you should add a kerneldoc comment, like all the ndo_*
methods have.
> +};
>
> struct tls_sw_context {
> struct crypto_aead *aead_send;
> @@ -115,6 +137,8 @@ struct tls_context {
> int (*getsockopt)(struct sock *sk, int level,
> int optname, char __user *optval,
> int __user *optlen);
> + int (*hash)(struct sock *sk);
> + void (*unhash)(struct sock *sk);
> };
>
> int wait_on_pending_writer(struct sock *sk, long *timeo);
> @@ -256,5 +280,7 @@ static inline struct tls_offload_context *tls_offload_ctx(
>
> int tls_proccess_cmsg(struct sock *sk, struct msghdr *msg,
> unsigned char *record_type);
> +void tls_register_device(struct tls_device *device);
> +void tls_unregister_device(struct tls_device *device);
Prototype without implementation, please don't do that. This happens
because you split your patchset so that each patch has all the changes
for exactly one file.
--
Sabrina
next prev parent reply other threads:[~2018-03-07 10:16 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-06 15:35 [PATCH v9 crypto 00/12] Chelsio Inline TLS Atul Gupta
2018-03-06 15:36 ` [PATCH v9 crypto 01/12] tls: tls_device struct to register TLS drivers Atul Gupta
2018-03-07 10:16 ` Sabrina Dubroca [this message]
2018-03-07 11:21 ` Atul Gupta
2018-03-06 15:37 ` [PATCH v9 crypto 02/12] ethtool: enable Inline TLS in HW Atul Gupta
2018-03-07 12:35 ` Sabrina Dubroca
2018-03-07 12:44 ` Atul Gupta
2018-03-06 15:38 ` [PATCH v9 crypto 00/12] Chelsio Inline TLS Vakul Garg
2018-03-06 15:45 ` Atul Gupta
2018-03-07 10:23 ` Sabrina Dubroca
2018-03-07 11:26 ` Atul Gupta
-- strict thread matches above, loose matches on Subject: below --
2018-03-06 15:39 [PATCH v9 crypto 04/12] chtls: structure and macro definiton Atul Gupta
2018-03-06 15:39 ` [PATCH v9 crypto 05/12] cxgb4: Inline TLS FW Interface Atul Gupta
2018-03-06 15:39 ` [PATCH v9 crypto 06/12] cxgb4: LLD driver changes to enable TLS Atul Gupta
2018-03-07 12:59 ` Sabrina Dubroca
2018-03-08 8:58 ` Atul Gupta
2018-03-06 15:39 ` [PATCH v9 crypto 07/12] chcr: Key Macro Atul Gupta
2018-03-06 15:39 ` [PATCH v9 crypto 08/12] chtls: Key program Atul Gupta
2018-03-07 15:05 ` Sabrina Dubroca
2018-03-08 11:18 ` Atul Gupta
2018-03-06 15:39 ` [PATCH v9 crypto 09/12] chtls: CPL handler definition Atul Gupta
2018-03-06 15:39 ` [PATCH v9 crypto 10/12] chtls: Inline crypto request Tx/Rx Atul Gupta
2018-03-06 15:39 ` [PATCH v9 crypto 11/12] chtls: Register chtls Inline TLS with net tls Atul Gupta
2018-03-06 15:39 ` [PATCH v9 crypto 12/12] Makefile Kconfig Atul Gupta
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180307101625.GA20949@bistromath.localdomain \
--to=sd@queasysnail.net \
--cc=atul.gupta@chelsio.com \
--cc=davejwatson@fb.com \
--cc=davem@davemloft.net \
--cc=ganeshgr@chelsio.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).