From: Jason Xing <kerneljasonxing@gmail.com>
To: edumazet@google.com, pablo@netfilter.org, kadlec@netfilter.org,
fw@strlen.de, kuba@kernel.org, pabeni@redhat.com,
davem@davemloft.net
Cc: netfilter-devel@vger.kernel.org, coreteam@netfilter.org,
netdev@vger.kernel.org, Jason Xing <kernelxing@tencent.com>
Subject: Re: [PATCH net-next] netfilter: conntrack: dccp: try not to drop skb in conntrack
Date: Mon, 11 Mar 2024 14:37:25 +0800 [thread overview]
Message-ID: <CAL+tcoBsTjTRMiFzq_EHyYSBr9rROO-QFY5PZ3Aj-M4YDLpr=g@mail.gmail.com> (raw)
In-Reply-To: <20240308092915.9751-1-kerneljasonxing@gmail.com>
On Fri, Mar 8, 2024 at 5:29 PM Jason Xing <kerneljasonxing@gmail.com> wrote:
>
> From: Jason Xing <kernelxing@tencent.com>
>
> It would be better not to drop skb in conntrack unless we have good
> alternative as Florian said[1]. So we can treat the result of testing
> skb's header pointer as nf_conntrack_tcp_packet() does.
>
> [1]
> Link: https://lore.kernel.org/all/20240307141025.GL4420@breakpoint.cc/
>
> Signed-off-by: Jason Xing <kernelxing@tencent.com>
> ---
> net/netfilter/nf_conntrack_proto_dccp.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/net/netfilter/nf_conntrack_proto_dccp.c b/net/netfilter/nf_conntrack_proto_dccp.c
> index e2db1f4ec2df..ebc4f733bb2e 100644
> --- a/net/netfilter/nf_conntrack_proto_dccp.c
> +++ b/net/netfilter/nf_conntrack_proto_dccp.c
> @@ -525,7 +525,7 @@ int nf_conntrack_dccp_packet(struct nf_conn *ct, struct sk_buff *skb,
>
> dh = skb_header_pointer(skb, dataoff, sizeof(*dh), &_dh.dh);
> if (!dh)
> - return NF_DROP;
> + return -NF_ACCEPT;
>
> if (dccp_error(dh, skb, dataoff, state))
> return -NF_ACCEPT;
> @@ -533,7 +533,7 @@ int nf_conntrack_dccp_packet(struct nf_conn *ct, struct sk_buff *skb,
> /* pull again, including possible 48 bit sequences and subtype header */
> dh = dccp_header_pointer(skb, dataoff, dh, &_dh);
> if (!dh)
> - return NF_DROP;
> + return -NF_ACCEPT;
>
> type = dh->dccph_type;
> if (!nf_ct_is_confirmed(ct) && !dccp_new(ct, skb, dh, state))
> --
> 2.37.3
>
I saw the status in patchwork was changed, but I've not received the
comments. So I spent some time learning how it works in the netfilter
area.
I just noticed that there are two trees (nf and nf-next), so should I
target nf-next and resend this patch and another one[1]?
[1]: https://lore.kernel.org/netfilter-devel/20240308092915.9751-2-kerneljasonxing@gmail.com/T/#m0ced362b380cff7e031d020e906ec2aa00669ce6
Thanks,
Jason
next prev parent reply other threads:[~2024-03-11 6:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-08 9:29 [PATCH net-next] netfilter: conntrack: dccp: try not to drop skb in conntrack Jason Xing
2024-03-08 9:29 ` [PATCH net-next] netfilter: conntrack: using NF_DROP in test statement in nf_conntrack_in() Jason Xing
2024-03-11 6:37 ` Jason Xing [this message]
2024-03-11 15:56 ` [PATCH net-next] netfilter: conntrack: dccp: try not to drop skb in conntrack Jakub Kicinski
2024-03-11 16:00 ` Jason Xing
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='CAL+tcoBsTjTRMiFzq_EHyYSBr9rROO-QFY5PZ3Aj-M4YDLpr=g@mail.gmail.com' \
--to=kerneljasonxing@gmail.com \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=kadlec@netfilter.org \
--cc=kernelxing@tencent.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pablo@netfilter.org \
/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).