From: Peilin Ye <yepeilin.cs@gmail.com>
To: Davide Caratti <dcaratti@redhat.com>
Cc: Jamal Hadi Salim <jhs@mojatatu.com>,
Cong Wang <xiyou.wangcong@gmail.com>,
Jiri Pirko <jiri@resnulli.us>, Paolo Abeni <pabeni@redhat.com>,
Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>,
wizhao@redhat.com, netdev@vger.kernel.org
Subject: Re: [PATCH net] net/sched: act_mirred: use the backlog for mirred ingress
Date: Fri, 18 Nov 2022 15:07:29 -0800 [thread overview]
Message-ID: <20221118230729.GA2234@bytedance> (raw)
In-Reply-To: <33dc43f587ec1388ba456b4915c75f02a8aae226.1663945716.git.dcaratti@redhat.com>
Hi all,
On Fri, Sep 23, 2022 at 05:11:12PM +0200, Davide Caratti wrote:
> +mirred_egress_to_ingress_tcp_test()
> +{
> + local tmpfile=$(mktemp) tmpfile1=$(mktemp)
> +
> + RET=0
> + dd conv=sparse status=none if=/dev/zero bs=1M count=2 of=$tmpfile
> + tc filter add dev $h1 protocol ip pref 100 handle 100 egress flower \
> + ip_proto tcp src_ip 192.0.2.1 dst_ip 192.0.2.2 \
> + action ct commit nat src addr 192.0.2.2 pipe \
> + action ct clear pipe \
> + action ct commit nat dst addr 192.0.2.1 pipe \
> + action ct clear pipe \
> + action skbedit ptype host pipe \
> + action mirred ingress redirect dev $h1
FWIW, I couldn't reproduce the lockup using this test case (with
forwarding.config.sample), but I got the same lockup in tcp_v4_rcv()
using a different (but probably less realistic) TC filter:
tc filter add dev $h1 protocol ip pref 100 handle 100 egress flower \
ip_proto tcp src_ip 192.0.2.1 dst_ip 192.0.2.2 \
action pedit ex munge ip src set 192.0.2.2 pipe \
action pedit ex munge ip dst set 192.0.2.1 pipe \
action skbedit ptype host pipe \
action mirred ingress redirect dev $h1
Thanks,
Peilin Ye
next prev parent reply other threads:[~2022-11-18 23:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-23 15:11 [PATCH net] net/sched: act_mirred: use the backlog for mirred ingress Davide Caratti
2022-09-25 18:08 ` Cong Wang
2022-10-04 17:40 ` Davide Caratti
2022-10-16 17:28 ` Cong Wang
2022-11-18 23:07 ` Peilin Ye [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-09 23:54 Jakub Kicinski
2024-02-12 14:51 ` Jamal Hadi Salim
2024-02-12 15:02 ` Jakub Kicinski
2024-02-12 15:11 ` Jamal Hadi Salim
2024-02-13 11:06 ` Paolo Abeni
2024-02-14 0:27 ` Jakub Kicinski
2024-02-14 3:40 ` Jakub Kicinski
2024-02-14 15:11 ` Jamal Hadi Salim
2024-02-14 15:28 ` Jamal Hadi Salim
2024-02-14 16:10 ` Davide Caratti
2024-02-15 0:31 ` Jakub Kicinski
2024-02-15 17:55 ` Davide Caratti
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=20221118230729.GA2234@bytedance \
--to=yepeilin.cs@gmail.com \
--cc=dcaratti@redhat.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=marcelo.leitner@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=wizhao@redhat.com \
--cc=xiyou.wangcong@gmail.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).