From: Jakub Sitnicki <jakub@cloudflare.com>
To: Pengcheng Yang <yangpc@wangsu.com>
Cc: John Fastabend <john.fastabend@gmail.com>,
bpf@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH bpf 0/4] bpf, sockmap: Fix some issues with using apply_bytes
Date: Mon, 21 Nov 2022 10:35:34 +0100 [thread overview]
Message-ID: <87k03o7ipx.fsf@cloudflare.com> (raw)
In-Reply-To: <1668598161-15455-1-git-send-email-yangpc@wangsu.com>
On Wed, Nov 16, 2022 at 07:29 PM +08, Pengcheng Yang wrote:
> Patch 0001~0003 fixes three issues with using apply_bytes when redirecting.
> Patch 0004 adds ingress tests for txmsg with apply_bytes in selftests.
>
> Pengcheng Yang (4):
> bpf, sockmap: Fix repeated calls to sock_put() when msg has more_data
> bpf, sockmap: Fix missing BPF_F_INGRESS flag when using apply_bytes
> bpf, sockmap: Fix data loss caused by using apply_bytes on ingress
> redirect
> selftests/bpf: Add ingress tests for txmsg with apply_bytes
>
> include/linux/skmsg.h | 1 +
> net/core/skmsg.c | 1 +
> net/ipv4/tcp_bpf.c | 9 +++++++--
> net/tls/tls_sw.c | 1 +
> tools/testing/selftests/bpf/test_sockmap.c | 18 ++++++++++++++++++
> 5 files changed, 28 insertions(+), 2 deletions(-)
Thanks for the patches. I need a bit more time to review them.
next prev parent reply other threads:[~2022-11-21 9:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 11:29 [PATCH bpf 0/4] bpf, sockmap: Fix some issues with using apply_bytes Pengcheng Yang
2022-11-16 11:29 ` [PATCH bpf 2/4] bpf, sockmap: Fix missing BPF_F_INGRESS flag when " Pengcheng Yang
2022-11-16 11:29 ` [PATCH bpf 4/4] selftests/bpf: Add ingress tests for txmsg with apply_bytes Pengcheng Yang
2022-11-21 9:35 ` Jakub Sitnicki [this message]
2022-11-21 16:38 ` [PATCH bpf 0/4] bpf, sockmap: Fix some issues with using apply_bytes Daniel Borkmann
[not found] ` <1668598161-15455-2-git-send-email-yangpc@wangsu.com>
2022-11-22 2:16 ` [PATCH bpf 1/4] bpf, sockmap: Fix repeated calls to sock_put() when msg has more_data 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=87k03o7ipx.fsf@cloudflare.com \
--to=jakub@cloudflare.com \
--cc=bpf@vger.kernel.org \
--cc=john.fastabend@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=yangpc@wangsu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.