From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: davem@davemloft.net, kuba@kernel.org, ast@kernel.org,
daniel@iogearbox.net, john.fastabend@gmail.com,
netdev@vger.kernel.org, bpf@vger.kernel.org,
jakub@cloudflare.com, andrii@kernel.org, kafai@fb.com,
songliubraving@fb.com, yhs@fb.com, kpsingh@kernel.org,
edumazet@google.com, ncardwell@google.com,
syzkaller@googlegroups.com
Subject: Re: [PATCH net 1/2] bpf, sockmap: Do not ignore orig_len parameter
Date: Thu, 03 Mar 2022 07:00:10 +0000 [thread overview]
Message-ID: <164629081042.23910.10991604475899860456.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220302161723.3910001-1-eric.dumazet@gmail.com>
Hello:
This series was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 2 Mar 2022 08:17:22 -0800 you wrote:
> From: Eric Dumazet <edumazet@google.com>
>
> Currently, sk_psock_verdict_recv() returns skb->len
>
> This is problematic because tcp_read_sock() might have
> passed orig_len < skb->len, due to the presence of TCP urgent data.
>
> [...]
Here is the summary with links:
- [net,1/2] bpf, sockmap: Do not ignore orig_len parameter
https://git.kernel.org/netdev/net/c/60ce37b03917
- [net,2/2] tcp: make tcp_read_sock() more robust
https://git.kernel.org/netdev/net/c/e3d5ea2c011e
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-03-03 7:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-02 16:17 [PATCH net 1/2] bpf, sockmap: Do not ignore orig_len parameter Eric Dumazet
2022-03-02 16:17 ` [PATCH net 2/2] tcp: make tcp_read_sock() more robust Eric Dumazet
2022-03-03 7:00 ` patchwork-bot+netdevbpf [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=164629081042.23910.10991604475899860456.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=jakub@cloudflare.com \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=syzkaller@googlegroups.com \
--cc=yhs@fb.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.