bpf: Sockmap/tls, msg_push_data may leave end mark in place
authorJohn Fastabend <john.fastabend@gmail.com>
Sat, 11 Jan 2020 06:12:03 +0000 (06:12 +0000)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Thu, 23 Jan 2020 07:22:45 +0000 (08:22 +0100)
commit9ae0793f8fe491d7afcf3993d69281f04dc4c1f2
tree380541264b5083cc557e537ed522f6ff4798da9e
parentb332bffe9ac55272b22c6f286252e6b7b25149b3
bpf: Sockmap/tls, msg_push_data may leave end mark in place

commit cf21e9ba1eb86c9333ca5b05b2f1cc94021bcaef upstream.

Leaving an incorrect end mark in place when passing to crypto
layer will cause crypto layer to stop processing data before
all data is encrypted. To fix clear the end mark on push
data instead of expecting users of the helper to clear the
mark value after the fact.

This happens when we push data into the middle of a skmsg and
have room for it so we don't do a set of copies that already
clear the end flag.

Fixes: 6fff607e2f14b ("bpf: sk_msg program helper bpf_msg_push_data")
Signed-off-by: John Fastabend <john.fastabend@gmail.com>
Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
Acked-by: Song Liu <songliubraving@fb.com>
Cc: stable@vger.kernel.org
Link: https://lore.kernel.org/bpf/20200111061206.8028-6-john.fastabend@gmail.com
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
net/core/filter.c