Netdev List
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: vakul.garg@nxp.com
Cc: netdev@vger.kernel.org, borisp@mellanox.com,
	aviadye@mellanox.com, davejwatson@fb.com
Subject: Re: [net-next v2 1/5] net/tls: Do not enable zero-copy prematurely
Date: Thu, 19 Jul 2018 05:23:25 +0900 (KST)	[thread overview]
Message-ID: <20180719.052325.900558008055928374.davem@davemloft.net> (raw)
In-Reply-To: <20180716155715.13987-1-vakul.garg@nxp.com>

From: Vakul Garg <vakul.garg@nxp.com>
Date: Mon, 16 Jul 2018 21:27:11 +0530

> Zero-copy mode was left enabled even when zerocopy_from_iter() failed.
> Set the zero-copy mode only when zerocopy_from_iter() succeeds. This
> leads to removal of argument 'zc' of function decrypt_skb_update().
> Function decrypt_skb_update() does not need to check whether
> ctx->decrypted is set since it is never called if ctx->decrypted is
> true.
> 
> Signed-off-by: Vakul Garg <vakul.garg@nxp.com>

This adds a warning:

net/tls/tls_sw.c: In function ‘decrypt_skb_update’:
net/tls/tls_sw.c:662:28: warning: unused variable ‘ctx’ [-Wunused-variable]
  struct tls_sw_context_rx *ctx = tls_sw_ctx_rx(tls_ctx);

Also, you must submit a patch series with a proper cover letter
"[net-next vX 0/N] net/tls: ..." explaining what the patch series
is doing, how it is doing it, and why it doing it that way.

You should also provide appropriate "Fixes: " tags to your
patches.

Thank you.

      parent reply	other threads:[~2018-07-18 21:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-16 15:57 [net-next v2 1/5] net/tls: Do not enable zero-copy prematurely Vakul Garg
2018-07-16 15:57 ` [net-next v2 2/5] net/tls: Use socket data_ready callback on record availability Vakul Garg
2018-07-16 15:57 ` [net-next v2 3/5] net/tls: Remove redundant variable assignments and wakeup Vakul Garg
2018-07-16 15:57 ` [net-next v2 4/5] net/tls: Remove redundant array allocation Vakul Garg
2018-07-16 15:57 ` [net-next v2 5/5] net/tls: Rework error checking after decrypt_skb_update() Vakul Garg
2018-07-18 20:23 ` David Miller [this message]

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=20180719.052325.900558008055928374.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=aviadye@mellanox.com \
    --cc=borisp@mellanox.com \
    --cc=davejwatson@fb.com \
    --cc=netdev@vger.kernel.org \
    --cc=vakul.garg@nxp.com \
    /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