From: gang.yan@linux.dev
To: "Jiayuan Chen" <jiayuan.chen@linux.dev>,
"Geliang Tang" <geliang@kernel.org>,
"John Fastabend" <john.fastabend@gmail.com>,
"Jakub Sitnicki" <jakub@cloudflare.com>,
"Eric Dumazet" <edumazet@google.com>,
"Neal Cardwell" <ncardwell@google.com>,
"Kuniyuki Iwashima" <kuniyu@google.com>,
"David S. Miller" <davem@davemloft.net>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
"Simon Horman" <horms@kernel.org>,
"Sabrina Dubroca" <sd@queasysnail.net>,
"David Howells" <dhowells@redhat.com>,
"Matthieu Baerts" <matttbe@kernel.org>,
"Mat Martineau" <martineau@kernel.org>
Cc: "Geliang Tang" <tanggeliang@kylinos.cn>,
netdev@vger.kernel.org, bpf@vger.kernel.org,
mptcp@lists.linux.dev
Subject: Re: [PATCH bpf 1/2] bpf: drop duplicate check_app_limited in tcp_bpf_push
Date: Mon, 14 Sep 2026 08:45:41 +0000 [thread overview]
Message-ID: <3782cb274da7916a0b46f3e8fefac86b19b0e1ab@linux.dev> (raw)
In-Reply-To: <da26d2f3-7283-4e9f-85b4-6c12b9beda99@linux.dev>
September 14, 2026 at 4:24 PM, "Jiayuan Chen" <jiayuan.chen@linux.dev mailto:jiayuan.chen@linux.dev?to=%22Jiayuan%20Chen%22%20%3Cjiayuan.chen%40linux.dev%3E > wrote:
> Same as the tls one: this looks like a cleanup to me. Is there a real regression that affects kernel or user behavior?
>
> Do we really need a Fixes tag?
>
Hi Jiayuan,
It's a part of the thread in [1], just kindly remind that there had some comments from Matt:
'''
Also, should this be seen as a fix? From what I understand, some
behaviours have changed, and it is only recently that this call is no
longer needed.
'''
From my view, it seems like that there have some misses in the 'fixed' commit, so the fix tag
should be kept, right?
[1] https://lore.kernel.org/mptcp/b5f9e8d7-b738-1df6-3b5e-1d54cbbc663c@gmail.com/T/#m1fbcb32408236e2c68554fd26353c98bb59633f9
Thanks
Gang
> >
> > Signed-off-by: Geliang Tang <tanggeliang@kylinos.cn>
> > ---
> > net/ipv4/tcp_bpf.c | 1 -
> > 1 file changed, 1 deletion(-)
> >
> > diff --git a/net/ipv4/tcp_bpf.c b/net/ipv4/tcp_bpf.c
> > index 2e234d155b5e..d5fcf3ce4861 100644
> > --- a/net/ipv4/tcp_bpf.c
> > +++ b/net/ipv4/tcp_bpf.c
> > @@ -108,7 +108,6 @@ static int tcp_bpf_push(struct sock *sk, struct sk_msg *msg, u32 apply_bytes,
> > off = sge->offset;
> > page = sg_page(sge);
> > > - tcp_rate_check_app_limited(sk);
> > retry:
> > msghdr.msg_flags = flags | MSG_SPLICE_PAGES;
> > has_tx_ulp = tls_sw_has_ctx_tx(sk);
> >
>
next prev parent reply other threads:[~2026-09-14 8:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-14 7:14 [PATCH 0/2] Drop redundant tcp_rate_check_app_limited calls Geliang Tang
2026-09-14 7:14 ` [PATCH bpf 1/2] bpf: drop duplicate check_app_limited in tcp_bpf_push Geliang Tang
2026-09-14 8:24 ` Jiayuan Chen
2026-09-14 8:45 ` gang.yan
2026-09-14 9:31 ` Matthieu Baerts
2026-09-14 8:45 ` gang.yan [this message]
2026-09-14 10:06 ` Geliang Tang
2026-09-14 7:14 ` [PATCH net 2/2] tls: drop duplicate check_app_limited in tls_push_sg Geliang Tang
2026-09-14 8:07 ` bot+bpf-ci
2026-09-15 23:01 ` [PATCH 0/2] Drop redundant tcp_rate_check_app_limited calls Jakub Kicinski
2026-09-16 10:30 ` Geliang Tang
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=3782cb274da7916a0b46f3e8fefac86b19b0e1ab@linux.dev \
--to=gang.yan@linux.dev \
--cc=bpf@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=edumazet@google.com \
--cc=geliang@kernel.org \
--cc=horms@kernel.org \
--cc=jakub@cloudflare.com \
--cc=jiayuan.chen@linux.dev \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=martineau@kernel.org \
--cc=matttbe@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sd@queasysnail.net \
--cc=tanggeliang@kylinos.cn \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox