From: Martin KaFai Lau <martin.lau@linux.dev>
To: John Fastabend <john.fastabend@gmail.com>,
Jakub Sitnicki <jakub@cloudflare.com>
Cc: bpf@vger.kernel.org, Cong Wang <cong.wang@bytedance.com>,
Yaxin Chen <yaxin.chen1@bytedance.com>,
netdev@vger.kernel.org
Subject: Re: [Patch net-next] tcp_bpf: remove an unused parameter for bpf_tcp_ingress()
Date: Tue, 27 Aug 2024 14:50:01 -0700 [thread overview]
Message-ID: <92e329ec-b504-48fa-9ef8-83efa7e5ba6a@linux.dev> (raw)
In-Reply-To: <20240823224843.1985277-1-yaxin.chen1@bytedance.com>
On 8/23/24 3:48 PM, Yaxin Chen wrote:
> Parameter flags is not used in bpf_tcp_ingress().
>
> Reviewed-by: Cong Wang <cong.wang@bytedance.com>
> Cc: John Fastabend <john.fastabend@gmail.com>
> Cc: Jakub Sitnicki <jakub@cloudflare.com>
> Signed-off-by: Yaxin Chen <yaxin.chen1@bytedance.com>
> ---
> net/ipv4/tcp_bpf.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/net/ipv4/tcp_bpf.c b/net/ipv4/tcp_bpf.c
> index 53b0d62fd2c2..57a1614c55f9 100644
> --- a/net/ipv4/tcp_bpf.c
> +++ b/net/ipv4/tcp_bpf.c
> @@ -30,7 +30,7 @@ void tcp_eat_skb(struct sock *sk, struct sk_buff *skb)
> }
>
> static int bpf_tcp_ingress(struct sock *sk, struct sk_psock *psock,
> - struct sk_msg *msg, u32 apply_bytes, int flags)
> + struct sk_msg *msg, u32 apply_bytes)
> {
> bool apply = apply_bytes;
> struct scatterlist *sge;
> @@ -167,7 +167,7 @@ int tcp_bpf_sendmsg_redir(struct sock *sk, bool ingress,
> if (unlikely(!psock))
> return -EPIPE;
>
> - ret = ingress ? bpf_tcp_ingress(sk, psock, msg, bytes, flags) :
> + ret = ingress ? bpf_tcp_ingress(sk, psock, msg, bytes) :
lgtm also. John and Jakub Sitnicki, please help to take a look and Ack if this
looks good to you also.
> tcp_bpf_push_locked(sk, msg, bytes, flags, false);
> sk_psock_put(sk, psock);
> return ret;
next prev parent reply other threads:[~2024-08-27 21:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-23 22:48 [Patch net-next] tcp_bpf: remove an unused parameter for bpf_tcp_ingress() Yaxin Chen
2024-08-26 21:49 ` Jakub Kicinski
2024-08-27 21:50 ` Martin KaFai Lau [this message]
2024-08-29 15:56 ` Jakub Sitnicki
2024-09-02 16:50 ` patchwork-bot+netdevbpf
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=92e329ec-b504-48fa-9ef8-83efa7e5ba6a@linux.dev \
--to=martin.lau@linux.dev \
--cc=bpf@vger.kernel.org \
--cc=cong.wang@bytedance.com \
--cc=jakub@cloudflare.com \
--cc=john.fastabend@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=yaxin.chen1@bytedance.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).