diff options
author | John Fastabend <john.fastabend@gmail.com> | 2023-05-22 19:56:11 -0700 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2023-06-05 09:29:42 +0200 |
commit | d3cbd7c571446a876aefd8320500300b2c951c58 (patch) | |
tree | 264a0fbe34b97e2ca5411306c3cb6acf04d454a1 /include | |
parent | 8818b2229a15d16d9f8844e0ed51ea283d612b78 (diff) | |
download | linux-stable-d3cbd7c571446a876aefd8320500300b2c951c58.tar.gz linux-stable-d3cbd7c571446a876aefd8320500300b2c951c58.tar.bz2 linux-stable-d3cbd7c571446a876aefd8320500300b2c951c58.zip |
bpf, sockmap: Wake up polling after data copy
[ Upstream commit 6df7f764cd3cf5a03a4a47b23be47e57e41fcd85 ]
When TCP stack has data ready to read sk_data_ready() is called. Sockmap
overwrites this with its own handler to call into BPF verdict program.
But, the original TCP socket had sock_def_readable that would additionally
wake up any user space waiters with sk_wake_async().
Sockmap saved the callback when the socket was created so call the saved
data ready callback and then we can wake up any epoll() logic waiting
on the read.
Note we call on 'copied >= 0' to account for returning 0 when a FIN is
received because we need to wake up user for this as well so they
can do the recvmsg() -> 0 and detect the shutdown.
Fixes: 04919bed948dc ("tcp: Introduce tcp_read_skb()")
Signed-off-by: John Fastabend <john.fastabend@gmail.com>
Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
Reviewed-by: Jakub Sitnicki <jakub@cloudflare.com>
Link: https://lore.kernel.org/bpf/20230523025618.113937-8-john.fastabend@gmail.com
Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions