Linux cryptographic layer development
 help / color / mirror / Atom feed
From: Jakub Kicinski <jakub.kicinski@netronome.com>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, oss-drivers@netronome.com,
	borisp@mellanox.com, aviadye@mellanox.com,
	john.fastabend@gmail.com, daniel@iogearbox.net,
	syzbot+f8495bff23a879a6d0bd@syzkaller.appspotmail.com,
	syzbot+6f50c99e8f6194bf363f@syzkaller.appspotmail.com,
	Eric Biggers <ebiggers@kernel.org>,
	herbert@gondor.apana.org.au, glider@google.com,
	linux-crypto@vger.kernel.org
Subject: Re: [PATCH net] net/tls: fix sk_msg trim on fallback to copy mode
Date: Thu, 31 Oct 2019 14:16:44 -0700	[thread overview]
Message-ID: <20191031141644.232af7ed@cakuba.netronome.com> (raw)
In-Reply-To: <20191030160542.30295-1-jakub.kicinski@netronome.com>

On Wed, 30 Oct 2019 09:05:42 -0700, Jakub Kicinski wrote:
> sk_msg_trim() tries to only update curr pointer if it falls into
> the trimmed region. The logic, however, does not take into the
> account pointer wrapping that sk_msg_iter_var_prev() does.
> This means that when the message was trimmed completely, the new
> curr pointer would have the value of MAX_MSG_FRAGS - 1, which is
> neither smaller than any other value, nor would it actually be
> correct.
> 
> Special case the trimming to 0 length a little bit.
> 
> This bug caused the TLS code to not copy all of the message, if
> zero copy filled in fewer sg entries than memcopy would need.
> 
> Big thanks to Alexander Potapenko for the non-KMSAN reproducer.
> 
> Fixes: d829e9c4112b ("tls: convert to generic sk_msg interface")
> Reported-by: syzbot+f8495bff23a879a6d0bd@syzkaller.appspotmail.com
> Reported-by: syzbot+6f50c99e8f6194bf363f@syzkaller.appspotmail.com
> Signed-off-by: Jakub Kicinski <jakub.kicinski@netronome.com>
> ---
> Daniel, John, does this look okay?
> 
> CC: Eric Biggers <ebiggers@kernel.org>
> CC: herbert@gondor.apana.org.au
> CC: glider@google.com
> CC: linux-crypto@vger.kernel.org
> 
>  net/core/skmsg.c | 5 ++++-
>  1 file changed, 4 insertions(+), 1 deletion(-)

Daniel, John does this patch look reasonable? I must admit 
the skmsg stuff in TLS scares me, it'd appreciate an ack.

  reply	other threads:[~2019-10-31 21:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-30 16:05 [PATCH net] net/tls: fix sk_msg trim on fallback to copy mode Jakub Kicinski
2019-10-31 21:16 ` Jakub Kicinski [this message]
2019-10-31 22:05 ` John Fastabend
2019-10-31 22:08   ` John Fastabend
2019-10-31 22:24   ` Jakub Kicinski
2019-11-01  1:41     ` Jakub Kicinski
2019-11-01  4:44     ` John Fastabend
2019-11-01  4:54       ` Jakub Kicinski
2019-11-01 15:01         ` John Fastabend
2019-11-01 17:22           ` [oss-drivers] " Jakub Kicinski
2019-11-01 19:51             ` Jakub Kicinski
2019-11-04 18:56               ` John Fastabend
2019-11-04 19:34                 ` Jakub Kicinski
2019-11-04 22:58                   ` John Fastabend

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=20191031141644.232af7ed@cakuba.netronome.com \
    --to=jakub.kicinski@netronome.com \
    --cc=aviadye@mellanox.com \
    --cc=borisp@mellanox.com \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=ebiggers@kernel.org \
    --cc=glider@google.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=john.fastabend@gmail.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=oss-drivers@netronome.com \
    --cc=syzbot+6f50c99e8f6194bf363f@syzkaller.appspotmail.com \
    --cc=syzbot+f8495bff23a879a6d0bd@syzkaller.appspotmail.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