From: Jakub Kicinski <kuba@kernel•org>
To: Jiayuan Chen <mrpre@163•com>
Cc: bpf@vger•kernel.org, jakub@cloudflare•com,
john.fastabend@gmail•com, netdev@vger•kernel.org,
martin.lau@linux•dev, ast@kernel•org, edumazet@google•com,
davem@davemloft•net, dsahern@kernel•org, pabeni@redhat•com,
linux-kernel@vger•kernel.org, song@kernel•org, andrii@kernel•org,
mhal@rbox•co, yonghong.song@linux•dev, daniel@iogearbox•net,
xiyou.wangcong@gmail•com, horms@kernel•org, corbet@lwn•net,
eddyz87@gmail•com, cong.wang@bytedance•com, shuah@kernel•org,
mykolal@fb•com, jolsa@kernel•org, haoluo@google•com,
sdf@fomichev•me, kpsingh@kernel•org, linux-doc@vger•kernel.org
Subject: Re: [PATCH bpf v5 1/3] bpf: fix wrong copied_seq calculation
Date: Mon, 13 Jan 2025 16:04:04 -0800 [thread overview]
Message-ID: <20250113160404.7ab0927d@kernel.org> (raw)
In-Reply-To: <20250109094402.50838-2-mrpre@163.com>
On Thu, 9 Jan 2025 17:43:59 +0800 Jiayuan Chen wrote:
> However, for programs where both stream_parser and stream_verdict are
> active(strparser purpose), tcp_read_sock() was used instead of
> tcp_read_skb() (sk_data_ready->strp_data_ready->tcp_read_sock)
> tcp_read_sock() now still update 'sk->copied_seq', leading to duplicated
> updates.
To state the obvious feels like the abstraction between TCP and psock
has broken down pretty severely at this stage. You're modifying TCP
and straight up calling TCP functions from skmsg.c :(
> +int tcp_read_sock_noack(struct sock *sk, read_descriptor_t *desc,
> + sk_read_actor_t recv_actor, u32 noack,
> + u32 *copied_seq)
> +{
> + return __tcp_read_sock(sk, desc, recv_actor,
> + noack, copied_seq);
> +}
> +EXPORT_SYMBOL(tcp_read_sock_noack);
Pretty sure you don't have to export this. skmsg can't be a module.
next prev parent reply other threads:[~2025-01-14 0:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-09 9:43 [PATCH bpf v5 0/3] bpf: fix wrong copied_seq calculation and add tests Jiayuan Chen
2025-01-09 9:43 ` [PATCH bpf v5 1/3] bpf: fix wrong copied_seq calculation Jiayuan Chen
2025-01-14 0:04 ` Jakub Kicinski [this message]
2025-01-14 6:35 ` Jiayuan Chen
2025-01-14 18:01 ` Jakub Kicinski
2025-01-14 11:27 ` Jakub Sitnicki
2025-01-09 9:44 ` [PATCH bpf v5 2/3] selftests/bpf: add strparser test for bpf Jiayuan Chen
2025-01-09 9:44 ` [PATCH bpf v5 3/3] bpf, strparser, docs: Add new callback " Jiayuan Chen
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=20250113160404.7ab0927d@kernel.org \
--to=kuba@kernel$(echo .)org \
--cc=andrii@kernel$(echo .)org \
--cc=ast@kernel$(echo .)org \
--cc=bpf@vger$(echo .)kernel.org \
--cc=cong.wang@bytedance$(echo .)com \
--cc=corbet@lwn$(echo .)net \
--cc=daniel@iogearbox$(echo .)net \
--cc=davem@davemloft$(echo .)net \
--cc=dsahern@kernel$(echo .)org \
--cc=eddyz87@gmail$(echo .)com \
--cc=edumazet@google$(echo .)com \
--cc=haoluo@google$(echo .)com \
--cc=horms@kernel$(echo .)org \
--cc=jakub@cloudflare$(echo .)com \
--cc=john.fastabend@gmail$(echo .)com \
--cc=jolsa@kernel$(echo .)org \
--cc=kpsingh@kernel$(echo .)org \
--cc=linux-doc@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=martin.lau@linux$(echo .)dev \
--cc=mhal@rbox$(echo .)co \
--cc=mrpre@163$(echo .)com \
--cc=mykolal@fb$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=sdf@fomichev$(echo .)me \
--cc=shuah@kernel$(echo .)org \
--cc=song@kernel$(echo .)org \
--cc=xiyou.wangcong@gmail$(echo .)com \
--cc=yonghong.song@linux$(echo .)dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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