On 2019/10/19 5:25 上午, Eyal Birger wrote:
Hi,
On Fri, 18 Oct 2019 00:33:53 +0800
Zhiyuan Hou wrote:
On 2019/10/16 8:13 下午, Eyal Birger wrote:
Hi,
On Wed, 16 Oct 2019 01:22:01 +0800
Zhiyuan Hou wrote:
On 2019/10/15 1:57 上午, Cong Wang wrote:
On Sat, Oct 12, 2019 at 12:16 AM Zhiyuan
On 2019/10/16 8:13 下午, Eyal Birger wrote:
Hi,
On Wed, 16 Oct 2019 01:22:01 +0800
Zhiyuan Hou wrote:
On 2019/10/15 1:57 上午, Cong Wang wrote:
On Sat, Oct 12, 2019 at 12:16 AM Zhiyuan Hou
wrote:
diff --git a/net/sched/act_mirred.c b/net/sched/act_mirred.c
index 9ce073a05414..6108a64c0cd5
On 2019/10/14 8:46 下午, Eric Dumazet wrote:
On 10/14/19 12:07 AM, Zhiyuan Hou wrote:
On 2019/10/12 6:59 下午, Eric Dumazet wrote:
On 10/12/19 12:16 AM, Zhiyuan Hou wrote:
In act_mirred's ingress redirection, if the skb's dst_entry is valid
when call function netif_receive_skb, the fllowing l3
On 2019/10/15 1:57 上午, Cong Wang wrote:
On Sat, Oct 12, 2019 at 12:16 AM Zhiyuan Hou
wrote:
diff --git a/net/sched/act_mirred.c b/net/sched/act_mirred.c
index 9ce073a05414..6108a64c0cd5 100644
--- a/net/sched/act_mirred.c
+++ b/net/sched/act_mirred.c
@@ -18,6 +18,7 @@
#include
#include
On 2019/10/13 3:34 上午, Sergei Shtylyov wrote:
Hello!
On 10/12/2019 10:16 AM, Zhiyuan Hou wrote:
In act_mirred's ingress redirection, if the skb's dst_entry is valid
when call function netif_receive_skb, the fllowing l3 stack process
Following or flowing?
Sorry, it should be following
On 2019/10/12 6:59 下午, Eric Dumazet wrote:
On 10/12/19 12:16 AM, Zhiyuan Hou wrote:
In act_mirred's ingress redirection, if the skb's dst_entry is valid
when call function netif_receive_skb, the fllowing l3 stack process
(ip_rcv_finish_core) will check dst_entry and skip the routing
decision
dst->dst_input points to dst_discard.
This patch drops the skb's dst_entry before calling netif_receive_skb
so that the skb can be made routing decision like a normal ingress
skb.
Signed-off-by: Zhiyuan Hou
---
net/sched/act_mirred.c | 5 -
1 file changed, 4 insertions(+), 1 delet
在 2019/6/26 下午4:16, Paolo Abeni 写道:
Hi,
On Tue, 2019-06-25 at 14:42 +0800, Zhiyuan Hou wrote:
In ipvlan l3s mode, ingress packet is switched to slave interface and
delivers to l4 stack. This may cause two problems:
1. When slave is in an ns different from master, the behavior of stack
nf_conntrack_confirm() to make
conntrack work with new mode.
Signed-off-by: Zha Bin
Signed-off-by: Zhiyuan Hou
---
drivers/net/ipvlan/ipvlan.h | 9 -
drivers/net/ipvlan/ipvlan_l3s.c | 16 ++--
2 files changed, 22 insertions(+), 3 deletions(-)
diff --git a/drivers/net
9 matches
Mail list logo
